MicMac - Contributions de l’utilisateur [fr]

Campari

2019-04-10T07:20:58Z

XavierR : Explanations of PPFree

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==

Campari is a tool for compensation of heterogeneous measures (tie points and ground control points).

===Syntax===
The global syntax for Campari is :

<pre>mm3d Campari FullDirectory InputOrientation OutputOrientation NamedArgs</pre>

===Help===
You can access to the help by typing :
<pre>mm3d Campari -help</pre>

Mandatory unnamed args :
* string :: {Full Directory (Dir+Pattern)}
* string :: {Input Orientation}
* string :: {Output Orientation}

Named args :
*[Name=GCP] vector :: {[GrMes.xml,GrUncertainty,ImMes.xml,ImUnc]}
*[Name=EmGPS] vector :: {Embedded GPS [Gps-Dir,GpsUnc, ?GpsAlti?], GpsAlti if != Plani}
*[Name=GpsLa] Pt3dr :: {Gps Lever Arm, in combination with EmGPS}
*[Name=SigmaTieP] REAL :: {Sigma use for TieP weighting (Def=1)}
*[Name=FactElimTieP] REAL :: {Fact elimination of tie point (prop to SigmaTieP, Def=5)}
*[Name=CPI1] bool :: {Calib Per Im, Firt time}
*[Name=CPI2] bool :: {Calib Per Im, After first time, reUsing Calib Per Im As input}
*[Name=FocFree] bool :: {Foc Free (Def=false)}
*[Name=PPFree] bool :: {Principal Point Free (Def=false)}
*[Name=AffineFree] bool :: {Affine Parameter (Def=false)}
*[Name=AllFree] bool :: {Affine Parameter (Def=false)}
*[Name=DetGCP] bool :: {Detail on GCP (Def=false)}
*[Name=Visc] REAL :: {Viscosity in Levenberg-Marquardt like resolution (Def=1.0)}
*[Name=ExpTxt] bool :: {Export in text format (Def=false)}
*[Name=ImMinMax] vector :: {Im max and min to avoid tricky pat}
*[Name=DegAdd] INT :: {When specified, degree of additional parameter}
*[Name=DegFree] INT :: {When specified degree of freedom of parameters generics}
*[Name=DRMax] INT :: {When specified degree of freedom of radial parameters}
*[Name=PoseFigee] bool :: {Does the external orientation of the cameras are frozen or free (Def=false, i.e. camera poses are free)}

By default, the bundle adjustment computed by Campari only affects camera orientation. Changing the value of '''FocFree''' and/or '''PPFree''' and/or '''AffineFree''', or '''AllFree''' to '''1''' permits to refine also camera calibration.

A stated [http://bestrema.fr/micmac-tutoriel-et-script-pour-photogrammetrie-sous-windows/ on this page], '''PPFree=True''' (or PPFree=1) may be used with RadialBasic or RadialStd calibration when the camera stabilization is enabled. In these cases prinpal point of the camera is mobile and has to be computed.

=== Understanding the output ===

The following image explains what each values in the output means :
[http://folk.uio.no/lucg/data_transfert/MicMac/CampariFig.jpg Image]

===Examples===
====Using GCP file====
For example, in the Mur Saint Martin dataset, you can launch :
<pre>mm3d Campari ".*JPG" MEP-Basc2 MEP-Terrain GCP=[MurSaintMartin.xml,0.02,MesureBasc.xml,0.5]</pre>

====With embedded GPS data, with refinement of camera calibration====
In the "Grand-Leez" dataset, adding GPS information in the bundle adjustment has a positive impact on the refinement of the camera orientation, in particular on the camera calibration.
<pre>Campari "R.*.JPG" BL72 BL72-Campari EmGPS=[GPS-BL72,2] FocFree=1 PPFree=1</pre>

==Meaning of error messages==
=== Unexpected End Of String in ElStdRead(vector<Type> &) ===
If you got an errors as:
<pre>------------------------------------------------------------
| Sorry, the following FATAL ERROR happened
|
| Unexpected End Of String in ElStdRead(vector<Type> &)
|
------------------------------------------------------------</pre>
It's probably just because you forgot a space into the brackets expression, as this:
mm3d Campari .*JPG Arbitrary Ground GCP=[Target_Coord.xml,0.01, Target_measure-S2D.xml,0.5]
in place of this:
mm3d Campari .*JPG Arbitrary Ground GCP=[Target_Coord.xml,0.01,Target_measure-S2D.xml,0.5]

Campari

2019-04-10T07:08:13Z

XavierR : Add meaning of an error message

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==

Campari is a tool for compensation of heterogeneous measures (tie points and ground control points).

===Syntax===
The global syntax for Campari is :

<pre>mm3d Campari FullDirectory InputOrientation OutputOrientation NamedArgs</pre>

===Help===
You can access to the help by typing :
<pre>mm3d Campari -help</pre>

Mandatory unnamed args :
* string :: {Full Directory (Dir+Pattern)}
* string :: {Input Orientation}
* string :: {Output Orientation}

Named args :
*[Name=GCP] vector :: {[GrMes.xml,GrUncertainty,ImMes.xml,ImUnc]}
*[Name=EmGPS] vector :: {Embedded GPS [Gps-Dir,GpsUnc, ?GpsAlti?], GpsAlti if != Plani}
*[Name=GpsLa] Pt3dr :: {Gps Lever Arm, in combination with EmGPS}
*[Name=SigmaTieP] REAL :: {Sigma use for TieP weighting (Def=1)}
*[Name=FactElimTieP] REAL :: {Fact elimination of tie point (prop to SigmaTieP, Def=5)}
*[Name=CPI1] bool :: {Calib Per Im, Firt time}
*[Name=CPI2] bool :: {Calib Per Im, After first time, reUsing Calib Per Im As input}
*[Name=FocFree] bool :: {Foc Free (Def=false)}
*[Name=PPFree] bool :: {Principal Point Free (Def=false)}
*[Name=AffineFree] bool :: {Affine Parameter (Def=false)}
*[Name=AllFree] bool :: {Affine Parameter (Def=false)}
*[Name=DetGCP] bool :: {Detail on GCP (Def=false)}
*[Name=Visc] REAL :: {Viscosity in Levenberg-Marquardt like resolution (Def=1.0)}
*[Name=ExpTxt] bool :: {Export in text format (Def=false)}
*[Name=ImMinMax] vector :: {Im max and min to avoid tricky pat}
*[Name=DegAdd] INT :: {When specified, degree of additional parameter}
*[Name=DegFree] INT :: {When specified degree of freedom of parameters generics}
*[Name=DRMax] INT :: {When specified degree of freedom of radial parameters}
*[Name=PoseFigee] bool :: {Does the external orientation of the cameras are frozen or free (Def=false, i.e. camera poses are free)}

By default, the bundle adjustment computed by Campari only affects camera orientation. Changing the value of '''FocFree''' and/or '''PPFree''' and/or '''AffineFree''', or '''AllFree''' to '''1''' permits to refine also camera calibration.

=== Understanding the output ===

The following image explains what each values in the output means :
[http://folk.uio.no/lucg/data_transfert/MicMac/CampariFig.jpg Image]

===Examples===
====Using GCP file====
For example, in the Mur Saint Martin dataset, you can launch :
<pre>mm3d Campari ".*JPG" MEP-Basc2 MEP-Terrain GCP=[MurSaintMartin.xml,0.02,MesureBasc.xml,0.5]</pre>

====With embedded GPS data, with refinement of camera calibration====
In the "Grand-Leez" dataset, adding GPS information in the bundle adjustment has a positive impact on the refinement of the camera orientation, in particular on the camera calibration.
<pre>Campari "R.*.JPG" BL72 BL72-Campari EmGPS=[GPS-BL72,2] FocFree=1 PPFree=1</pre>

==Meaning of error messages==
=== Unexpected End Of String in ElStdRead(vector<Type> &) ===
If you got an errors as:
<pre>------------------------------------------------------------
| Sorry, the following FATAL ERROR happened
|
| Unexpected End Of String in ElStdRead(vector<Type> &)
|
------------------------------------------------------------</pre>
It's probably just because you forgot a space into the brackets expression, as this:
mm3d Campari .*JPG Arbitrary Ground GCP=[Target_Coord.xml,0.01, Target_measure-S2D.xml,0.5]
in place of this:
mm3d Campari .*JPG Arbitrary Ground GCP=[Target_Coord.xml,0.01,Target_measure-S2D.xml,0.5]

Install MicMac Windows

2019-03-27T12:16:32Z

XavierR : Reorder, Delete obsolete exiv2 manual installation

= Install process for MicMac on Windows =
French version below.

==Installation with binaries==
===Download===
====Download last beta binaries from GitHub ====
Download the micmac_win.zip archive here :

<code>https://github.com/micmacIGN/micmac/releases</code> 
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta13/micmac_win.zip v1.0.beta13] is a 64 bits release.
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta10/micmac_win.zip v1.0.beta10] is a 32 bits one.

====Or download last "nightly" binary from AppVeyor====
Download the '''micmac_win.zip''' archive here (only for Windows 64 bits) : 

<code>https://ci.appveyor.com/project/gmaillet/micmac-uct71/build/artifacts</code>

===Installation===
Choose the 32 or 64bits version according your Windows system ("Configuration pannel/System"). Then extract the ".zip" file where you want to install MicMac.
*We recommend you to install MicMac in a directory where the path doesn't include any space or special character (i.e.: " ","&","@" etc...). The common error is to install it in "C:\Program Files (x86)" which include space.

===Set environmental path===
It is possible that you should have to indicate to your computer where the MicMac binaries are. You need to open the configuration panel -> System -> Set parameters (Screenshot 1)
[[Image:Capture ecran1.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 1]]

Then Advanced parameters -> Environnemental variable (Screenshot 2).
[[Image:Capture ecran2.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 2]]

Double-click in the path variable and add at the end (Screenshot 3): 
<code>;installation_directory\micmac\bin (for example ";C:\micmac\bin")</code>
[[Image:Capture ecran3.jpg|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 3]]

==Installation with Setup - Obsolete: Non recommanded ==

*This is an old version : '''NOT RECOMMANDED. [[:Install_MicMac_Windows#Download_last_beta_binaries_from_GitHub| Use rather binaries from GitHub to get newer releases]].'''

*Download the setup from : 
<code>http://logiciels.ign.fr/?Telechargement,20</code> 
Choose the 32 or 64bits version according to your Windows system ("Configuration pannel/System"). Then, follow the differents step of the setup.
*We recommand you to install MicMac in a directory where the path doesn't include any space or special character (i.e.: " ","&","@" etc...). The common error is to install it in "C:\Program Files (x86)" which include space.

==Check Installation==
===List of micmac tools===
To check if MicMac is well installed, you can type in a terminal :
<pre>mm3d</pre>
This will return the list of all tools available for micmac library. 

===Check dependencies===
Sometimes, even when the MicMac installation is good, you can encounter messages in the terminal such as :
*"Warning Exiftool not installed"
This warnings means that MicMac can't find an external tools.
MicMac integrates a module which can check if all dependencies are correctly installed. It can be called by typing : 
<pre>
mm3d CheckDependencies
</pre>

[[Image:checkdependencies.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 4]]

You will get an output like Screenshot 4, with different informations :
*MicMac revision : micmac source code version number
*Qt : "enabled" permit you to use graphical interfaces such SaisieAppuisQT
*Kakadu : Image library for JPEG2000 management
*MicMac directory : Directory where MicMac is installed
*make :
*exiftool : library of image metadata management
*exiv2 : library of image metadata management
*convert :
*proj : library for cartographic projection
*cs2cs :

==Known problems==

==How to use MicMac with Windows==

This video shows some basic steps on how to use MicMac on Windows.

{{#ev:youtube|https://www.youtube.com/watch?v=tezTFRanTYA|500x300px}}

=French Version : Installation de MicMac sous Windows=

==Avec les binaires==

===Téléchargement===
====Téléchargement des derniers binaires à partir de GitHub ====
Télécharger l'archive micmac_win.zip ici :

<code>https://github.com/micmacIGN/micmac/releases</code> 
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta13/micmac_win.zip v1.0.beta13] est une version 64 bits.
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta10/micmac_win.zip v1.0.beta10] est une version 32 bits.

====Ou télécharger les derniers binaires "instables" sur AppVeyor====
Télécharger l'archive micmac_win.zip ici (seulement pour Windows 64 bits) :

<code>https://ci.appveyor.com/project/gmaillet/micmac-uct71/build/artifacts</code>

====Ou télécharger les derniers binaires "instables" sur le site de l'IGN ====
Télécharger le binaire ici : 
<code>http://logiciels.ign.fr/?Telechargement,20</code> 

===Installation===
*Décompresser le fichier micmac_bin_windows_x86_64_rev3982.zip dans le répertoire voulu. Attention : proscrire les arborescences contenant des espaces ou/et des accents) !

*Aller dans « Panneau de configuration Système », cliquer sur « Modifier les paramètres »

*Cliquer ensuite sur « Paramètres Système Avancés » et enfin sur « Variables d’environnement. »

*Dans « Variables Système » choisir la variable « Path » et cliquer sur « Modifier ».

*Dans « Valeur de la variable », rajouter à la fin un point-virgule suivi du nom du répertoire contenant les binaires ;répertoire_des_binaires. Attention : proscrire les arborescences contenant des espaces ou/et des accents) !

*Quitter le panneau de configuration en cliquant sur OK à chaque fois.
==Avec l'installateur - Obsolète : NON RECOMMANDÉ ! ==

*Cette solution consiste à installer MicMac en téléchargeant le setup proposé sur le site de l’IGN. Attention : L’installation par setup est uniquement recommandée si la version d’installation est la plus récente disponible sur le site.

*Télécharger le setup depuis http://logiciels.ign.fr/?Micmac. Choisir la version 32 ou 64bits en fonction de son type de système. Suivre les étapes d’installation semblable aux setups des logiciels Windows.

==Vérification de l'installation==

*Lancer une invite de commande (Installation_MicMac_Windows) et taper mm3d pour vérifier que tout est bien installé. La liste des commandes disponibles doit s’afficher.

*Taper ensuite : mm3d CheckDependencies

*Vérifier que tout est installé en vérifiant que chaque paquet est « found ». Si un paquet est manquant, se référer au fichier LisezMoi téléchargé avec les binaires.

[[Category:Installation]]

Install MicMac Windows

2019-03-27T12:03:48Z

XavierR : /* With Setup */

French version below.

==With binaries==
===Download===
====Download last beta binaries from GitHub ====
Download the micmac_win.zip archive here :

<code>https://github.com/micmacIGN/micmac/releases</code> 
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta13/micmac_win.zip v1.0.beta13] is a 64 bits release.
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta10/micmac_win.zip v1.0.beta10] is a 32 bits one.

====Or download last "nightly" binary from AppVeyor====
Download the '''micmac_win.zip''' archive here (only for Windows 64 bits) : 

<code>https://ci.appveyor.com/project/gmaillet/micmac-uct71/build/artifacts</code>

===Installation===
Choose the 32 or 64bits version according your Windows system ("Configuration pannel/System"). Then extract the ".zip" file where you want to install MicMac.
*We recommend you to install MicMac in a directory where the path doesn't include any space or special character (i.e.: " ","&","@" etc...). The common error is to install it in "C:\Program Files (x86)" which include space.

===Set environmental path===
It is possible that you should have to indicate to your computer where the MicMac binaries are. You need to open the configuration panel -> System -> Set parameters (Screenshot 1)
[[Image:Capture ecran1.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 1]]

Then Advanced parameters -> Environnemental variable (Screenshot 2).
[[Image:Capture ecran2.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 2]]

Double-click in the path variable and add at the end (Screenshot 3): 
<code>;installation_directory\micmac\bin (for example ";C:\micmac\bin")</code>
[[Image:Capture ecran3.jpg|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 3]]

==With Setup==

*This is an old version : '''NOT RECOMMANDED. [[:Install_MicMac_Windows#Download_last_beta_binaries_from_GitHub| Use rather binaries from GitHub to get newer releases]].'''

*Download the setup from : 
<code>http://logiciels.ign.fr/?Telechargement,20</code> 
Choose the 32 or 64bits version according to your Windows system ("Configuration pannel/System"). Then, follow the differents step of the setup.
*We recommand you to install MicMac in a directory where the path doesn't include any space or special character (i.e.: " ","&","@" etc...). The common error is to install it in "C:\Program Files (x86)" which include space.

==Check Installation==
===List of micmac tools===
To check if MicMac is well installed, you can type in a terminal :
<pre>mm3d</pre>
This will return the list of all tools available for micmac library. 

===Check dependencies===
Sometimes, even when the MicMac installation is good, you can encounter messages in the terminal such as :
*"Warning Exiftool not installed"
This warnings means that MicMac can't find an external tools.
MicMac integrates a module which can check if all dependencies are correctly installed. It can be called by typing : 
<pre>
mm3d CheckDependencies
</pre>

[[Image:checkdependencies.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 4]]

You will get an output like Screenshot 4, with different informations :
*MicMac revision : micmac source code version number
*Qt : "enabled" permit you to use graphical interfaces such SaisieAppuisQT
*Kakadu : Image library for JPEG2000 management
*MicMac directory : Directory where MicMac is installed
*make :
*exiftool : library of image metadata management
*exiv2 : library of image metadata management
*convert :
*proj : library for cartographic projection
*cs2cs :

===Option : Install Exiv2===
FIXME: is this always necessary ??

*You can download the exe file from : 
<code>http://www.exiv2.org/download.html</code> 
click on "Download exiv2.exe"

*Move the "exiv2.exe" file in the MicMac binaries directory ("C:\micmac\bin")

==Known problems==

==How to use MicMac with Windows==

This video shows some basic steps on how to use MicMac on Windows.

{{#ev:youtube|https://www.youtube.com/watch?v=tezTFRanTYA|500x300px}}

=French Version : Installation MicMac pour windows=

==Avec le setup==

*Cette solution consiste à installer MicMac en téléchargeant le setup proposé sur le site de l’IGN. Attention : L’installation par setup est uniquement recommandée si la version d’installation est la plus récente disponible sur le site.

*Télécharger le setup depuis http://logiciels.ign.fr/?Micmac. Choisir la version 32 ou 64bits en fonction de son type de système. Suivre les étapes d’installation semblable aux setups des logiciels Windows.

==Avec les binaires==

===Téléchargement===
====Téléchargement des derniers binaires à partir de GitHub ====
Télécharger l'archive micmac_win.zip ici :

<code>https://github.com/micmacIGN/micmac/releases</code> 
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta13/micmac_win.zip v1.0.beta13] est une version 64 bits.
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta10/micmac_win.zip v1.0.beta10] est une version 32 bits.

====Ou télécharger les derniers binaires "instables" sur AppVeyor====
Télécharger l'archive micmac_win.zip ici (seulement pour Windows 64 bits) :

<code>https://ci.appveyor.com/project/gmaillet/micmac-uct71/build/artifacts</code>

====Ou télécharger les derniers binaires "instables" sur le site de l'IGN ====
Télécharger le binaire ici : 
<code>http://logiciels.ign.fr/?Telechargement,20</code> 

===Installation===
*Décompresser le fichier micmac_bin_windows_x86_64_rev3982.zip dans le répertoire voulu. Attention : proscrire les arborescences contenant des espaces ou/et des accents) !

*Aller dans « Panneau de configuration Système », cliquer sur « Modifier les paramètres »

*Cliquer ensuite sur « Paramètres Système Avancés » et enfin sur « Variables d’environnement. »

*Dans « Variables Système » choisir la variable « Path » et cliquer sur « Modifier ».

*Dans « Valeur de la variable », rajouter à la fin un point-virgule suivi du nom du répertoire contenant les binaires ;répertoire_des_binaires. Attention : proscrire les arborescences contenant des espaces ou/et des accents) !

*Quitter le panneau de configuration en cliquant sur OK à chaque fois.

===Vérification de l'iinstallation===

*Lancer une invite de commande (Installation_MicMac_Windows) et taper mm3d pour vérifier que tout est bien installé. La liste des commandes disponibles doit s’afficher.

*Taper ensuite : mm3d CheckDependencies

*Vérifier que tout est installé en vérifiant que chaque paquet est « found ». Si un paquet est manquant, se référer au fichier LisezMoi téléchargé avec les binaires.

==Optionnel : Installation de Exiv2==
*Se rendre sur http://www.exiv2.org/download.html puis télécharger l’éxecutable Windows en cliquant sur « Download exiv2.exe ».

*Il faut ensuite placer le fichier exiv2.exe à côté des binaires de MicMac (par défaut C:\MicMac64bits\bin)

[[Category:Installation]]

Install

2019-03-27T12:02:35Z

XavierR : ordering titles

MicMac is an open source project that aims at being cross platform. Very few dependencies are mandatory to have the core program work.

The following platforms are "officially" supported, but it is possible to install MicMac on most x86/x64 platforms (Windows Xp-Vista-7-8-10, Mac OSX, Fedora, RHEL, Ubuntu...).

==Ubuntu==
Learn how to [[Install MicMac Ubuntu|Install MicMac on Ubuntu]].

Here is some basic steps on how to use [[Tutorial Ubuntu|commands Ubuntu]].

==Windows==
Learn how to [[Install MicMac Windows|install MicMac on Windows]]

==Mac==
Learn how to [[Install MicMac MAC|install MicMac on MAC]]

==Raspberry Pi==
Learn how to [[Compilation_de_MicMac_sur_ARM_(RaspBerryPi)|install MicMac on Raspberry Pi]]

==Useful softwares for MicMac==

=== GUI ===
==== AperoDeDenis ====
You can use '''AperoDeDenis''' which try to be a global and easy to use alternative GUI to use MicMac.

It is developed by Denis Jouin from the [https://www.cerema.fr/fr/actualites/cerema-normandie-centre-facilite-acces-photogrammetrie-3d Cerema] (Centre d'études et d'expertise sur les risques, l'environnement, la mobilité et l'aménagement, french public institute).

The main repository to download documentation and software is hosted on [https://github.com/micmacIGN/InterfaceCEREMA/tree/master/InterfaceCEREMA GitHub].

Micmac and Meshlab/CloudCompare (see below) have to be set up before to use AperoDeDenis.

=== Visualization ===

Here are some really useful tools to visualize the different 3D products :
*'''MeshLab''' : http://www.meshlab.net/ (all platform are supported). This software is generally used for points clouds visualization, surface reconstruction and texturing.
*'''CloudCompare''' : http://www.cloudcompare.org/ (all platforms). Similar to Meshlab, possibly more up to date and richer in tools.

Install

2019-03-27T12:00:57Z

XavierR : Delete Nautilus specific tool, too specific!

MicMac is an open source project that aims at being cross platform. Very few dependencies are mandatory to have the core program work.

The following platforms are "officially" supported, but it is possible to install MicMac on most x86/x64 platforms (Windows Xp-Vista-7-8-10, Mac OSX, Fedora, RHEL, Ubuntu...).

==Ubuntu==
Learn how to [[Install MicMac Ubuntu|Install MicMac on Ubuntu]].

Here is some basic steps on how to use [[Tutorial Ubuntu|commands Ubuntu]].

==Windows==
Learn how to [[Install MicMac Windows|install MicMac on Windows]]

==Mac==
Learn how to [[Install MicMac MAC|install MicMac on MAC]]

==Raspberry Pi==
Learn how to [[Compilation_de_MicMac_sur_ARM_(RaspBerryPi)|install MicMac on Raspberry Pi]]

==Useful softwares for MicMac==

=== GUI ===
You can use '''AperoDeDenis''' which try to be a global and easy to use alternative GUI to use MicMac.

It is developed by Denis Jouin from the [https://www.cerema.fr/fr/actualites/cerema-normandie-centre-facilite-acces-photogrammetrie-3d Cerema] (Centre d'études et d'expertise sur les risques, l'environnement, la mobilité et l'aménagement, french public institute).

The main repository to download documentation and software is hosted on [https://github.com/micmacIGN/InterfaceCEREMA/tree/master/InterfaceCEREMA GitHub].

Micmac and Meshlab/CloudCompare (see below) have to be set up before to use AperoDeDenis.

=== Visualization ===

Here are some really useful tools to visualize the different 3D products :
*'''MeshLab''' : http://www.meshlab.net/ (all platform are supported). This software is generally used for points clouds visualization, surface reconstruction and texturing.
*'''CloudCompare''' : http://www.cloudcompare.org/ (all platforms). Similar to Meshlab, possibly more up to date and richer in tools.

Install

2019-03-27T12:00:07Z

XavierR : Update and improve AperoDeDenis presentation

MicMac is an open source project that aims at being cross platform. Very few dependencies are mandatory to have the core program work.

The following platforms are "officially" supported, but it is possible to install MicMac on most x86/x64 platforms (Windows Xp-Vista-7-8-10, Mac OSX, Fedora, RHEL, Ubuntu...).

==Ubuntu==
Learn how to [[Install MicMac Ubuntu|Install MicMac on Ubuntu]].

Here is some basic steps on how to use [[Tutorial Ubuntu|commands Ubuntu]].

==Windows==
Learn how to [[Install MicMac Windows|install MicMac on Windows]]

==Mac==
Learn how to [[Install MicMac MAC|install MicMac on MAC]]

==Raspberry Pi==
Learn how to [[Compilation_de_MicMac_sur_ARM_(RaspBerryPi)|install MicMac on Raspberry Pi]]

==Useful softwares for MicMac==

=== GUI ===
You can use '''AperoDeDenis''' which try to be a global and easy to use alternative GUI to use MicMac.

It is developed by Denis Jouin from the [https://www.cerema.fr/fr/actualites/cerema-normandie-centre-facilite-acces-photogrammetrie-3d Cerema] (Centre d'études et d'expertise sur les risques, l'environnement, la mobilité et l'aménagement, french public institute).

The main repository to download documentation and software is hosted on [https://github.com/micmacIGN/InterfaceCEREMA/tree/master/InterfaceCEREMA GitHub].

Micmac and Meshlab/CloudCompare (see below) have to be set up before to use AperoDeDenis.

=== Visualization ===

Here are some really useful tools to visualize the different 3D products :
*'''MeshLab''' : http://www.meshlab.net/ (all platform are supported). This software is generally used for points clouds visualization, surface reconstruction and texturing.
*'''CloudCompare''' : http://www.cloudcompare.org/ (all platforms). Similar to Meshlab, possibly more up to date and richer in tools.

Other tools that may be useful: :
*Nautilus open terminal : You can install it with : <code>sudo apt-get install nautilus-open-terminal</code> (Linux platform only). This module is really useful for opening a terminal directly from the image directory.

GCPConvert

2019-02-11T15:40:26Z

XavierR :

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
The command GCPConvert is used to:
*transform a set of ground control points from most text format to MicMac’s Xml format.
*transform the ground control points into an euclidean coordinate system, suitable for MicMac.

===Allowed commands===
* AppEgels
* AppGeoCub
* AppInFile
* AppXML

===Syntax===
The global syntax for GCPConvert is :
<pre>mm3d GCPConvert FormatSpecification GCPFile NamedArgs</pre>

===Help===
You can access to the help by typing :
<pre>mm3d GCPConvert -help</pre>

Mandatory unnamed args :
*string :: {[[GCPConvert#Formatting_the_input_GCP_file|Format specification]]}
*string :: {GCP File}
Named args :
*[Name=Out] string :: {Xml Out File}
*[Name=ChSys] string :: {Change coordinate file}
*[Name=MulCo] REAL :: {Multiplier of result (for development and testing use)}
*[Name=MulInc] bool :: {Multiplier also incertitude ? (for development and testing use)}
*[Name=Offs] Pt3dr :: {Offset to substruct to all coordinates ; Def=[0,0,0]}

===Example===
====Formatting the input GCP file====
Launching this command,
<pre>mm3d GCPConvert AppInFile CP3D_Format.txt</pre>
or
<pre>mm3d GCPConvert "#F=N_X_Y_Z" CP3D_Format.txt</pre>
You should get a file like this:
<pre><?xml version="1.0" ?>
<DicoAppuisFlottant>
<OneAppuisDAF>
<Pt>301.610 939.1341 144.75</Pt>
<NamePt>30</NamePt>
<Incertitude>1 1 1</Incertitude>
</OneAppuisDAF>
<OneAppuisDAF>
<Pt>301.412 937.530 144.787</Pt>
<NamePt>31</NamePt>
<Incertitude>1 1 1</Incertitude>
</OneAppuisDAF>
</DicoAppuisFlottant></pre>

====Offset the output GCP file====
To avoid problems which could appear with other tools that don't deal with too many digits coordinates,you can use an offset with the '''Offs''' option:

mm3d GCPConvert AppInFile F20-1_Cibles.txt Offs=[1657000,6210000,0]

===Uncertainty in output XML file===
As seen in previous example, the uncertainty of each ground control point is fixed by default at the value of one ground unit in each direction of the coordinate system:
<pre><Incertitude>1 1 1</Incertitude></pre>

In case of using the generated GCP file with Campari for bundle adjustment, you'll have to specify a factor which will be alter this uncertainty. So, if uncertainty is equal for each direction and each point, it's easier to specify it by this way.
In the following example, factor of '''0.002''' generates an uncertainty of '''2 mm''' in a metric coordinate system.
<pre>mm3d Campari ".*JPG" MEP_Basc2 MEP_Terrain GCP=[Targets.xml,0.002,Targets_Final-S2D.xml,0.5]</pre>

==Formatting the input GCP file ==
If you don't use an AppXML formatted file (in fact a MicMac's XML file), the input file has to be a '''space or tabulation separated values file''' (no comma or other symbols). You can use 'Egels' or 'GeoCub' format, or describe your file as explained below.

===AppGeoCub===
Text file is formatted as:
<pre>PointNumber X Y Z</pre>
Lines beginning with '%' are considered as comments.

===AppEgels===
Text file is formatted as:
<pre>PointNumber VariableNonImported X Y Z</pre>
Lines beginning with '#' are considered as comments.

This file format is used by some IGN/ENSG softwares developed by Yves Egels[http://yves.egels.free.fr/Soft/telecharger.html].

===AppInFile===
The first line describes name and position of the rows. It begins by '#F= ', where
*the first character '#' means that all line beginning by a # will be a comment;
*the two characters 'F=' mean that this is really a format specification;
'#F= ' followed by the format specification :
*'N' means the name of the point;
*'X', 'Y', 'Z' means the coordinates;
*'Ix', 'Iy', 'Iz' means the accuracy (not mandatory);
*S means a string which has not to be interpreted;
separated by spaces.

You can reorder this format as you want.

''Example 1:''
<pre>#F= N X Y Z Ix Iy Iz
157 233.28 144.03 103.05 0.00332 0.0034 0.0039
158 317.011 -0.00000 0.0000 0.0053 0.0060 0.0071</pre>
*N means the first string of each line is the name of the point;
*X, Y, Z means that this strings number 2, 3 and 4 are the coordinates;
*Ix, Iy, Iz means that this strings number 5, 6 and 7 are the accuracy;

''Example 2:''
<pre>#F= N S X Y Z
300 3 94.208685 658.506787 42.39556
301 3 95.323427 656.409116 43.502239
302 3 97.008135 654.424482 45.084237</pre>
*N means the first string of each line is the name of the point;
*S means the 2nd string has not to be interpreted;
*X, Y, Z means that this strings number 3, 4 and 5 are the coordinates.

==Known limitations==
===GCPConverts add many decimals to coordinates===
As reported [[http://forum-micmac.forumprod.com/gcpconvert-add-many-decimals-to-coordinates-t1267.html]], GCPConvert alters slightly values during the conversion, by adding non significant decimals.
So instead of taking back this file:
<pre><?xml version="1.0" ?>
<DicoAppuisFlottant>
<OneAppuisDAF>
<Pt>301.610 939.1341 144.75</Pt>
<NamePt>30</NamePt>
<Incertitude>1 1 1</Incertitude>
</OneAppuisDAF>
<OneAppuisDAF>
<Pt>301.412 937.530 144.787</Pt>
<NamePt>31</NamePt>
<Incertitude>1 1 1</Incertitude>
</OneAppuisDAF>
</DicoAppuisFlottant></pre>
You may rather obtain this one:
<pre><?xml version="1.0" ?>
<DicoAppuisFlottant>
<OneAppuisDAF>
<Pt>301.61000000000001 939.13400000000001 144.75</Pt>
<NamePt>30</NamePt>
<Incertitude>1 1 1</Incertitude>
</OneAppuisDAF>
<OneAppuisDAF>
<Pt>301.41199999999998 937.52999999999997 144.78700000000001</Pt>
<NamePt>31</NamePt>
<Incertitude>1 1 1</Incertitude>
</OneAppuisDAF>
</DicoAppuisFlottant></pre>

GCPConvert

2019-02-11T15:38:59Z

XavierR :

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
The command GCPConvert is used to:
*transform a set of ground control points from most text format to MicMac’s Xml format.
*transform the ground control points into an euclidean coordinate system, suitable for MicMac.

===Allowed commands===
* AppEgels
* AppGeoCub
* AppInFile
* AppXML

===Syntax===
The global syntax for GCPConvert is :
<pre>mm3d GCPConvert FormatSpecification GCPFile NamedArgs</pre>

===Help===
You can access to the help by typing :
<pre>mm3d GCPConvert -help</pre>

Mandatory unnamed args :
*string :: {[[GCPConvert#Formatting_the_input_GCP_file|Format specification]]}
*string :: {GCP File}
Named args :
*[Name=Out] string :: {Xml Out File}
*[Name=ChSys] string :: {Change coordinate file}
*[Name=MulCo] REAL :: {Multiplier of result (for development and testing use)}
*[Name=MulInc] bool :: {Multiplier also incertitude ? (for development and testing use)}
*[Name=Offs] Pt3dr :: {Offset to substruct to all coordinates ; Def=[0,0,0]}

===Example===
==Formatting the input GCP file
Launching this command,
<pre>mm3d GCPConvert AppInFile CP3D_Format.txt</pre>
or
<pre>mm3d GCPConvert "#F=N_X_Y_Z" CP3D_Format.txt</pre>
You should get a file like this:
<pre><?xml version="1.0" ?>
<DicoAppuisFlottant>
<OneAppuisDAF>
<Pt>301.610 939.1341 144.75</Pt>
<NamePt>30</NamePt>
<Incertitude>1 1 1</Incertitude>
</OneAppuisDAF>
<OneAppuisDAF>
<Pt>301.412 937.530 144.787</Pt>
<NamePt>31</NamePt>
<Incertitude>1 1 1</Incertitude>
</OneAppuisDAF>
</DicoAppuisFlottant></pre>

==Offset the output GCP file==
To avoid problems which could appear with other tools that don't deal with too many digits coordinates,you can use an offset with the '''Offs''' option:

mm3d GCPConvert AppInFile F20-1_Cibles.txt Offs=[1657000,6210000,0]

===Uncertainty in output XML file===
As seen in previous example, the uncertainty of each ground control point is fixed by default at the value of one ground unit in each direction of the coordinate system:
<pre><Incertitude>1 1 1</Incertitude></pre>

In case of using the generated GCP file with Campari for bundle adjustment, you'll have to specify a factor which will be alter this uncertainty. So, if uncertainty is equal for each direction and each point, it's easier to specify it by this way.
In the following example, factor of '''0.002''' generates an uncertainty of '''2 mm''' in a metric coordinate system.
<pre>mm3d Campari ".*JPG" MEP_Basc2 MEP_Terrain GCP=[Targets.xml,0.002,Targets_Final-S2D.xml,0.5]</pre>

==Formatting the input GCP file ==
If you don't use an AppXML formatted file (in fact a MicMac's XML file), the input file has to be a '''space or tabulation separated values file''' (no comma or other symbols). You can use 'Egels' or 'GeoCub' format, or describe your file as explained below.

===AppGeoCub===
Text file is formatted as:
<pre>PointNumber X Y Z</pre>
Lines beginning with '%' are considered as comments.

===AppEgels===
Text file is formatted as:
<pre>PointNumber VariableNonImported X Y Z</pre>
Lines beginning with '#' are considered as comments.

This file format is used by some IGN/ENSG softwares developed by Yves Egels[http://yves.egels.free.fr/Soft/telecharger.html].

===AppInFile===
The first line describes name and position of the rows. It begins by '#F= ', where
*the first character '#' means that all line beginning by a # will be a comment;
*the two characters 'F=' mean that this is really a format specification;
'#F= ' followed by the format specification :
*'N' means the name of the point;
*'X', 'Y', 'Z' means the coordinates;
*'Ix', 'Iy', 'Iz' means the accuracy (not mandatory);
*S means a string which has not to be interpreted;
separated by spaces.

You can reorder this format as you want.

''Example 1:''
<pre>#F= N X Y Z Ix Iy Iz
157 233.28 144.03 103.05 0.00332 0.0034 0.0039
158 317.011 -0.00000 0.0000 0.0053 0.0060 0.0071</pre>
*N means the first string of each line is the name of the point;
*X, Y, Z means that this strings number 2, 3 and 4 are the coordinates;
*Ix, Iy, Iz means that this strings number 5, 6 and 7 are the accuracy;

''Example 2:''
<pre>#F= N S X Y Z
300 3 94.208685 658.506787 42.39556
301 3 95.323427 656.409116 43.502239
302 3 97.008135 654.424482 45.084237</pre>
*N means the first string of each line is the name of the point;
*S means the 2nd string has not to be interpreted;
*X, Y, Z means that this strings number 3, 4 and 5 are the coordinates.

==Known limitations==
===GCPConverts add many decimals to coordinates===
As reported [[http://forum-micmac.forumprod.com/gcpconvert-add-many-decimals-to-coordinates-t1267.html]], GCPConvert alters slightly values during the conversion, by adding non significant decimals.
So instead of taking back this file:
<pre><?xml version="1.0" ?>
<DicoAppuisFlottant>
<OneAppuisDAF>
<Pt>301.610 939.1341 144.75</Pt>
<NamePt>30</NamePt>
<Incertitude>1 1 1</Incertitude>
</OneAppuisDAF>
<OneAppuisDAF>
<Pt>301.412 937.530 144.787</Pt>
<NamePt>31</NamePt>
<Incertitude>1 1 1</Incertitude>
</OneAppuisDAF>
</DicoAppuisFlottant></pre>
You may rather obtain this one:
<pre><?xml version="1.0" ?>
<DicoAppuisFlottant>
<OneAppuisDAF>
<Pt>301.61000000000001 939.13400000000001 144.75</Pt>
<NamePt>30</NamePt>
<Incertitude>1 1 1</Incertitude>
</OneAppuisDAF>
<OneAppuisDAF>
<Pt>301.41199999999998 937.52999999999997 144.78700000000001</Pt>
<NamePt>31</NamePt>
<Incertitude>1 1 1</Incertitude>
</OneAppuisDAF>
</DicoAppuisFlottant></pre>

Malt

2018-06-28T07:58:11Z

XavierR : /* Help */

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
Malt is a simplified interface to MicMac. Currently it can handle matching in ground geometry and ground-image geometry. Ground geometry is adapted when the scene can be described by a single function Z = f (X, Y ) (with X, Y, Z being euclidean coordinates); this case occurs quite often when the scene is relatively flat and the acquisition is made by photo acquired orthogonally to the main plane. The main use cases are:
* modelization of facades to generate ortho photo in architecture;
* modelization of earth surface from aerial acquisition;

Ground image geometry is very general and flexible and can be used in almost all acquisition. Its main drawbacks is that it requires 16 some interaction to select the master images, the mask of these images and the associated secondary images.

===Syntax===
The basic syntax requires 3 args :
<pre>mm3d Malt Type Image_Pattern Orientation</pre>

*Second arg specifies the subset of images.
*Third arg specifies the orientation.

===Allowed commands===
*Ortho
*UrbanMNE
*GeomImage

====Ortho====
For a matching adapted to ortho photo generation.
====UrbanMNE====
For a matching adapted to urban digital elevation model.
====GeomImage====
For a matching in ground image geometry.

==Help==
A basic help can be asked with
<pre> mm3d Malt -help </pre> 

Mandatory unnamed args :
*string :: {Correlation mode (must be in allowed enumerated values)}
*string :: {Full Name (Dir+Pattern)}
*string :: {Orientation}

Named args :
*[Name=Master] string :: { Master image must exist iff Mode=GeomImage, AUTO for Using result of AperoChImSecMM}
*[Name=SzW] INT :: {Correlation Window Size (1 means 3x3)}
*[Name=CorMS] bool :: {New Multi Scale correlation option, def=false, available in image geometry}
*[Name=UseGpu] bool :: {Use Cuda acceleration, def=false}
*[Name=Regul] REAL :: {Regularization factor}
*[Name=DirMEC] string :: {Subdirectory where the results will be stored}
*[Name=DirOF] string :: {Subdirectory for ortho (def in Ortho-${DirMEC}) }
*[Name=UseTA] INT :: {Use TA as Masq when it exists (Def is true)}
*[Name=ZoomF] INT :: {Final zoom, (Def 2 in ortho,1 in MNE)}
*[Name=ZoomI] INT :: {Initial Zoom, (Def depends on number of images)}
*[Name=ZPas] REAL :: {Quantification step in equivalent pixel (def=0.4)}
*[Name=Exe] INT :: {Execute command (Def is true !!)}
*[Name=Repere] string :: {Local system of coordinates}
*[Name=NbVI] INT :: {Number of Visible Images required (Def = 3)}
*[Name=HrOr] bool :: {Compute High Resolution Ortho}
*[Name=LrOr] bool :: {Compute Low Resolution Ortho}
*[Name=DirTA] string :: {Directory of TA (for mask)}
*[Name=Purge] bool :: {Purge the directory of Results before compute}
*[Name=DoMEC] bool :: {Do the Matching}
*[Name=DoOrtho] bool :: {Do the Ortho (Def=mDoMEC)}
*[Name=UnAnam] bool :: {Compute the un-anamorphosed DTM and ortho (Def context dependent)}
*[Name=2Ortho] bool :: {Do both anamorphosed ans un-anamorphosed ortho (when applyable) }
*[Name=ZInc] REAL :: {Incertitude on Z (in proportion of average depth, def=0.3) }
*[Name=DefCor] REAL :: {Default Correlation in un correlated pixels (Def=0.2)}
*[Name=CostTrans] REAL :: {Cost to change from correlation to uncorrelation (Def=2.0) }
*[Name=Etape0] INT :: {First Step (Def=1) }
*[Name=AffineLast] bool :: {Affine Last Etape with Step Z/2 (Def=true) }
*[Name=ResolOrtho] REAL :: {Resolution of ortho, relatively to images (Def=1.0; 0.5 means smaller images) }
*[Name=ImMNT] string :: {Filter to select images used for matching (Def All, usable with ortho) }
*[Name=ImOrtho] string :: {Filter to select images used for ortho (Def All) }
*[Name=ZMoy] REAL :: {Average value of Z}
*[Name=Spherik] bool :: {If true the surface for rectification is a sphere}
*[Name=WMI] REAL :: {Mininum width of reduced images (to fix ZoomInit)}
*[Name=MasqIm] string :: {Masq per Im; Def None; Use "Masq" for standard result of SaisieMasq}
*[Name=MasqImGlob] string :: {Glob Masq per Im : if uses, give full name of masq (for ex toto.tif) }
*[Name=IncMax] REAL :: {Maximum incidence of image}
*[Name=BoxClip] Box2dr :: {To Clip Computation, normalized image coordinates ([0,0,1,1] means full box)}
*[Name=BoxTerrain] Box2dr :: {([Xmin,Ymin,Xmax,Ymax])}
*[Name=ResolTerrain] REAL :: {Ground resolution (pixel size in ground unit) for ZoomF=1 (Def automatically computed)}
*[Name=RoundResol] bool :: {Use rounding of resolution (def context dependent,tuning purpose)}
*[Name=GCC] bool :: {Generate export for Cube Correlation}
*[Name=EZA] bool :: {Export Z Absolute}
*[Name=Equiv] vector<std::string> :: {Equivalent classes, as a set of pattern, def=None}
*[Name=MOri] string :: {Mode Orientation (GRID or RTO) if not XML frame camera}
*[Name=MaxFlow] bool :: {Use MaxFlow(MinCut) instead of 2D ProgDyn (SGM), slower sometime better, Def=false }
*[Name=SzRec] INT :: {Sz of overlap between computation tiles, Def=50; for some rare side effects}
*[Name=Masq3D] string :: {Name of 3D mask}
*[Name=NbProc] INT :: {Nb Proc Used}
*[Name=PSIBN] REAL :: {Penal for Automatic Selection of Images to Best Nadir (Def=-1, don't use)}
*[Name=InternalNoIncid] bool :: {Internal Use}
*[Name=PtDebug] Pt2di :: {Internal Use (Point of debuging)}

===Example===
An example with data set of Mur Saint Martin :

<pre> mm3d Malt Ortho "./IMGP41((6[7-9])|([7-8][0-9])).JPG" Basc </pre>

==Notes about DEM==

Malt generates DEMs which can be retrieve in a folder named MEC-MALT by default :
<pre> Z_NumA_DeZoomB_STD-MALT.tif </pre>
where A B dependens on the step of the computation and of the arguments of the Malt command.

Generated DEMs elevation values '''are not recorded''' in a metric unit unless you specify the '''EZA=1''' option for Malt.

The conversion values are stored in the file :
<pre>Z_NumA_DeZoomB_STD-MALT.xml </pre>

Install MicMac Windows

2018-06-28T07:27:33Z

XavierR : /* Téléchargement des derniers binaires à partir de GitHub */

French version below.

==With binaries==
===Download===
====Download last beta binaries from GitHub ====
Download the micmac_win.zip archive here :

<code>https://github.com/micmacIGN/micmac/releases</code> 
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta13/micmac_win.zip v1.0.beta13] is a 64 bits release.
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta10/micmac_win.zip v1.0.beta10] is a 32 bits one.

====Or download last "nightly" binary from AppVeyor====
Download the '''micmac_win.zip''' archive here (only for Windows 64 bits) : 

<code>https://ci.appveyor.com/project/gmaillet/micmac-uct71/build/artifacts</code>

===Installation===
Choose the 32 or 64bits version according your Windows system ("Configuration pannel/System"). Then extract the ".zip" file where you want to install MicMac.
*We recommend you to install MicMac in a directory where the path doesn't include any space or special character (i.e.: " ","&","@" etc...). The common error is to install it in "C:\Program Files (x86)" which include space.

===Set environmental path===
It is possible that you should have to indicate to your computer where the MicMac binaries are. You need to open the configuration panel -> System -> Set parameters (Screenshot 1)
[[Image:Capture ecran1.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 1]]

Then Advanced parameters -> Environnemental variable (Screenshot 2).
[[Image:Capture ecran2.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 2]]

Double-click in the path variable and add at the end (Screenshot 3): 
<code>;installation_directory\micmac\bin (for example ";C:\micmac\bin")</code>
[[Image:Capture ecran3.jpg|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 3]]

==With Setup==

*This is an old version : NOT RECOMMANDED. [[:Install_MicMac_Windows#Download_last_beta_binaries_from_GitHub| Use rather binaries from GitHub to get newer releases]].

*Download the setup from : 
<code>http://logiciels.ign.fr/?Telechargement,20</code> 
Choose the 32 or 64bits version according to your Windows system ("Configuration pannel/System"). Then, follow the differents step of the setup.
*We recommand you to install MicMac in a directory where the path doesn't include any space or special character (i.e.: " ","&","@" etc...). The common error is to install it in "C:\Program Files (x86)" which include space.

==Check Installation==
===List of micmac tools===
To check if MicMac is well installed, you can type in a terminal :
<pre>mm3d</pre>
This will return the list of all tools available for micmac library. 

===Check dependencies===
Sometimes, even when the MicMac installation is good, you can encounter messages in the terminal such as :
*"Warning Exiftool not installed"
This warnings means that MicMac can't find an external tools.
MicMac integrates a module which can check if all dependencies are correctly installed. It can be called by typing : 
<pre>
mm3d CheckDependencies
</pre>

[[Image:checkdependencies.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 4]]

You will get an output like Screenshot 4, with different informations :
*MicMac revision : micmac source code version number
*Qt : "enabled" permit you to use graphical interfaces such SaisieAppuisQT
*Kakadu : Image library for JPEG2000 management
*MicMac directory : Directory where MicMac is installed
*make :
*exiftool : library of image metadata management
*exiv2 : library of image metadata management
*convert :
*proj : library for cartographic projection
*cs2cs :

===Option : Install Exiv2===
FIXME: is this always necessary ??

*You can download the exe file from : 
<code>http://www.exiv2.org/download.html</code> 
click on "Download exiv2.exe"

*Move the "exiv2.exe" file in the MicMac binaries directory ("C:\micmac\bin")

==Known problems==

==How to use MicMac with Windows==

This video shows some basic steps on how to use MicMac on Windows.

{{#ev:youtube|https://www.youtube.com/watch?v=tezTFRanTYA|500x300px}}

=French Version : Installation MicMac pour windows=

==Avec le setup==

*Cette solution consiste à installer MicMac en téléchargeant le setup proposé sur le site de l’IGN. Attention : L’installation par setup est uniquement recommandée si la version d’installation est la plus récente disponible sur le site.

*Télécharger le setup depuis http://logiciels.ign.fr/?Micmac. Choisir la version 32 ou 64bits en fonction de son type de système. Suivre les étapes d’installation semblable aux setups des logiciels Windows.

==Avec les binaires==

===Téléchargement===
====Téléchargement des derniers binaires à partir de GitHub ====
Télécharger l'archive micmac_win.zip ici :

<code>https://github.com/micmacIGN/micmac/releases</code> 
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta13/micmac_win.zip v1.0.beta13] est une version 64 bits.
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta10/micmac_win.zip v1.0.beta10] est une version 32 bits.

====Ou télécharger les derniers binaires "instables" sur AppVeyor====
Télécharger l'archive micmac_win.zip ici (seulement pour Windows 64 bits) :

<code>https://ci.appveyor.com/project/gmaillet/micmac-uct71/build/artifacts</code>

====Ou télécharger les derniers binaires "instables" sur le site de l'IGN ====
Télécharger le binaire ici : 
<code>http://logiciels.ign.fr/?Telechargement,20</code> 

===Installation===
*Décompresser le fichier micmac_bin_windows_x86_64_rev3982.zip dans le répertoire voulu. Attention : proscrire les arborescences contenant des espaces ou/et des accents) !

*Aller dans « Panneau de configuration Système », cliquer sur « Modifier les paramètres »

*Cliquer ensuite sur « Paramètres Système Avancés » et enfin sur « Variables d’environnement. »

*Dans « Variables Système » choisir la variable « Path » et cliquer sur « Modifier ».

*Dans « Valeur de la variable », rajouter à la fin un point-virgule suivi du nom du répertoire contenant les binaires ;répertoire_des_binaires. Attention : proscrire les arborescences contenant des espaces ou/et des accents) !

*Quitter le panneau de configuration en cliquant sur OK à chaque fois.

===Vérification de l'iinstallation===

*Lancer une invite de commande (Installation_MicMac_Windows) et taper mm3d pour vérifier que tout est bien installé. La liste des commandes disponibles doit s’afficher.

*Taper ensuite : mm3d CheckDependencies

*Vérifier que tout est installé en vérifiant que chaque paquet est « found ». Si un paquet est manquant, se référer au fichier LisezMoi téléchargé avec les binaires.

==Optionnel : Installation de Exiv2==
*Se rendre sur http://www.exiv2.org/download.html puis télécharger l’éxecutable Windows en cliquant sur « Download exiv2.exe ».

*Il faut ensuite placer le fichier exiv2.exe à côté des binaires de MicMac (par défaut C:\MicMac64bits\bin)

[[Category:Installation]]

Install MicMac Windows

2018-06-28T07:26:57Z

XavierR : /* Download last beta binaries from GitHub */

French version below.

==With binaries==
===Download===
====Download last beta binaries from GitHub ====
Download the micmac_win.zip archive here :

<code>https://github.com/micmacIGN/micmac/releases</code> 
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta13/micmac_win.zip v1.0.beta13] is a 64 bits release.
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta10/micmac_win.zip v1.0.beta10] is a 32 bits one.

====Or download last "nightly" binary from AppVeyor====
Download the '''micmac_win.zip''' archive here (only for Windows 64 bits) : 

<code>https://ci.appveyor.com/project/gmaillet/micmac-uct71/build/artifacts</code>

===Installation===
Choose the 32 or 64bits version according your Windows system ("Configuration pannel/System"). Then extract the ".zip" file where you want to install MicMac.
*We recommend you to install MicMac in a directory where the path doesn't include any space or special character (i.e.: " ","&","@" etc...). The common error is to install it in "C:\Program Files (x86)" which include space.

===Set environmental path===
It is possible that you should have to indicate to your computer where the MicMac binaries are. You need to open the configuration panel -> System -> Set parameters (Screenshot 1)
[[Image:Capture ecran1.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 1]]

Then Advanced parameters -> Environnemental variable (Screenshot 2).
[[Image:Capture ecran2.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 2]]

Double-click in the path variable and add at the end (Screenshot 3): 
<code>;installation_directory\micmac\bin (for example ";C:\micmac\bin")</code>
[[Image:Capture ecran3.jpg|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 3]]

==With Setup==

*This is an old version : NOT RECOMMANDED. [[:Install_MicMac_Windows#Download_last_beta_binaries_from_GitHub| Use rather binaries from GitHub to get newer releases]].

*Download the setup from : 
<code>http://logiciels.ign.fr/?Telechargement,20</code> 
Choose the 32 or 64bits version according to your Windows system ("Configuration pannel/System"). Then, follow the differents step of the setup.
*We recommand you to install MicMac in a directory where the path doesn't include any space or special character (i.e.: " ","&","@" etc...). The common error is to install it in "C:\Program Files (x86)" which include space.

==Check Installation==
===List of micmac tools===
To check if MicMac is well installed, you can type in a terminal :
<pre>mm3d</pre>
This will return the list of all tools available for micmac library. 

===Check dependencies===
Sometimes, even when the MicMac installation is good, you can encounter messages in the terminal such as :
*"Warning Exiftool not installed"
This warnings means that MicMac can't find an external tools.
MicMac integrates a module which can check if all dependencies are correctly installed. It can be called by typing : 
<pre>
mm3d CheckDependencies
</pre>

[[Image:checkdependencies.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 4]]

You will get an output like Screenshot 4, with different informations :
*MicMac revision : micmac source code version number
*Qt : "enabled" permit you to use graphical interfaces such SaisieAppuisQT
*Kakadu : Image library for JPEG2000 management
*MicMac directory : Directory where MicMac is installed
*make :
*exiftool : library of image metadata management
*exiv2 : library of image metadata management
*convert :
*proj : library for cartographic projection
*cs2cs :

===Option : Install Exiv2===
FIXME: is this always necessary ??

*You can download the exe file from : 
<code>http://www.exiv2.org/download.html</code> 
click on "Download exiv2.exe"

*Move the "exiv2.exe" file in the MicMac binaries directory ("C:\micmac\bin")

==Known problems==

==How to use MicMac with Windows==

This video shows some basic steps on how to use MicMac on Windows.

{{#ev:youtube|https://www.youtube.com/watch?v=tezTFRanTYA|500x300px}}

=French Version : Installation MicMac pour windows=

==Avec le setup==

*Cette solution consiste à installer MicMac en téléchargeant le setup proposé sur le site de l’IGN. Attention : L’installation par setup est uniquement recommandée si la version d’installation est la plus récente disponible sur le site.

*Télécharger le setup depuis http://logiciels.ign.fr/?Micmac. Choisir la version 32 ou 64bits en fonction de son type de système. Suivre les étapes d’installation semblable aux setups des logiciels Windows.

==Avec les binaires==

===Téléchargement===
====Téléchargement des derniers binaires à partir de GitHub ====
Télécharger l'archive micmac_win.zip ici :

<code>https://github.com/micmacIGN/micmac/releases</code> 
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta11/micmac_win.zip v1.0.beta11] est une version 64 bits.
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta10/micmac_win.zip v1.0.beta10] est une version 32 bits.

====Ou télécharger les derniers binaires "instables" sur AppVeyor====
Télécharger l'archive micmac_win.zip ici (seulement pour Windows 64 bits) :

<code>https://ci.appveyor.com/project/gmaillet/micmac-uct71/build/artifacts</code>

====Ou télécharger les derniers binaires "instables" sur le site de l'IGN ====
Télécharger le binaire ici : 
<code>http://logiciels.ign.fr/?Telechargement,20</code> 

===Installation===
*Décompresser le fichier micmac_bin_windows_x86_64_rev3982.zip dans le répertoire voulu. Attention : proscrire les arborescences contenant des espaces ou/et des accents) !

*Aller dans « Panneau de configuration Système », cliquer sur « Modifier les paramètres »

*Cliquer ensuite sur « Paramètres Système Avancés » et enfin sur « Variables d’environnement. »

*Dans « Variables Système » choisir la variable « Path » et cliquer sur « Modifier ».

*Dans « Valeur de la variable », rajouter à la fin un point-virgule suivi du nom du répertoire contenant les binaires ;répertoire_des_binaires. Attention : proscrire les arborescences contenant des espaces ou/et des accents) !

*Quitter le panneau de configuration en cliquant sur OK à chaque fois.

===Vérification de l'iinstallation===

*Lancer une invite de commande (Installation_MicMac_Windows) et taper mm3d pour vérifier que tout est bien installé. La liste des commandes disponibles doit s’afficher.

*Taper ensuite : mm3d CheckDependencies

*Vérifier que tout est installé en vérifiant que chaque paquet est « found ». Si un paquet est manquant, se référer au fichier LisezMoi téléchargé avec les binaires.

==Optionnel : Installation de Exiv2==
*Se rendre sur http://www.exiv2.org/download.html puis télécharger l’éxecutable Windows en cliquant sur « Download exiv2.exe ».

*Il faut ensuite placer le fichier exiv2.exe à côté des binaires de MicMac (par défaut C:\MicMac64bits\bin)

[[Category:Installation]]

Install MicMac Windows

2017-07-06T11:39:35Z

XavierR : Fin de la msie à jour de l'installation par binaire (version fr)

French version below.
==With Setup (recommended)==

*NEW! [[:Install_MicMac_Windows#Download_last_beta_binaries_from_GitHub| Use binaries from GitHub to get newer releases]].

*Download the setup from : 
<code>http://logiciels.ign.fr/?Telechargement,20</code> 
Choose the 32 or 64bits version according to your Windows system ("Configuration pannel/System"). Then, follow the differents step of the setup.
*We recommand you to install MicMac in a directory where the path doesn't include any space or special character (i.e.: " ","&","@" etc...). The common error is to install it in "C:\Program Files (x86)" which include space.

==With binaries==
===Download===
====Download last beta binaries from GitHub ====
Download the micmac_win.zip archive here :

<code>https://github.com/micmacIGN/micmac/releases</code> 
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta11/micmac_win.zip v1.0.beta11] is a 64 bits release.
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta10/micmac_win.zip v1.0.beta10] is a 32 bits one.

====Or download last "nightly" binary from AppVeyor====
Download the '''micmac_win.zip''' archive here (only for Windows 64 bits) : 

<code>https://ci.appveyor.com/project/gmaillet/micmac-uct71/build/artifacts</code>

====Or download "stable" binaries from IGN website ====
*Download the binaries from : 
<code>http://logiciels.ign.fr/?Telechargement,20</code> 

===Installation===
Choose the 32 or 64bits version according your Windows system ("Configuration pannel/System"). Then extract the ".zip" file where you want to install MicMac.
*We recommend you to install MicMac in a directory where the path doesn't include any space or special character (i.e.: " ","&","@" etc...). The common error is to install it in "C:\Program Files (x86)" which include space.

===Set environmental path===
It is possible that you should have to indicate to your computer where the MicMac binaries are. You need to open the configuration panel -> System -> Set parameters (Screenshot 1)
[[Image:Capture ecran1.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 1]]

Then Advanced parameters -> Environnemental variable (Screenshot 2).
[[Image:Capture ecran2.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 2]]

Double-click in the path variable and add at the end (Screenshot 3): 
<code>;installation_directory\micmac\bin (for example ";C:\micmac\bin")</code>
[[Image:Capture ecran3.jpg|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 3]]

==Check Installation==
===List of micmac tools===
To check if MicMac is well installed, you can type in a terminal :
<pre>mm3d</pre>
This will return the list of all tools available for micmac library. 

===Check dependencies===
Sometimes, even when the MicMac installation is good, you can encounter messages in the terminal such as :
*"Warning Exiftool not installed"
This warnings means that MicMac can't find an external tools.
MicMac integrates a module which can check if all dependencies are correctly installed. It can be called by typing : 
<pre>
mm3d CheckDependencies
</pre>

[[Image:checkdependencies.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 4]]

You will get an output like Screenshot 4, with different informations :
*MicMac revision : micmac source code version number
*Qt : "enabled" permit you to use graphical interfaces such SaisieAppuisQT
*Kakadu : Image library for JPEG2000 management
*MicMac directory : Directory where MicMac is installed
*make :
*exiftool : library of image metadata management
*exiv2 : library of image metadata management
*convert :
*proj : library for cartographic projection
*cs2cs :

===Option : Install Exiv2===
FIXME: is this always necessary ??

*You can download the exe file from : 
<code>http://www.exiv2.org/download.html</code> 
click on "Download exiv2.exe"

*Move the "exiv2.exe" file in the MicMac binaries directory ("C:\micmac\bin")

==Known problems==

==How to use MicMac with Windows==

This video shows some basic steps on how to use MicMac on Windows.

{{#ev:youtube|https://www.youtube.com/watch?v=tezTFRanTYA|500x300px}}

=French Version : Installation MicMac pour windows=

==Avec le setup==

*Cette solution consiste à installer MicMac en téléchargeant le setup proposé sur le site de l’IGN. Attention : L’installation par setup est uniquement recommandée si la version d’installation est la plus récente disponible sur le site.

*Télécharger le setup depuis http://logiciels.ign.fr/?Micmac. Choisir la version 32 ou 64bits en fonction de son type de système. Suivre les étapes d’installation semblable aux setups des logiciels Windows.

==Avec les binaires==

===Téléchargement===
====Téléchargement des derniers binaires à partir de GitHub ====
Télécharger l'archive micmac_win.zip ici :

<code>https://github.com/micmacIGN/micmac/releases</code> 
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta11/micmac_win.zip v1.0.beta11] est une version 64 bits.
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta10/micmac_win.zip v1.0.beta10] est une version 32 bits.

====Ou télécharger les derniers binaires "instables" sur AppVeyor====
Télécharger l'archive micmac_win.zip ici (seulement pour Windows 64 bits) :

<code>https://ci.appveyor.com/project/gmaillet/micmac-uct71/build/artifacts</code>

====Ou télécharger les derniers binaires "instables" sur le site de l'IGN ====
Télécharger le binaire ici : 
<code>http://logiciels.ign.fr/?Telechargement,20</code> 

===Installation===
*Décompresser le fichier micmac_bin_windows_x86_64_rev3982.zip dans le répertoire voulu. Attention : proscrire les arborescences contenant des espaces ou/et des accents) !

*Aller dans « Panneau de configuration Système », cliquer sur « Modifier les paramètres »

*Cliquer ensuite sur « Paramètres Système Avancés » et enfin sur « Variables d’environnement. »

*Dans « Variables Système » choisir la variable « Path » et cliquer sur « Modifier ».

*Dans « Valeur de la variable », rajouter à la fin un point-virgule suivi du nom du répertoire contenant les binaires ;répertoire_des_binaires. Attention : proscrire les arborescences contenant des espaces ou/et des accents) !

*Quitter le panneau de configuration en cliquant sur OK à chaque fois.

===Vérification de l'iinstallation===

*Lancer une invite de commande (Installation_MicMac_Windows) et taper mm3d pour vérifier que tout est bien installé. La liste des commandes disponibles doit s’afficher.

*Taper ensuite : mm3d CheckDependencies

*Vérifier que tout est installé en vérifiant que chaque paquet est « found ». Si un paquet est manquant, se référer au fichier LisezMoi téléchargé avec les binaires.

==Optionnel : Installation de Exiv2==
*Se rendre sur http://www.exiv2.org/download.html puis télécharger l’éxecutable Windows en cliquant sur « Download exiv2.exe ».

*Il faut ensuite placer le fichier exiv2.exe à côté des binaires de MicMac (par défaut C:\MicMac64bits\bin)

[[Category:Installation]]

Install MicMac Windows

2017-07-06T11:24:20Z

XavierR : /* Or download last nightly binary from AppVeyor */

French version below.
==With Setup (recommended)==

*NEW! [[:Install_MicMac_Windows#Download_last_beta_binaries_from_GitHub| Use binaries from GitHub to get newer releases]].

*Download the setup from : 
<code>http://logiciels.ign.fr/?Telechargement,20</code> 
Choose the 32 or 64bits version according to your Windows system ("Configuration pannel/System"). Then, follow the differents step of the setup.
*We recommand you to install MicMac in a directory where the path doesn't include any space or special character (i.e.: " ","&","@" etc...). The common error is to install it in "C:\Program Files (x86)" which include space.

==With binaries==
===Download===
====Download last beta binaries from GitHub ====
Download the micmac_win.zip archive here :

<code>https://github.com/micmacIGN/micmac/releases</code> 
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta11/micmac_win.zip v1.0.beta11] is a 64 bits release.
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta10/micmac_win.zip v1.0.beta10] is a 32 bits one.

====Or download last "nightly" binary from AppVeyor====
Download the '''micmac_win.zip''' archive here (only for Windows 64 bits) : 

<code>https://ci.appveyor.com/project/gmaillet/micmac-uct71/build/artifacts</code>

====Or download "stable" binaries from IGN website ====
*Download the binaries from : 
<code>http://logiciels.ign.fr/?Telechargement,20</code> 

===Installation===
Choose the 32 or 64bits version according your Windows system ("Configuration pannel/System"). Then extract the ".zip" file where you want to install MicMac.
*We recommend you to install MicMac in a directory where the path doesn't include any space or special character (i.e.: " ","&","@" etc...). The common error is to install it in "C:\Program Files (x86)" which include space.

===Set environmental path===
It is possible that you should have to indicate to your computer where the MicMac binaries are. You need to open the configuration panel -> System -> Set parameters (Screenshot 1)
[[Image:Capture ecran1.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 1]]

Then Advanced parameters -> Environnemental variable (Screenshot 2).
[[Image:Capture ecran2.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 2]]

Double-click in the path variable and add at the end (Screenshot 3): 
<code>;installation_directory\micmac\bin (for example ";C:\micmac\bin")</code>
[[Image:Capture ecran3.jpg|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 3]]

==Check Installation==
===List of micmac tools===
To check if MicMac is well installed, you can type in a terminal :
<pre>mm3d</pre>
This will return the list of all tools available for micmac library. 

===Check dependencies===
Sometimes, even when the MicMac installation is good, you can encounter messages in the terminal such as :
*"Warning Exiftool not installed"
This warnings means that MicMac can't find an external tools.
MicMac integrates a module which can check if all dependencies are correctly installed. It can be called by typing : 
<pre>
mm3d CheckDependencies
</pre>

[[Image:checkdependencies.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 4]]

You will get an output like Screenshot 4, with different informations :
*MicMac revision : micmac source code version number
*Qt : "enabled" permit you to use graphical interfaces such SaisieAppuisQT
*Kakadu : Image library for JPEG2000 management
*MicMac directory : Directory where MicMac is installed
*make :
*exiftool : library of image metadata management
*exiv2 : library of image metadata management
*convert :
*proj : library for cartographic projection
*cs2cs :

===Option : Install Exiv2===
FIXME: is this always necessary ??

*You can download the exe file from : 
<code>http://www.exiv2.org/download.html</code> 
click on "Download exiv2.exe"

*Move the "exiv2.exe" file in the MicMac binaries directory ("C:\micmac\bin")

==Known problems==

==How to use MicMac with Windows==

This video shows some basic steps on how to use MicMac on Windows.

{{#ev:youtube|https://www.youtube.com/watch?v=tezTFRanTYA|500x300px}}

=French Version : Installation MicMac pour windows=

==Avec le setup==

*Cette solution consiste à installer MicMac en téléchargeant le setup proposé sur le site de l’IGN. Attention : L’installation par setup est uniquement recommandée si la version d’installation est la plus récente disponible sur le site.

*Télécharger le setup depuis http://logiciels.ign.fr/?Micmac. Choisir la version 32 ou 64bits en fonction de son type de système. Suivre les étapes d’installation semblable aux setups des logiciels Windows.

==Avec les binaires==

*Télécharger les binaires précompilés depuis http://logiciels.ign.fr/?Micmac. Choisir la bonne version 32 ou 64 bit selon votre ordinateur. (Pour connaître la version du système de son ordinateur : Démarrer/Panneau de configuration/Système).

*Décompresser le fichier micmac_bin_windows_x86_64_rev3982.zip dans le répertoire voulu. Attention : proscrire les arborescences contenant des espaces ou/et des accents) !

*Aller dans « Panneau de configuration Système », cliquer sur « Modifier les paramètres »

*Cliquer ensuite sur « Paramètres Système Avancés » et enfin sur « Variables d’environnement. »

*Dans « Variables Système » choisir la variable « Path » et cliquer sur « Modifier ».

*Dans « Valeur de la variable », rajouter à la fin un point-virgule suivi du nom du répertoire contenant les binaires ;répertoire_des_binaires. Attention : proscrire les arborescences contenant des espaces ou/et des accents) !

*Quitter le panneau de configuration en cliquant sur OK à chaque fois.

*Lancer une invite de commande (Installation_MicMac_Windows) et taper mm3d pour vérifier que tout est bien installé. La liste des commandes disponibles doit s’afficher.

*Taper ensuite : mm3d CheckDependencies

*Vérifier que tout est installé en vérifiant que chaque paquet est « found ». Si un paquet est manquant, se référer au fichier LisezMoi téléchargé avec les binaires.

==Optionnel : Installation de Exiv2==
*Se rendre sur http://www.exiv2.org/download.html puis télécharger l’éxecutable Windows en cliquant sur « Download exiv2.exe ».

*Il faut ensuite placer le fichier exiv2.exe à côté des binaires de MicMac (par défaut C:\MicMac64bits\bin)

[[Category:Installation]]

Install MicMac Windows

2017-07-06T11:23:56Z

XavierR : /* Download last beta binaries from GitHub */

French version below.
==With Setup (recommended)==

*NEW! [[:Install_MicMac_Windows#Download_last_beta_binaries_from_GitHub| Use binaries from GitHub to get newer releases]].

*Download the setup from : 
<code>http://logiciels.ign.fr/?Telechargement,20</code> 
Choose the 32 or 64bits version according to your Windows system ("Configuration pannel/System"). Then, follow the differents step of the setup.
*We recommand you to install MicMac in a directory where the path doesn't include any space or special character (i.e.: " ","&","@" etc...). The common error is to install it in "C:\Program Files (x86)" which include space.

==With binaries==
===Download===
====Download last beta binaries from GitHub ====
Download the micmac_win.zip archive here :

<code>https://github.com/micmacIGN/micmac/releases</code> 
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta11/micmac_win.zip v1.0.beta11] is a 64 bits release.
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta10/micmac_win.zip v1.0.beta10] is a 32 bits one.

====Or download last nightly binary from AppVeyor====
Download the '''micmac_win.zip''' archive here (only for Windows 64 bits) : 

<code>https://ci.appveyor.com/project/gmaillet/micmac-uct71/build/artifacts</code>

====Or download "stable" binaries from IGN website ====
*Download the binaries from : 
<code>http://logiciels.ign.fr/?Telechargement,20</code> 

===Installation===
Choose the 32 or 64bits version according your Windows system ("Configuration pannel/System"). Then extract the ".zip" file where you want to install MicMac.
*We recommend you to install MicMac in a directory where the path doesn't include any space or special character (i.e.: " ","&","@" etc...). The common error is to install it in "C:\Program Files (x86)" which include space.

===Set environmental path===
It is possible that you should have to indicate to your computer where the MicMac binaries are. You need to open the configuration panel -> System -> Set parameters (Screenshot 1)
[[Image:Capture ecran1.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 1]]

Then Advanced parameters -> Environnemental variable (Screenshot 2).
[[Image:Capture ecran2.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 2]]

Double-click in the path variable and add at the end (Screenshot 3): 
<code>;installation_directory\micmac\bin (for example ";C:\micmac\bin")</code>
[[Image:Capture ecran3.jpg|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 3]]

==Check Installation==
===List of micmac tools===
To check if MicMac is well installed, you can type in a terminal :
<pre>mm3d</pre>
This will return the list of all tools available for micmac library. 

===Check dependencies===
Sometimes, even when the MicMac installation is good, you can encounter messages in the terminal such as :
*"Warning Exiftool not installed"
This warnings means that MicMac can't find an external tools.
MicMac integrates a module which can check if all dependencies are correctly installed. It can be called by typing : 
<pre>
mm3d CheckDependencies
</pre>

[[Image:checkdependencies.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 4]]

You will get an output like Screenshot 4, with different informations :
*MicMac revision : micmac source code version number
*Qt : "enabled" permit you to use graphical interfaces such SaisieAppuisQT
*Kakadu : Image library for JPEG2000 management
*MicMac directory : Directory where MicMac is installed
*make :
*exiftool : library of image metadata management
*exiv2 : library of image metadata management
*convert :
*proj : library for cartographic projection
*cs2cs :

===Option : Install Exiv2===
FIXME: is this always necessary ??

*You can download the exe file from : 
<code>http://www.exiv2.org/download.html</code> 
click on "Download exiv2.exe"

*Move the "exiv2.exe" file in the MicMac binaries directory ("C:\micmac\bin")

==Known problems==

==How to use MicMac with Windows==

This video shows some basic steps on how to use MicMac on Windows.

{{#ev:youtube|https://www.youtube.com/watch?v=tezTFRanTYA|500x300px}}

=French Version : Installation MicMac pour windows=

==Avec le setup==

*Cette solution consiste à installer MicMac en téléchargeant le setup proposé sur le site de l’IGN. Attention : L’installation par setup est uniquement recommandée si la version d’installation est la plus récente disponible sur le site.

*Télécharger le setup depuis http://logiciels.ign.fr/?Micmac. Choisir la version 32 ou 64bits en fonction de son type de système. Suivre les étapes d’installation semblable aux setups des logiciels Windows.

==Avec les binaires==

*Télécharger les binaires précompilés depuis http://logiciels.ign.fr/?Micmac. Choisir la bonne version 32 ou 64 bit selon votre ordinateur. (Pour connaître la version du système de son ordinateur : Démarrer/Panneau de configuration/Système).

*Décompresser le fichier micmac_bin_windows_x86_64_rev3982.zip dans le répertoire voulu. Attention : proscrire les arborescences contenant des espaces ou/et des accents) !

*Aller dans « Panneau de configuration Système », cliquer sur « Modifier les paramètres »

*Cliquer ensuite sur « Paramètres Système Avancés » et enfin sur « Variables d’environnement. »

*Dans « Variables Système » choisir la variable « Path » et cliquer sur « Modifier ».

*Dans « Valeur de la variable », rajouter à la fin un point-virgule suivi du nom du répertoire contenant les binaires ;répertoire_des_binaires. Attention : proscrire les arborescences contenant des espaces ou/et des accents) !

*Quitter le panneau de configuration en cliquant sur OK à chaque fois.

*Lancer une invite de commande (Installation_MicMac_Windows) et taper mm3d pour vérifier que tout est bien installé. La liste des commandes disponibles doit s’afficher.

*Taper ensuite : mm3d CheckDependencies

*Vérifier que tout est installé en vérifiant que chaque paquet est « found ». Si un paquet est manquant, se référer au fichier LisezMoi téléchargé avec les binaires.

==Optionnel : Installation de Exiv2==
*Se rendre sur http://www.exiv2.org/download.html puis télécharger l’éxecutable Windows en cliquant sur « Download exiv2.exe ».

*Il faut ensuite placer le fichier exiv2.exe à côté des binaires de MicMac (par défaut C:\MicMac64bits\bin)

[[Category:Installation]]

Install MicMac Windows

2017-07-06T11:22:47Z

XavierR : /* Or download last nightly binary from AppVeyor */

French version below.
==With Setup (recommended)==

*NEW! [[:Install_MicMac_Windows#Download_last_beta_binaries_from_GitHub| Use binaries from GitHub to get newer releases]].

*Download the setup from : 
<code>http://logiciels.ign.fr/?Telechargement,20</code> 
Choose the 32 or 64bits version according to your Windows system ("Configuration pannel/System"). Then, follow the differents step of the setup.
*We recommand you to install MicMac in a directory where the path doesn't include any space or special character (i.e.: " ","&","@" etc...). The common error is to install it in "C:\Program Files (x86)" which include space.

==With binaries==
===Download===
====Download last beta binaries from GitHub ====
<code>https://github.com/micmacIGN/micmac/releases</code> 
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta11/micmac_win.zip v1.0.beta11] is a 64 bits release.
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta10/micmac_win.zip v1.0.beta10] is a 32 bits one.

====Or download last nightly binary from AppVeyor====
Download the '''micmac_win.zip''' archive here (only for Windows 64 bits) : 

<code>https://ci.appveyor.com/project/gmaillet/micmac-uct71/build/artifacts</code>

====Or download "stable" binaries from IGN website ====
*Download the binaries from : 
<code>http://logiciels.ign.fr/?Telechargement,20</code> 

===Installation===
Choose the 32 or 64bits version according your Windows system ("Configuration pannel/System"). Then extract the ".zip" file where you want to install MicMac.
*We recommend you to install MicMac in a directory where the path doesn't include any space or special character (i.e.: " ","&","@" etc...). The common error is to install it in "C:\Program Files (x86)" which include space.

===Set environmental path===
It is possible that you should have to indicate to your computer where the MicMac binaries are. You need to open the configuration panel -> System -> Set parameters (Screenshot 1)
[[Image:Capture ecran1.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 1]]

Then Advanced parameters -> Environnemental variable (Screenshot 2).
[[Image:Capture ecran2.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 2]]

Double-click in the path variable and add at the end (Screenshot 3): 
<code>;installation_directory\micmac\bin (for example ";C:\micmac\bin")</code>
[[Image:Capture ecran3.jpg|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 3]]

==Check Installation==
===List of micmac tools===
To check if MicMac is well installed, you can type in a terminal :
<pre>mm3d</pre>
This will return the list of all tools available for micmac library. 

===Check dependencies===
Sometimes, even when the MicMac installation is good, you can encounter messages in the terminal such as :
*"Warning Exiftool not installed"
This warnings means that MicMac can't find an external tools.
MicMac integrates a module which can check if all dependencies are correctly installed. It can be called by typing : 
<pre>
mm3d CheckDependencies
</pre>

[[Image:checkdependencies.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 4]]

You will get an output like Screenshot 4, with different informations :
*MicMac revision : micmac source code version number
*Qt : "enabled" permit you to use graphical interfaces such SaisieAppuisQT
*Kakadu : Image library for JPEG2000 management
*MicMac directory : Directory where MicMac is installed
*make :
*exiftool : library of image metadata management
*exiv2 : library of image metadata management
*convert :
*proj : library for cartographic projection
*cs2cs :

===Option : Install Exiv2===
FIXME: is this always necessary ??

*You can download the exe file from : 
<code>http://www.exiv2.org/download.html</code> 
click on "Download exiv2.exe"

*Move the "exiv2.exe" file in the MicMac binaries directory ("C:\micmac\bin")

==Known problems==

==How to use MicMac with Windows==

This video shows some basic steps on how to use MicMac on Windows.

{{#ev:youtube|https://www.youtube.com/watch?v=tezTFRanTYA|500x300px}}

=French Version : Installation MicMac pour windows=

==Avec le setup==

*Cette solution consiste à installer MicMac en téléchargeant le setup proposé sur le site de l’IGN. Attention : L’installation par setup est uniquement recommandée si la version d’installation est la plus récente disponible sur le site.

*Télécharger le setup depuis http://logiciels.ign.fr/?Micmac. Choisir la version 32 ou 64bits en fonction de son type de système. Suivre les étapes d’installation semblable aux setups des logiciels Windows.

==Avec les binaires==

*Télécharger les binaires précompilés depuis http://logiciels.ign.fr/?Micmac. Choisir la bonne version 32 ou 64 bit selon votre ordinateur. (Pour connaître la version du système de son ordinateur : Démarrer/Panneau de configuration/Système).

*Décompresser le fichier micmac_bin_windows_x86_64_rev3982.zip dans le répertoire voulu. Attention : proscrire les arborescences contenant des espaces ou/et des accents) !

*Aller dans « Panneau de configuration Système », cliquer sur « Modifier les paramètres »

*Cliquer ensuite sur « Paramètres Système Avancés » et enfin sur « Variables d’environnement. »

*Dans « Variables Système » choisir la variable « Path » et cliquer sur « Modifier ».

*Dans « Valeur de la variable », rajouter à la fin un point-virgule suivi du nom du répertoire contenant les binaires ;répertoire_des_binaires. Attention : proscrire les arborescences contenant des espaces ou/et des accents) !

*Quitter le panneau de configuration en cliquant sur OK à chaque fois.

*Lancer une invite de commande (Installation_MicMac_Windows) et taper mm3d pour vérifier que tout est bien installé. La liste des commandes disponibles doit s’afficher.

*Taper ensuite : mm3d CheckDependencies

*Vérifier que tout est installé en vérifiant que chaque paquet est « found ». Si un paquet est manquant, se référer au fichier LisezMoi téléchargé avec les binaires.

==Optionnel : Installation de Exiv2==
*Se rendre sur http://www.exiv2.org/download.html puis télécharger l’éxecutable Windows en cliquant sur « Download exiv2.exe ».

*Il faut ensuite placer le fichier exiv2.exe à côté des binaires de MicMac (par défaut C:\MicMac64bits\bin)

[[Category:Installation]]

Install MicMac Windows

2017-07-06T09:11:41Z

XavierR : Installation by Github and AppVeyor binaries

French version below.
==With Setup (recommended)==

*NEW! [[:Install_MicMac_Windows#Download_last_beta_binaries_from_GitHub| Use binaries from GitHub to get newer releases]].

*Download the setup from : 
<code>http://logiciels.ign.fr/?Telechargement,20</code> 
Choose the 32 or 64bits version according to your Windows system ("Configuration pannel/System"). Then, follow the differents step of the setup.
*We recommand you to install MicMac in a directory where the path doesn't include any space or special character (i.e.: " ","&","@" etc...). The common error is to install it in "C:\Program Files (x86)" which include space.

==With binaries==
===Download===
====Download last beta binaries from GitHub ====
<code>https://github.com/micmacIGN/micmac/releases</code> 
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta11/micmac_win.zip v1.0.beta11] is a 64 bits release.
* [https://github.com/micmacIGN/micmac/releases/download/v1.0.beta10/micmac_win.zip v1.0.beta10] is a 32 bits one.

====Or download last nightly binary from AppVeyor====
<code>https://ci.appveyor.com/project/gmaillet/micmac-uct71/build/artifacts</code> 

====Or download "stable" binaries from IGN website ====
*Download the binaries from : 
<code>http://logiciels.ign.fr/?Telechargement,20</code> 

===Installation===
Choose the 32 or 64bits version according your Windows system ("Configuration pannel/System"). Then extract the ".zip" file where you want to install MicMac.
*We recommend you to install MicMac in a directory where the path doesn't include any space or special character (i.e.: " ","&","@" etc...). The common error is to install it in "C:\Program Files (x86)" which include space.

===Set environmental path===
It is possible that you should have to indicate to your computer where the MicMac binaries are. You need to open the configuration panel -> System -> Set parameters (Screenshot 1)
[[Image:Capture ecran1.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 1]]

Then Advanced parameters -> Environnemental variable (Screenshot 2).
[[Image:Capture ecran2.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 2]]

Double-click in the path variable and add at the end (Screenshot 3): 
<code>;installation_directory\micmac\bin (for example ";C:\micmac\bin")</code>
[[Image:Capture ecran3.jpg|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 3]]

==Check Installation==
===List of micmac tools===
To check if MicMac is well installed, you can type in a terminal :
<pre>mm3d</pre>
This will return the list of all tools available for micmac library. 

===Check dependencies===
Sometimes, even when the MicMac installation is good, you can encounter messages in the terminal such as :
*"Warning Exiftool not installed"
This warnings means that MicMac can't find an external tools.
MicMac integrates a module which can check if all dependencies are correctly installed. It can be called by typing : 
<pre>
mm3d CheckDependencies
</pre>

[[Image:checkdependencies.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 4]]

You will get an output like Screenshot 4, with different informations :
*MicMac revision : micmac source code version number
*Qt : "enabled" permit you to use graphical interfaces such SaisieAppuisQT
*Kakadu : Image library for JPEG2000 management
*MicMac directory : Directory where MicMac is installed
*make :
*exiftool : library of image metadata management
*exiv2 : library of image metadata management
*convert :
*proj : library for cartographic projection
*cs2cs :

===Option : Install Exiv2===
FIXME: is this always necessary ??

*You can download the exe file from : 
<code>http://www.exiv2.org/download.html</code> 
click on "Download exiv2.exe"

*Move the "exiv2.exe" file in the MicMac binaries directory ("C:\micmac\bin")

==Known problems==

==How to use MicMac with Windows==

This video shows some basic steps on how to use MicMac on Windows.

{{#ev:youtube|https://www.youtube.com/watch?v=tezTFRanTYA|500x300px}}

=French Version : Installation MicMac pour windows=

==Avec le setup==

*Cette solution consiste à installer MicMac en téléchargeant le setup proposé sur le site de l’IGN. Attention : L’installation par setup est uniquement recommandée si la version d’installation est la plus récente disponible sur le site.

*Télécharger le setup depuis http://logiciels.ign.fr/?Micmac. Choisir la version 32 ou 64bits en fonction de son type de système. Suivre les étapes d’installation semblable aux setups des logiciels Windows.

==Avec les binaires==

*Télécharger les binaires précompilés depuis http://logiciels.ign.fr/?Micmac. Choisir la bonne version 32 ou 64 bit selon votre ordinateur. (Pour connaître la version du système de son ordinateur : Démarrer/Panneau de configuration/Système).

*Décompresser le fichier micmac_bin_windows_x86_64_rev3982.zip dans le répertoire voulu. Attention : proscrire les arborescences contenant des espaces ou/et des accents) !

*Aller dans « Panneau de configuration Système », cliquer sur « Modifier les paramètres »

*Cliquer ensuite sur « Paramètres Système Avancés » et enfin sur « Variables d’environnement. »

*Dans « Variables Système » choisir la variable « Path » et cliquer sur « Modifier ».

*Dans « Valeur de la variable », rajouter à la fin un point-virgule suivi du nom du répertoire contenant les binaires ;répertoire_des_binaires. Attention : proscrire les arborescences contenant des espaces ou/et des accents) !

*Quitter le panneau de configuration en cliquant sur OK à chaque fois.

*Lancer une invite de commande (Installation_MicMac_Windows) et taper mm3d pour vérifier que tout est bien installé. La liste des commandes disponibles doit s’afficher.

*Taper ensuite : mm3d CheckDependencies

*Vérifier que tout est installé en vérifiant que chaque paquet est « found ». Si un paquet est manquant, se référer au fichier LisezMoi téléchargé avec les binaires.

==Optionnel : Installation de Exiv2==
*Se rendre sur http://www.exiv2.org/download.html puis télécharger l’éxecutable Windows en cliquant sur « Download exiv2.exe ».

*Il faut ensuite placer le fichier exiv2.exe à côté des binaires de MicMac (par défaut C:\MicMac64bits\bin)

[[Category:Installation]]

PIMs2Mnt

2017-07-03T13:13:45Z

XavierR :

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==

In a prior step, [[PIMs]] computes depth map for each image. PIMs2Mnt merges these individual depth maps in a global digital surface (or elevation) model.
 
Name of this tool comes from "Per Image Matching" (PIM) and the french "Modèle Numérique de Terrain" (MNT) which is generally translated by "Digital Elevation Model" (DEM).

==Syntax==
The basic syntax requires an argument :
<pre>mm3d PIMs2Mnt PIMsType </pre>

===Mandatory unnamed arguments===
* string :: {Dir or PIM-Type (QuickMac ...)}

Authorized values are the same the types used with [[PIMs]] (Type in (Ground, Statue, Forest, TestIGN, QuickMac, MicMac, BigMac, MTDTmp). 
The chosen type must have been computed at the prior step with the [[PIMs|this tool]].

===Unmandatory named arguments===
* [Name=DS] REAL :: {Downscale, Def=1.0}
* [Name=ZReg] REAL :: {Regularisation, context depend}
* [Name=Repere] string :: {Repair (Euclid or Cyl)}
* [Name=Pat] string :: {Pattern, def = all existing clouds}
* [Name=DoMnt] bool :: { Compute DTM , def=true (use false to return only ortho)}
* [Name=DoOrtho] bool :: {Generate ortho photo, def=false}
* [Name=MasqImGlob] string :: {Global Masq for ortho: if used, give full name of masq (e.g. MasqGlob.tif) }
* [Name=Debug] bool :: {Debug !!!}
* [Name=UseTA] bool :: {Use TA as filter when exist (Def=false)}
* [Name=RI] REAL :: {Resol Im, def=1 }

===Help===
A basic help can be asked with
<pre> mm3d PIMs2Mnt -help </pre> 

==Workflow==
PIms2MNT is part of the new pipeline of simplified tools for dense patching and orthorectification. 

[[Image:Picto-previous.png|20px]] Previous Command : [[PIMs]] 
[[Image:Picto-next.png|20px]] Next Command : [[Tawny]].

==Example==
An example included in the [[GrandLeez|GrandLeez tutorial]] :

<pre> mm3d Pims2MNT MicMac DoOrtho=1 </pre>

==GUI==
As for other tools, arguments can be chosen through a GUI using the command:
vPIMs2MNT

==Notes about DEM==

PIMs generates DEMs which can be retrieved in the file :
<pre> ...\PIMs-TmpBasc\PIMs-Merged_Prof.tif </pre>

Generated DEM '''is not recorded''' in the coordinates system, even if it is georeferenced (with a TFW file). Difference stands in a translation and scale factor : by this way, it accommodates better the limitations of floating point precision on very high precision data.

They are stored in a local system which can be transform in the initial one using parameters specified in the file :
<pre>...\PIMs-TmpBasc\PIMs-ZNUM-Merged.xml </pre>

Example of this file:
<pre><?xml version="1.0" ?>
<FileOriMnt>
<NameFileMnt>PIMs-Merged_Prof.tif</NameFileMnt>
<NameFileMasque>PIMs-Merged_Masq.tif</NameFileMasque>
<NombrePixels>6324 8584</NombrePixels>
<OriginePlani>300.94499999999999 939.577</OriginePlani>
<ResolutionPlani>0.00050000000000000001 -0.00050000000000000001</ResolutionPlani>
<OrigineAlti>144.411</OrigineAlti>
<ResolutionAlti>0.00050000000000000001</ResolutionAlti>
<Geometrie>eGeomMNTEuclid</Geometrie>
</FileOriMnt>
</pre>

'' '''FIXME''' which parameters has to be applied? 
''- ResolutionPlani as Z scale factor? ''
''- ResolutionAlti as Z scale factor? ''
''- +OriginePlani for the XY translation? ''
''- +OrigineAlti for the Z translation?'' ''

PIMs2Mnt

2017-07-03T13:10:20Z

XavierR : Creation

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==

In a prior step, [[PIMs]] computes depth map for each image. PIMs2Mnt merges these individual depth maps in a global digital surface (or elevation) model.
 
Name of this tool comes from "Per Image Matching" (PIM) and the french "Modèle Numérique de Terrain" (MNT) which is generally translated by "Digital Elevation Model" (DEM).

==Syntax==
The basic syntax requires an argument :
<pre>mm3d PIMs2Mnt PIMsType </pre>

===Mandatory unnamed arguments===
* string :: {Dir or PIM-Type (QuickMac ...)}

Authorized values are the same the types used with [[PIMs]] (Type in (Ground, Statue, Forest, TestIGN, QuickMac, MicMac, BigMac, MTDTmp). 
The chosen type must have been computed at the prior step with the [[PIMs|this tool]].

===Unmandatory named arguments===
* [Name=DS] REAL :: {Downscale, Def=1.0}
* [Name=ZReg] REAL :: {Regularisation, context depend}
* [Name=Repere] string :: {Repair (Euclid or Cyl)}
* [Name=Pat] string :: {Pattern, def = all existing clouds}
* [Name=DoMnt] bool :: { Compute DTM , def=true (use false to return only ortho)}
* [Name=DoOrtho] bool :: {Generate ortho photo, def=false}
* [Name=MasqImGlob] string :: {Global Masq for ortho: if used, give full name of masq (e.g. MasqGlob.tif) }
* [Name=Debug] bool :: {Debug !!!}
* [Name=UseTA] bool :: {Use TA as filter when exist (Def=false)}
* [Name=RI] REAL :: {Resol Im, def=1 }

===Help===
A basic help can be asked with
<pre> mm3d PIMs2Mnt -help </pre> 

==Workflow==
PIms2MNT is part of the new pipeline of simplified tools for dense patching and orthorectification. 

[[Image:Picto-previous.png|20px]] Previous Command : [[PIMs]] 
[[Image:Picto-next.png|20px]] Next Command : [[Tawny]].

==Example==
An example included in the [[GrandLeez|GrandLeez tutorial]] :

<pre> mm3d Pims2MNT MicMac DoOrtho=1 </pre>

==GUI==
As for other tools, arguments can be chosen through a GUI using the command:
vPIMs2MNT

==Notes about DEM==

PIMs generates DEMs which can be retrieved in the file :
<pre> ...\PIMs-TmpBasc\PIMs-Merged_Prof.tif </pre>

Generated DEM '''is not recorded''' in the coordinates system, even if it is georeferenced (with a TFW file). Difference stands in a translation and scale factor : by this way, it accommodates better the limitations of floating point precision on very high precision data.

They are stored in a local system which can be transform in the initial one using parameters specified in the file :
<pre>...\PIMs-TmpBasc\PIMs-ZNUM-Merged.xml </pre>

Example of this file:
<pre><?xml version="1.0" ?>
<FileOriMnt>
<NameFileMnt>PIMs-Merged_Prof.tif</NameFileMnt>
<NameFileMasque>PIMs-Merged_Masq.tif</NameFileMasque>
<NombrePixels>6324 8584</NombrePixels>
<OriginePlani>300.94499999999999 939.577</OriginePlani>
<ResolutionPlani>0.00050000000000000001 -0.00050000000000000001</ResolutionPlani>
<OrigineAlti>144.411</OrigineAlti>
<ResolutionAlti>0.00050000000000000001</ResolutionAlti>
<Geometrie>eGeomMNTEuclid</Geometrie>
</FileOriMnt>
</pre>

'' '''FIXME''' which parameters has to be applied? 
- ResolutionPlani as Z scale factor? 
- ResolutionAlti as Z scale factor? 
- +'OriginePlani' for the XY translation? 
- +'OrigineAlti' for the Z translation?''

Malt

2017-07-03T11:22:22Z

XavierR : Rorganization, and add a paragraph about DEM

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
Malt is a simplified interface to MicMac. Currently it can handle matching in ground geometry and ground-image geometry. Ground geometry is adapted when the scene can be described by a single function Z = f (X, Y ) (with X, Y, Z being euclidean coordinates); this case occurs quite often when the scene is relatively flat and the acquisition is made by photo acquired orthogonally to the main plane. The main use cases are:
* modelization of facades to generate ortho photo in architecture;
* modelization of earth surface from aerial acquisition;

Ground image geometry is very general and flexible and can be used in almost all acquisition. Its main drawbacks is that it requires 16 some interaction to select the master images, the mask of these images and the associated secondary images.

===Syntax===
The basic syntax requires 3 args :
<pre>mm3d Malt Type Image_Pattern Orientation</pre>

*Second arg specifies the subset of images.
*Third arg specifies the orientation.

===Allowed commands===
*Ortho
*UrbanMNE
*GeomImage

====Ortho====
For a matching adapted to ortho photo generation.
====UrbanMNE====
For a matching adapted to urban digital elevation model.
====GeomImage====
For a matching in ground image geometry.

==Help==
A basic help can be asked with
<pre> mm3d Malt -help </pre> 

Mandatory unnamed args :
*string :: {Correlation mode (must be in allowed enumerated values)}
*string :: {Full Name (Dir+Pattern)}
*string :: {Orientation}

Named args :
*[Name=Master] string :: { Master image must exist iff Mode=GeomImage, AUTO for Using result of AperoChImSecMM}
*[Name=SzW] INT :: {Correlation Window Size (1 means 3x3)}
*[Name=CorMS] bool :: {New Multi Scale correlation option, def=false, available in image geometry}
*[Name=UseGpu] bool :: {Use Cuda acceleration, def=false}
*[Name=Regul] REAL :: {Regularization factor}
*[Name=DirMEC] string :: {Subdirectory where the results will be stored}
*[Name=DirOF] string :: {Subdirectory for ortho (def in Ortho-${DirMEC}) }
*[Name=UseTA] INT :: {Use TA as Masq when it exists (Def is true)}
*[Name=ZoomF] INT :: {Final zoom, (Def 2 in ortho,1 in MNE)}
*[Name=ZoomI] INT :: {Initial Zoom, (Def depends on number of images)}
*[Name=ZPas] REAL :: {Quantification step in equivalent pixel (def=0.4)}
*[Name=Exe] INT :: {Execute command (Def is true !!)}
*[Name=Repere] string :: {Local system of coordinates}
*[Name=NbVI] INT :: {Number of Visible Images required (Def = 3)}
*[Name=HrOr] bool :: {Compute High Resolution Ortho}
*[Name=LrOr] bool :: {Compute Low Resolution Ortho}
*[Name=DirTA] string :: {Directory of TA (for mask)}
*[Name=Purge] bool :: {Purge the directory of Results before compute}
*[Name=DoMEC] bool :: {Do the Matching}
*[Name=DoOrtho] bool :: {Do the Ortho (Def=mDoMEC)}
*[Name=UnAnam] bool :: {Compute the un-anamorphosed DTM and ortho (Def context dependent)}
*[Name=2Ortho] bool :: {Do both anamorphosed ans un-anamorphosed ortho (when applyable) }
*[Name=ZInc] REAL :: {Incertitude on Z (in proportion of average depth, def=0.3) }
*[Name=DefCor] REAL :: {Default Correlation in un correlated pixels (Def=0.2)}
*[Name=CostTrans] REAL :: {Cost to change from correlation to uncorrelation (Def=2.0) }
*[Name=Etape0] INT :: {First Step (Def=1) }
*[Name=AffineLast] bool :: {Affine Last Etape with Step Z/2 (Def=true) }
*[Name=ResolOrtho] REAL :: {Resolution of ortho, relatively to images (Def=1.0; 0.5 means smaller images) }
*[Name=ImMNT] string :: {Filter to select images used for matching (Def All, usable with ortho) }
*[Name=ImOrtho] string :: {Filter to select images used for ortho (Def All) }
*[Name=ZMoy] REAL :: {Average value of Z}
*[Name=Spherik] bool :: {If true the surface for rectification is a sphere}
*[Name=WMI] REAL :: {Mininum width of reduced images (to fix ZoomInit)}
*[Name=MasqIm] string :: {Masq per Im; Def None; Use "Masq" for standard result of SaisieMasq}
*[Name=MasqImGlob] string :: {Glob Masq per Im : if uses, give full name of masq (for ex toto.tif) }
*[Name=IncMax] REAL :: {Maximum incidence of image}
*[Name=BoxClip] Box2dr :: {To Clip Computation, normalized image coordinates ([0,0,1,1] means full box)}
*[Name=BoxTerrain] Box2dr :: {([Xmin,Ymin,Xmax,Ymax])}
*[Name=ResolTerrain] REAL :: {Ground Resol (Def automatically computed)}
*[Name=RoundResol] bool :: {Use rounding of resolution (def context dependent,tuning purpose)}
*[Name=GCC] bool :: {Generate export for Cube Correlation}
*[Name=EZA] bool :: {Export Z Absolute}
*[Name=Equiv] vector<std::string> :: {Equivalent classes, as a set of pattern, def=None}
*[Name=MOri] string :: {Mode Orientation (GRID or RTO) if not XML frame camera}
*[Name=MaxFlow] bool :: {Use MaxFlow(MinCut) instead of 2D ProgDyn (SGM), slower sometime better, Def=false }
*[Name=SzRec] INT :: {Sz of overlap between computation tiles, Def=50; for some rare side effects}
*[Name=Masq3D] string :: {Name of 3D Masq}
*[Name=NbProc] INT :: {Nb Proc Used}
*[Name=PSIBN] REAL :: {Penal for Automatic Selection of Images to Best Nadir (Def=-1, dont use)}
*[Name=InternalNoIncid] bool :: {Internal Use}
*[Name=PtDebug] Pt2di :: {Internal Use (Point of debuging)}

===Example===
An example with data set of Mur Saint Martin :

<pre> mm3d Malt Ortho "./IMGP41((6[7-9])|([7-8][0-9])).JPG" Basc </pre>

==Notes about DEM==

Malt generates DEMs which can be retrieve in a folder named MEC-MALT by default :
<pre> Z_NumA_DeZoomB_STD-MALT.tif </pre>
where A B dependens on the step of the computation and of the arguments of the Malt command.

Generated DEMs '''are not recorded''' in the coordinates system until you specify the '''EZA=1''' option for Malt.

They are stored in a local system which can be transform in the initial one using parameters specified in the file :
<pre>Z_NumA_DeZoomB_STD-MALT.xml </pre>

AperiCloud

2017-06-29T10:29:49Z

XavierR :

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
AperiCloud is used for generating a visualization of and sparse 3D model and cameras position, computed by [[Tapas]] for example.

===Syntax===
The global syntax for AperiCloud is :
<pre>mm3d AperiCloud FullName Orientation NamedArgs</pre>

===Results===
AperiCloud, generate a sparse 3D cloud (".ply") with the position and orientation of each camera. If you don't use "Out" option, the file will be stored in your working directory at the name : AperiCloud-Ori_Name.ply. You can use MeshLab to visualize the file. 
[[Image:01_Gravillonn_AO.jpg|x200px]]
[[Image:Pierrerue2.png|x200px]]
[[Image:Exercice_Fontaine1.png|x200px]]

===Workflow===
AperiCloud is a tool dedicated to visualization of orientations. So you can use it every times you process a orientation. When you have processed the final orientation, you can define a 3D mask with the ".ply" file generated by AperiCloud (SaisieMasqQT). 
[[Image:Picto-previous.png|20px]] Previous Command : [[Tapas]],[[GCPBascule]],[[Campari]] 
[[Image:Picto-next.png|20px]] Next Command : [[SaisieMasqQT]]. 


===Help===
You can access to the help by typing :
<pre>mm3d AperiCloud -help</pre>

Mandatory unnamed args :
*string :: {Full name (Dir+Pattern)}
*string :: {Orientation directory}
Named args :
*[Name=ExpTxt] INT :: {Point in txt format ? (Def=false)}
*[Name=Out] string :: {Result (Def=AperiCloud.ply)}
*[Name=Bin] INT :: {Ply in binary mode (Def=true)}
*[Name=RGB] INT :: {Use RGB image to texturate points (Def=true)}
*[Name=SeuilEc] REAL :: {Max residual (Def=10)}
*[Name=LimBsH] REAL :: {Limit ratio base to height (Def=1e-2)}
*[Name=WithPoints] bool :: {Do we add point cloud? (Def=true) }
*[Name=CalPerIm] bool :: {If a calibration per image was used (Def=false)}
*[Name=Focs] Pt2dr :: {Interval of Focal}
*[Name=WithCam] bool :: {With Camera (Def=true)}
*[Name=ColCadre] Pt3di :: {Col of camera rect Def= 255 0 0 (Red)}
*[Name=ColRay] Pt3di :: {Col of camera rect Def= 0 255 0 (Green)}
*[Name=SH] string :: {Set of Hom, Def="", give MasqFiltered for result of HomolFilterMasq}

===Example===

In example, you can launch this command in the Mur Saint Martin dataset :
<pre>mm3d AperiCloud «.*JPG » Out=MEP </pre>

== Known limitations ==
=== AperiCloud doesn't support 64 bits ply ===
Use of AperiCloud with coordinates with many digits generates models which seeems sliced, or very sparse, because this tool doesn't support 64 bits ply models.

Due to this limitations, it is recommended to use local or truncated coordinate. Or not to use AperiCloud after georeferencement in a projected coordinates system.
Look to [http://forum-micmac.forumprod.com/point-cloud-seems-sliced-and-very-sparse-after-coord-chgt-t1270.html| this thread] for an example and further information.

AperiCloud

2017-06-29T10:22:35Z

XavierR : 64b limitation

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
AperiCloud is used for generating a visualization of and sparse 3D model and cameras position, computed by [[Tapas]] for example.

===Syntax===
The global syntax for AperiCloud is :
<pre>mm3d AperiCloud FullName Orientation NamedArgs</pre>

===Results===
AperiCloud, generate a sparse 3D cloud (".ply") with the position and orientation of each camera. If you don't use "Out" option, the file will be stored in your working directory at the name : AperiCloud-Ori_Name.ply. You can use MeshLab to visualize the file. 
[[Image:01_Gravillonn_AO.jpg|x200px]]
[[Image:Pierrerue2.png|x200px]]
[[Image:Exercice_Fontaine1.png|x200px]]

===Workflow===
AperiCloud is a tool dedicated to visualization of orientations. So you can use it every times you process a orientation. When you have processed the final orientation, you can define a 3D mask with the ".ply" file generated by AperiCloud (SaisieMasqQT). 
[[Image:Picto-previous.png|20px]] Previous Command : [[Tapas]],[[GCPBascule]],[[Campari]] 
[[Image:Picto-next.png|20px]] Next Command : [[SaisieMasqQT]]. 


===Help===
You can access to the help by typing :
<pre>mm3d AperiCloud -help</pre>

Mandatory unnamed args :
*string :: {Full name (Dir+Pattern)}
*string :: {Orientation directory}
Named args :
*[Name=ExpTxt] INT :: {Point in txt format ? (Def=false)}
*[Name=Out] string :: {Result (Def=AperiCloud.ply)}
*[Name=Bin] INT :: {Ply in binary mode (Def=true)}
*[Name=RGB] INT :: {Use RGB image to texturate points (Def=true)}
*[Name=SeuilEc] REAL :: {Max residual (Def=10)}
*[Name=LimBsH] REAL :: {Limit ratio base to height (Def=1e-2)}
*[Name=WithPoints] bool :: {Do we add point cloud? (Def=true) }
*[Name=CalPerIm] bool :: {If a calibration per image was used (Def=false)}
*[Name=Focs] Pt2dr :: {Interval of Focal}
*[Name=WithCam] bool :: {With Camera (Def=true)}
*[Name=ColCadre] Pt3di :: {Col of camera rect Def= 255 0 0 (Red)}
*[Name=ColRay] Pt3di :: {Col of camera rect Def= 0 255 0 (Green)}
*[Name=SH] string :: {Set of Hom, Def="", give MasqFiltered for result of HomolFilterMasq}

===Example===

In example, you can launch this command in the Mur Saint Martin dataset :
<pre>mm3d AperiCloud «.*JPG » Out=MEP </pre>

== Known limitations ==
=== AperiCloud doesn't support 64 bits ply ===

Due to this limitations, it is recommended to use local or truncated coordinate. Or not to use AperiCloud after georeferencement in a projected coordinates system.
Look to [http://forum-micmac.forumprod.com/point-cloud-seems-sliced-and-very-sparse-after-coord-chgt-t1270.html|this thread] for an example and further information.

GrandLeez

2017-05-02T14:00:23Z

XavierR : fix typo

[[Image:picto-liste.png|25px|link=Tutorials]] [[Tutorials|Tutorials index]]
=Description=
This dataset will allow you to process a UAV mission a more generally a aerial mission. You will go trough direct georeferencing, GNSS delay correction, coordinate system change. We apply all this concepts to canopy model generation.

==Download==
You can find this dataset at <code>http://micmac.ensg.eu/data/uas_grand_leez_dataset.zip</code> 
Once you have downloaded it, you have to unzip the ".zip" archive.

=Presentation=
This dataset is kindly provided by "l’Unité Gestion des Ressources Forestières et des Milieux Naturels (GRFMN), Université de Liège". Contact: jo.lisein@ulg.ac.be
File present in the directory are :
*200 images : (800x600px) captured by a RICOH GR DIGITAL 3
[[Image:Carroussel_grandleez.png|x200px]]
*2 files to change coordinate system : SysCoBL72_EPSG31370.xml et SysCoRTL.xml
*Image Neighboors : FileImagesNeighbour.xml
*Image geolocation : GPS_WPK_Grand-Leez.csv
*2 commands scripts : UASGrandLeez.sh (Linux) et UASGrandLeez.bat (Windows)
*1 file with detailed commands : cmd_UAS_Grand-Leez.txt
This dataset is a UAV mission realised in GrandLeez, Belgium for forest canopy survey.

=Tutorial=
==Conversion of image coordinates==
OriConvert is used for 5 purposes:
#Conversion of the embedded GPS data into the micmac format : OriTxtInFile
#Generate the image pairs file
#Change the coordinate system (from WGS84 to a locally tangent system) with the argument : ChSys=DegreeWGS84@SysCoRTL.xml
#Compute relative speed of the camera (for GPS delay determination) : MTD1=1 CalcV=1
#Select a sample of the image block (PATC) for camera calibration : NameCple=FileImagesNeighbour.xml ImC=R0040536.JPG NbImC=25
<pre>mm3d OriConvert OriTxtInFile GPS_WPK_Grand-Leez.csv Nav-Brut-RTL ChSys=DegreeWGS84@SysCoRTL.xml MTD1=1 NameCple=FileImagesNeighbour.xml CalcV=1 ImC=R0040536.JPG NbImC=25</pre>
See [[OriConvert]] for more details on arguments and file format.

==Tie Point Generation with Tapioca==
The file FileImagesNeighbour.xml contain for each images, his differents neighboors. If you open the file, you can see :
<pre>
<Cple>R0040439.JPG R0040519.JPG</Cple>
<Cple>R0040439.JPG R0040514.JPG</Cple>
<Cple>R0040439.JPG R0040444.JPG</Cple>
<Cple>R0040439.JPG R0040517.JPG</Cple>
<Cple>R0040439.JPG R0040438.JPG</Cple>
<Cple>R0040439.JPG R0040440.JPG</Cple>
<Cple>R0040439.JPG R0040441.JPG</Cple>
<Cple>R0040439.JPG R0040516.JPG</Cple>
<Cple>R0040439.JPG R0040442.JPG</Cple>
<Cple>R0040439.JPG R0040515.JPG</Cple>
<Cple>R0040439.JPG R0040443.JPG</Cple>
</pre>
It means, image R0040439.JPG is connected with all the images detailed in <Cple> tag. So you can run the tie point generation with [[Tapioca]] using this file :
<pre>mm3d Tapioca File FileImagesNeighbour.xml -1</pre>
The processing time is shorter, because micmac knows which pictures to match.

==Camera Calibration==
To run a Camera calibration with [[Tapas]], you can take an other dataset (here using a block of 25 images), with exactly the same camera settings, or you can use a part of the principal dataset. Here we use the same images as in [[OriConvert]] to determine Internal Orientation Parameters (IOP) :
<pre>mm3d Tapas RadialBasic "R0040536.JPG|R0040537.JPG|R0040535.JPG|R0040578.JPG|R0040498.JPG|R0040499.JPG|R0040579.JPG|R0040538.JPG|R0040577.JPG|R0040534.JPG|R0040497.JPG|R0040500.JPG|R0040580.JPG|R0040456.JPG|R0040616.JPG|R0040576.JPG|R0040496.JPG|R0040617.JPG|R004045.JPG|R0040457.JPG|R0040615.JPG|R0040539.JPG|R0040501.JPG|R0040581.JPG|R0040533.JPG" Out=Sample4Calib-Rel</pre>
This is the result of the last iteration :
<pre>
| | Residual = 0.474718 ;; Evol, Moy=5.50743e-015 ,Max=3.70866e-014
| | Worst, Res 0.618139 for R0040576.JPG, Perc 99.446 for R0040496.JPG
| | Cond , Aver 6.46061 Max 42.4603 Prop>100 0
</pre>

==Orientation of the complete block in a relative system==
You can directly integrate the IOP determination in the relative orientation processing, by using [[Tapas]] and the argument InCal :
<pre>mm3d Tapas RadialBasic "R.*.JPG" Out=All-Rel InCal=Sample4Calib-Rel</pre>
This is the results of the last iteration :
<pre>
| | Residual = 0.420786 ;; Evol, Moy=3.64623e-014 ,Max=4.34387e-013
| | Worst, Res 0.662578 for R0040576.JPG, Perc 98.5075 for R0040472.JPG
| | Cond , Aver 5.84769 Max 47.5369 Prop>100 0
</pre>
<div class="toccolours mw-collapsible mw-collapsed" style="background-color: Lavender">
<h6 style="font-family: Helvetica:font-size: 40px">Go further</h6>
<div class="mw-collapsible-content">When you are using a pre-calibration in Tapas, you give a initial solution to the least squares algorithm, you improve the convergence speed/chances.
<pre>mm3d Tapas RadialBasic "R.*.JPG" Out=All-Rel-b</pre>
The results of the last iteration is :
<pre>
| | Residual = 0.420786 ;; Evol, Moy=4.39195e-013 ,Max=1.7138e-012
| | Worst, Res 0.662578 for R0040576.JPG, Perc 98.5075 for R0040472.JPG
| | Cond , Aver 5.40335 Max 52.3331 Prop>100 0
</pre>
The processing time is longer, but the residuals are the same, which prove the algortihm efficiency.
</div>
</div>

We will know compute a sparse cloud with image relative position and orientation, to check if the block is correctly computed :
<pre>mm3d AperiCloud "R.*.JPG" All-Rel</pre>
[[Image:05 ori rel.png|x300px]] 
Optionnaly, if meshlab is installed, you can vizualise the sparse cloud:
<pre>meshlab All-Rel.ply</pre>

==Absolute orientation and correction of the GNSS delay==
The position of the UAV are computed for the phase center of the GNSS which not correspond to the camera center. Moreover, the UAV is moving when you take the picture so you have to compute relative speed of each camera in order to determine and correct GNSS systematic error(delay).

First, we have to use the embedded GNSS data to set ("bascule") our system in the geographical coordinate system of choice (here a local radial tangential system - RTL) :

<pre>mm3d CenterBascule "R.*.JPG" All-Rel Nav-Brut-RTL tmp CalcV=1</pre>

Note : the target system NEEDS to be at least pseudo-euclidean (axes orthonormales). Lat/long/height is not such a system.

This is the result of the bascule
<pre>
...
BEGIN Compensation
BEGIN AMD
END AMD
APPLI APERO, NbUnknown = 1208
delay init ::: -0.0787348
...
</pre>
Here we compute a pre-absolute orientation from the relative one and we compare it to the image geolocation. The delay is estimated from the residuals and the UAV speed (here -0.0787348s).
OriConvert is (again) used for taking the delay into account and generate a new (accurate) orientation :
<pre>mm3d OriConvert OriTxtInFile GPS_WPK_Grand-Leez.csv Nav-adjusted-RTL ChSys=DegreeWGS84@SysCoRTL.xml MTD1=1 Delay=-0.0787348</pre>
Now we can use the precise georeferencing to compute the absolute orientation from the aerotriangulated model with CenterBascule
<pre>mm3d CenterBascule "R.*.JPG" All-Rel Nav-adjusted-RTL All-RTL</pre>

==Change the coordinate system==
Here we want to use the canopy model in other tools such OTB or QGIS for image segmentation/classification. So we have to backward transform our orientation coordinate system from local euclidian system to a geographic system. The tool to perform this transform is [[ChgSysCo]]. Here we transform to Belgian Lambert 72 (EPSG31370). More information about EPSG codes here : <code>http://spatialreference.org/ref/epsg/</code>
<pre>mm3d ChgSysCo "R.*JPG" All-RTL SysCoRTL.xml@SysCoBL72_EPSG31370.xml All-BL72</pre>
Compute an orientation vizualisation :
<pre>mm3d AperiCloud "R.*.JPG" All-BL72 Out=All-BL72-cam.ply WithPoints=0</pre>
The argument WithPoints, allow you to export only image position and orientation.
Optionnaly, if meshlab is installed, you can vizualise the orientation cloud :
<pre>meshlab All-BL72-cam.ply</pre>

==Canopy Surface Model==
===With Old pipeline===
Dense-matching with [[Malt]].
<pre>mm3d Malt Ortho "R.*JPG" All-BL72 DirMEC=MEC DefCor=0 AffineLast=1 Regul=0.005 HrOr=0 LrOr=0 ZoomF=1</pre>
This command line generate depth map by iteration on sub-sampling models. So we have to use the highest resolution, this is the file MEC/Z_Num8_DeZoom1_STD-MALT.tif
Here, we aren't interested in the generation of orthophoto, but we want to compute a Digital Elevation Model (DEM) for canopy survey, so we convert the depth map in 8bits
<pre>mm3d to8Bits MEC/Z_Num8_DeZoom1_STD-MALT.tif Out=Canopy_dem.tif</pre>
[[Image:Canopy DEM.png|x200px]]
 We can also export the dense point cloud and color it with [[Nuage2Ply]] :
<pre>mm3d Nuage2Ply "MEC/NuageImProf_STD-MALT_Etape_8.xml" Scale=8 Attr="Canopy_dem.tif" Out=CanopySurfaceModel.ply</pre>

One can compute the orthoimage with:
<pre>mm3d Tawny Ortho-MEC</pre>
The orthoimage will be the file Ortho-MEC/Orthophotomoisaic.tif .

Optionnaly, if meshlab is installed
<pre>meshlab CanopySurfaceModel.ply</pre>

===With New pipeline===
If you want to use the new pipeline, yo have to use [[PIMs]] and [[PIMs2MNT]] :
<pre>mm3d Pims MicMac "R.*JPG" All-BL72 DefCor=0 ZoomF=1</pre>
<pre>mm3d Pims2MNT MicMac DoOrtho=1</pre>
<pre>mm3d to8Bits PIMs-TmpBasc/PIMs-Merged_Prof.tif Out=Canopy_dem.tif</pre>
<pre>mm3d Nuage2Ply PIMs-TmpBasc/PIMs-Merged.xml Attr="Canopy_dem.tif" Out=CanopySurfaceModel.ply</pre>

Optionnaly, if meshlab is installed
<pre>meshlab CanopySurfaceModel.ply</pre>

TestKey

2017-04-25T08:54:42Z

XavierR : /* Help */

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
TestKey is a basic tool for testing a regular expression for image pattern selection.

===Syntax===
The global syntax for TestKey is :
<pre>mm3d TestKey pattern</pre>

===Results===
TestKey print on the screen which images are included in the image pattern. If the pattern isn't correct, micmac print an error message, so you can easily check if your pattern is correct or not.
By default it is limited to 10 Name, the Nb optionale parameters can increase this default value.

===Workflow===
TestKey didn't take part of any workflow, it's just a tool to test an image pattern.

===Help===
You can access to the help by typing :
<pre>mm3d TestKey -help</pre>

Mandatory unnamed args :
*string :: {Full Directory (Dir+Pattern)}
Named args :
*[Name=Nb] INT :: {Maximum number of files printed (def=10)}

===Example===
In example, you can launch this command in the Zhenjue dataset :
<pre>mm3d TestKey "DSC_313[2-9].JPG"</pre>

SaisieAppuisPredicQT

2017-04-24T09:09:34Z

XavierR :

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
It runs with the same arguments as [[SaisieAppuisInitQT]].

===Syntax===
The global syntax for SaisieAppuispredicQT is
<pre>mm3d SaisieAppuisPredicQT FullName Orientation FileForGroundControlPoints FileForImageMeasurements NamedArgs</pre>

===Help===
You can access to the help by typing :
<pre>mm3d SaisieAppuisPredicQT -help</pre>

Mandatory unnamed args :
*string :: {Full Name (Dir+Pattern)}
*string :: {Orientation}
*string :: {File for Ground Control Points}
*string :: {File for Image Measurements}

Named args :
*[Name=SzW] Pt2di :: {Size of global window (Def 800 800)}
*[Name=NbF] Pt2di :: {Number of Sub Window (Def 2 2)}
*[Name=WBlur] REAL :: {Size IN GROUND GEOMETRY of bluring for target}
*[Name=Type] string :: {in [MaxLoc,MinLoc,GeoCube]}
*[Name=ForceGray] bool :: {Force gray image, def=true}
*[Name=OriMode] string :: {Orientation type (GRID) (Def=Std)}
*[Name=ZMoy] REAL :: {Average Z, Mandatory in PB}
*[Name=ZInc] REAL :: {Incertitude on Z, Mandatory in PB}
*[Name=Masq3D] string :: {3D Masq used for visibility}
*[Name=PIMsF] string :: {PIMs filter used for visibility}
*[Name=InputSec] string :: {PIMs filter used for visibility}

===Example===
For example with the Saint-Michel de Cuxa data set :
<pre>mm3d SaisieAppuisPredicQT "Abbey-.*jpg" RTL-Init AppRTL.xml MesureFinale.xml</pre>

== Notes ==
=== XML file for image measurements ===
The last mandatory named argument is the name of an XML file where are stored points location relative to the image. But, in fact, if you specify "FileForImageMeasurements.xml" for this argument, two files will be created with slightly different names (and no one "FileForImageMeasurements.xml") :
* FileForImageMeasurements-S2D.xml, which stores points 2D coordinates inside each image;
* FileForImageMeasurements-S3D.xml, which stores points 3D coordinates, computed by spatial resection.

=== Validation of targeted points ===
In the SaisieAppuisPredicQT window, when you point a target you have to validate it by right click and "Validate" in the contextual menu to get the coordinates stored. 
Other values as "Dubious", "Refuted", "Not captured" change the color of the target and [http://forum-micmac.forumprod.com/saisieappuispredicqt-attributes-of-gcp-t1409.html| seems to have the same effect] as a reverse of the validation.

SaisieAppuisInitQT

2017-04-24T09:08:28Z

XavierR :

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
It runs with the same arguments as [[SaisieAppuisInit]].
SaisieAppuisInitQT displays two lists on the right side: the points list, and the images list. Points list can be clicked to choose which point to measure. You can also remove a point by clicking it in the list and press Suppr. You can also right-click and choose between following actions:
*Change images for selected point
*Delete selected points (multiple selection allowed)
*Validate selected points (idem)

The image lists show all available images. When a point has been measured in at least two images, the image list is displayed. Images currently displayed in the windows are highlighted in blue. The image where the cursor is moving is displayed in light orange. You can right-click and select View images to load corresponding images. A 3D window shows the images location, and the point measured. By default point are displayed in red ; when a point is selected, it is displayed in blue. You can drag-and-drop a ply file in this window (such as [[AperiCloud]].ply) to check if GCP are good.

===Syntax===
The global syntax for SaisieAppuisInitQT is :
<pre>mm3d SaisieAppuisInitQT FullName Orientation PointName FileForImageMeasurements NamedArgs </pre>

===Help===
You can access to the help by typing :
<pre>mm3d SaisieAppuisInitQT -help</pre>
Mandatory unnamed args :
*string :: {Full name (Dir+Pattern)}
*string :: {Orientation ; NONE if not used}
*string :: {Point name, or point file name}
*string :: {File for image measurement}

Named args :
*[Name=SzW] Pt2di :: {Sz of window}
*[Name=NbF] Pt2di :: {Nb of sub window}
*[Name=NameAuto] string :: {Prefix for automatic point creation}
*[Name=ForceGray] bool :: {Force gray image, def=false}
*[Name=OriMode] string :: {Orientation type (GRID) (Def=Std)}
*[Name=ZMoy] REAL :: {Average Z, Mandatory in PB}
*[Name=ZInc] REAL :: {Incertitude on Z, Mandatory in PB}

Example:
* <pre> mm3d SaisieAppuisInitQT IMG_558{0-9}[1].tif RadialBasic 100 measures.xml </pre>
*'NB: visual interface for argument edition available with command:
<pre> mm3d vSaisieAppuisInitQT </pre>

===Example===
For example with the Saint-Michel de Cuxa data set :

*<pre>SaisieAppuisInitQT "Abbey-IMG_(021[12]|023[3456]).jpg" All-Rel NamePointInit.txt MesureInit.xml </pre>

A visual interface for argument edition is also available with command:
*<pre>mm3d vSaisieAppuisInitQT} or mm3d vSaisieAppuisPredicQT</pre>

== Video tutorial and notes ==

=== How to use SaisieAppuisInitQT explained in this tutorial ===
{{#ev:youtube|https://www.youtube.com/watch?v=fz7NXFg9770}}

=== XML file for image measurements ===
The last mandatory named argument is the name of an XML file where are stored points location relative to the image. But, in fact, if you specify "MesureInit.xml" for this argument, two files will be created with slightly different names (and no one "FileForImageMeasurements.xml") :
* MesureInit-S2D.xml, which stores points 2D coordinates inside each image;
* MesureInit-S3D.xml, which stores points 3D coordinates, computed by spatial resection.

=== Validation of targeted points ===
In the SaisieAppuisInitQt window, when you point a target you have to validate it by right click and "Validate" in the contextual menu to get the coordinates stored. 
Other values as "Dubious", "Refuted", "Not captured" change the color of the target and [http://forum-micmac.forumprod.com/saisieappuispredicqt-attributes-of-gcp-t1409.html| seems to have the same effect] as a reverse of the validation.

SaisieAppuisPredicQT

2017-04-24T08:55:16Z

XavierR : /* Notes */

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
It runs with the same arguments as [[SaisieAppuisInitQT]].

===Syntax===
The global syntax for SaisieAppuispredicQT is
<pre>mm3d SaisieAppuisPredicQT FullName Orientation FileForGroundControlPoints FileForImageMeasurements NamedArgs</pre>

===Help===
You can access to the help by typing :
<pre>mm3d SaisieAppuisPredicQT -help</pre>

Mandatory unnamed args :
*string :: {Full Name (Dir+Pattern)}
*string :: {Orientation}
*string :: {File for Ground Control Points}
*string :: {File for Image Measurements}

Named args :
*[Name=SzW] Pt2di :: {Size of global window (Def 800 800)}
*[Name=NbF] Pt2di :: {Number of Sub Window (Def 2 2)}
*[Name=WBlur] REAL :: {Size IN GROUND GEOMETRY of bluring for target}
*[Name=Type] string :: {in [MaxLoc,MinLoc,GeoCube]}
*[Name=ForceGray] bool :: {Force gray image, def=true}
*[Name=OriMode] string :: {Orientation type (GRID) (Def=Std)}
*[Name=ZMoy] REAL :: {Average Z, Mandatory in PB}
*[Name=ZInc] REAL :: {Incertitude on Z, Mandatory in PB}
*[Name=Masq3D] string :: {3D Masq used for visibility}
*[Name=PIMsF] string :: {PIMs filter used for visibility}
*[Name=InputSec] string :: {PIMs filter used for visibility}

===Example===
For example with the Saint-Michel de Cuxa data set :
<pre>mm3d SaisieAppuisPredicQT "Abbey-.*jpg" RTL-Init AppRTL.xml MesureFinale.xml</pre>

== Notes ==
=== XML file for image measurements ===
The last mandatory named argument is the name of an XML file where are stored points location relative to the image. But, in fact, if you specify "FileForImageMeasurements.xml" for this argument, two files will be created with slightly different names (and no one "FileForImageMeasurements.xml") :
* FileForImageMeasurements-S2D.xml, which stores points 2D coordinates inside each image;
* FileForImageMeasurements-S3D.xml, which stores points 3D coordinates, computed by spatial resection.

=== Validation of targeted points ===
In the SaisieAppuisPredicQT window, when you point a target you have to validate it by right click and "Validate" in the contextual menu to get the coordinates stored.
Other values as "Dubious", "Refuted", "Not captured" [http://forum-micmac.forumprod.com/saisieappuispredicqt-attributes-of-gcp-t1409.html| seems to have the same effect] as a reverse of the validation.

SaisieAppuisInitQT

2017-04-24T08:54:40Z

XavierR : Add notes about S2D S3D files and "Dubious", "Refuted", "Not captured" attributes

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
It runs with the same arguments as [[SaisieAppuisInit]].
SaisieAppuisInitQT displays two lists on the right side: the points list, and the images list. Points list can be clicked to choose which point to measure. You can also remove a point by clicking it in the list and press Suppr. You can also right-click and choose between following actions:
*Change images for selected point
*Delete selected points (multiple selection allowed)
*Validate selected points (idem)

The image lists show all available images. When a point has been measured in at least two images, the image list is displayed. Images currently displayed in the windows are highlighted in blue. The image where the cursor is moving is displayed in light orange. You can right-click and select View images to load corresponding images. A 3D window shows the images location, and the point measured. By default point are displayed in red ; when a point is selected, it is displayed in blue. You can drag-and-drop a ply file in this window (such as [[AperiCloud]].ply) to check if GCP are good.

===Syntax===
The global syntax for SaisieAppuisInitQT is :
<pre>mm3d SaisieAppuisInitQT FullName Orientation PointName FileForImageMeasurements NamedArgs </pre>

===Help===
You can access to the help by typing :
<pre>mm3d SaisieAppuisInitQT -help</pre>
Mandatory unnamed args :
*string :: {Full name (Dir+Pattern)}
*string :: {Orientation ; NONE if not used}
*string :: {Point name, or point file name}
*string :: {File for image measurement}

Named args :
*[Name=SzW] Pt2di :: {Sz of window}
*[Name=NbF] Pt2di :: {Nb of sub window}
*[Name=NameAuto] string :: {Prefix for automatic point creation}
*[Name=ForceGray] bool :: {Force gray image, def=false}
*[Name=OriMode] string :: {Orientation type (GRID) (Def=Std)}
*[Name=ZMoy] REAL :: {Average Z, Mandatory in PB}
*[Name=ZInc] REAL :: {Incertitude on Z, Mandatory in PB}

Example:
* <pre> mm3d SaisieAppuisInitQT IMG_558{0-9}[1].tif RadialBasic 100 measures.xml </pre>
*'NB: visual interface for argument edition available with command:
<pre> mm3d vSaisieAppuisInitQT </pre>

===Example===
For example with the Saint-Michel de Cuxa data set :

*<pre>SaisieAppuisInitQT "Abbey-IMG_(021[12]|023[3456]).jpg" All-Rel NamePointInit.txt MesureInit.xml </pre>

A visual interface for argument edition is also available with command:
*<pre>mm3d vSaisieAppuisInitQT} or mm3d vSaisieAppuisPredicQT</pre>

== Video tutorial and notes ==

=== How to use SaisieAppuisInitQT explained in this tutorial ===
{{#ev:youtube|https://www.youtube.com/watch?v=fz7NXFg9770}}

=== XML file for image measurements ===
The last mandatory named argument is the name of an XML file where are stored points location relative to the image. But, in fact, if you specify "MesureInit.xml" for this argument, two files will be created with slightly different names (and no one "FileForImageMeasurements.xml") :
* MesureInit-S2D.xml, which stores points 2D coordinates inside each image;
* MesureInit-S3D.xml, which stores points 3D coordinates, computed by spatial resection.

=== Validation of targeted points ===
In the SaisieAppuisInitQt window, when you point a target you have to validate it by right click and "Validate" in the contextual menu to get the coordinates stored.
Other values as "Dubious", "Refuted", "Not captured" change the color of the target and [http://forum-micmac.forumprod.com/saisieappuispredicqt-attributes-of-gcp-t1409.html| seems to have the same effect] as a reverse of the validation.

SaisieAppuisPredicQT

2017-04-24T08:18:56Z

XavierR : Add notes about S2D S3D files and "Dubious", "Refuted", "Not captured" attributes

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
It runs with the same arguments as [[SaisieAppuisInitQT]].

===Syntax===
The global syntax for SaisieAppuispredicQT is
<pre>mm3d SaisieAppuisPredicQT FullName Orientation FileForGroundControlPoints FileForImageMeasurements NamedArgs</pre>

===Help===
You can access to the help by typing :
<pre>mm3d SaisieAppuisPredicQT -help</pre>

Mandatory unnamed args :
*string :: {Full Name (Dir+Pattern)}
*string :: {Orientation}
*string :: {File for Ground Control Points}
*string :: {File for Image Measurements}

Named args :
*[Name=SzW] Pt2di :: {Size of global window (Def 800 800)}
*[Name=NbF] Pt2di :: {Number of Sub Window (Def 2 2)}
*[Name=WBlur] REAL :: {Size IN GROUND GEOMETRY of bluring for target}
*[Name=Type] string :: {in [MaxLoc,MinLoc,GeoCube]}
*[Name=ForceGray] bool :: {Force gray image, def=true}
*[Name=OriMode] string :: {Orientation type (GRID) (Def=Std)}
*[Name=ZMoy] REAL :: {Average Z, Mandatory in PB}
*[Name=ZInc] REAL :: {Incertitude on Z, Mandatory in PB}
*[Name=Masq3D] string :: {3D Masq used for visibility}
*[Name=PIMsF] string :: {PIMs filter used for visibility}
*[Name=InputSec] string :: {PIMs filter used for visibility}

===Example===
For example with the Saint-Michel de Cuxa data set :
<pre>mm3d SaisieAppuisPredicQT "Abbey-.*jpg" RTL-Init AppRTL.xml MesureFinale.xml</pre>

== Notes ==
=== XML file for image measurements ===
The last mandatory named argument is the name of an XML file where are stored points location relative to the image. But, in fact, if you specify "FileForImageMeasurements.xml" for this argument, two files will be created with slightly different names (and no one "FileForImageMeasurements.xml") :
* FileForImageMeasurements-S2D.xml, which stores points 2D coordinates inside each image;
* FileForImageMeasurements-S3D.xml, which stores points 3D coordinates, computed by spatial resection.

=== Validation of targeted points ===
In the SaisieAppuisInitQt window, when you point a target you have to validate it by right click and "Validate" in the contextual menu to get the coordinates stored.
Other values as "Dubious", "Refuted", "Not captured" [http://forum-micmac.forumprod.com/saisieappuispredicqt-attributes-of-gcp-t1409.html| seems to have the same effect] as a reverse of the validation.

SaisieAppuisPredicQT

2017-04-24T07:22:02Z

XavierR : Fix typo and add internal link

Schnaps

2016-12-08T10:09:30Z

XavierR : fix typo + option ShowStat

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==

Schnaps is a global order-agnostic tie point reduction tool.

This command is used to clean and reduce tie points before any orientation, and without needing any order in the pictures. Its limitation is the user memory: it can't be used if computer RAM is lower than Homol directory size.

===Syntax===
The global syntax for Schnaps is :
<pre>mm3d Schnaps ImagePattern</pre>

===Workflow===
AperiCloud is a tool dedicated to tie point reduction. So you have to use it after tie points computation by Tapioca and before orientation computation by Tapas (or Martini). It could also be used after a first tiepoint reduction using mask(s) with HomolFilterMasq 
[[Image:Picto-previous.png|20px]] Previous Command : [[Tapioca]],[[HomolFilterMasq]] 
[[Image:Picto-next.png|20px]] Next Command : [[Tapas]],[[Martini]]. 


===Help===
You can access to the help by typing :
<pre>mm3d Schnaps -help</pre>

Mandatory unnamed args :
* string :: {Pattern of images}
Named args :
* [Name=HomolIn] string :: {Input Homol directory suffix (without "Homol")}
* [Name=NbWin] INT :: {Minimal homol points in each picture (default: 1000)}
* [Name=HomolOut] string :: {Output Homol directory suffix (default: _mini)}
* [Name=ExpTxt] bool :: {Ascii format for in and out, def=false}
* [Name=VeryStrict] bool :: {Be very strict with homols (remove any suspect),def=false}
* [Name=ShowStats] bool :: {Show Homol points stats before and after filtering, def=false}
* [Name=PoubelleName] string :: {Where to write suspicious pictures names, def="Schnaps_poubelle.txt"}
* [Name=minPercentCoverage] REAL :: {Minimum % of coverage to avoid adding to poubelle, def=30}

==Examples==

===Basic Example===
You can launch this command on most dataset with :
<pre>mm3d Schnaps «.*JPG »</pre>

By default Schnaps uses the \Homol" directory and creates a "\Homol_mini" directory for output, which will have to be specified in following commands, generally with SH argument. For example, with Tapas:
<pre>mm3d Tapas RadialExtended ".*JPG" SH=_mini</pre>

===After HomolFilterMasq===
Here, you have to specify the good homol directory. If you used default settings, it should be:
<pre>mm3d Schnaps ".*JPG" HomolIn=MasqFiltered</pre>

==Known limitations==
===ShowStats=True===
This option get the computation process very very slow. Don't use if you don't need it.

Denis Jouin

2016-12-08T08:38:45Z

XavierR : Lien vers GitHub

Denis Jouin travaille au CEREMA Normandie Centre, au sein du Laboratoire Régional de Rouen.

Il a réalisé en 2015/2016 une interface graphique pour MicMac.

Cette interface, AperoDeDenis, est disponible sur la forge de MicMac sous le répertoire "Interface CEREMA"[https://github.com/micmacIGN/InterfaceCEREMA].

Install MicMac Ubuntu

2016-12-08T08:34:58Z

XavierR : MicMac is now hosted on GitHub

MicMac is an open source project and you can download the source code and compile the project yourself. This page presents the steps of the installation on a Linux system using apt-get (such as Ubuntu), but similar steps work on other systems.

Beware : the code available in the latest revision might not be stable or might not compile in a given OS.

== Get the source ==

'''FIXME''': MicMac is now hosted on '''GitHub[[https://github.com/micmacIGN/micmac]]'''.

=== Install mercurial (obsolete)===
The MicMac project is hosted by a mercurial repository, so first you have to install mercurial.
<pre>sudo apt-get install mercurial</pre>

=== Download the source (obsolete)===
Go to the installation directory, where you want to install MicMac then launch
<pre>
hg clone https://geoportail.forge.ign.fr/hg/culture3d
login: culture3d
pswd: culture3d
</pre>
It can take some times.

== Build from sources ==
=== Classic installation ===
From the installation directory, move to the 'culture3d' directory :
<pre>cd culture3d</pre>
Then, you have to create a build directory and go in it :
<pre>
mkdir build
cd build
</pre>
Then we have to generate the makefile with the right options. To generate the defaut makefile, run :
<pre>cmake ..</pre>
Now we can finally build the sources by launching :
<pre>
make install -jK
</pre>
Where K="number of processor in your computer" (if you are not sure how many cores you have, just write a big number and all of the cores will be used).

=== With Qt tools ===
If you want to use tools GUI such : SaisieAppuisInitQT, SaisieMasqQT etc... Use instead :
<pre>cmake -DWITH_QT5=1 ../</pre>
You have perhaps to install QT if it's not done :
<pre>sudo apt-get install qt5-default qttools5-dev-tools</pre>
NB : Version 5 is used here, use "-DWITH_QT4=1" instead if ou have QT v4.
Then you can run the normal process, see above.

==Add MicMac to path==
We have now to edit the file wich contains environnement path which is located in "/etc/bash.bashrc". The file is maybe hidden, so press CTRL+H, or activate "Hidden files" in Display (Top bar).
So open a terminal and type :
<pre>
sudo gedit /etc/bash.bashrc
</pre>
NB : files in "/etc/" have to be opened in super user mode. 
Add the following lines at the bottom of the file : 
<code>export PATH=/''micmac_install_directory''/culture3d/bin:$PATH</code>

==Check Installation==
===List of MicMac tools===
To check if MicMac is well installed, you can type in a terminal :
<pre>mm3d</pre>
This will return the list of all tools available for micmac library. 

===Check dependencies===
Sometimes, even when the MicMac installation is good, you can encounter messages in the terminal such as :
*"Warning Exiftool not installed"
This warnings means that MicMac can't find an external tools.
MicMac integrates a module which can check if all dependencies are correctly installed. It can be called by typing : 
<pre>
mm3d CheckDependencies
</pre>

[[Image:checkdependencies.png|thumb|250px||alt=Exemple d'image en hauteur|Screenshot 1]]

You will get an output like Screenshot 1, with different informations :
*MicMac revision : micmac source code version number
*Qt : "enabled" permit you to use graphical interfaces such SaisieAppuisQT
*Kakadu : Image library for JPEG2000 management
*MicMac directory : Directory where MicMac is installed
*make :
*exiftool : library of image metadata management
*exiv2 : library of image metadata management
*convert :
*proj : library for cartographic projection
*cs2cs :

== Update sources ==
To update the sources, go in the installtion directory ("installation_directory/culture3d") and type:
<pre>
hg pull https://geoportail.forge.ign.fr/hg/culture3d
login: culture3d
pswd: culture3d
</pre>
Then upload the sources with the command:
<pre>
hg update
</pre>

You have now to build again the sources:
<pre>
cd build
cmake ..
make install -j8
</pre>
NB : if you want still use QT, don't forget to use <code>cmake -DWITH_QT5=1 ../</code>

== Troubleshooting ==
=== Errors with cmake ===
*<code>...Could NOT find OpenGL (missing: OPENGL_gl_LIBRARY OPENGL_INCLUDE_DIR)...</code> => Try to install Qt

[[Category:Installation]]

OriExport

2016-11-24T08:50:15Z

XavierR : Fix typo

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
The tool OriExport can convert MicMac external orientation to the de facto standard codification using omega-phi-kappa. For now it's quite basic and all the options are not implemented. However, it should solve the majority of problem relative to exporting results in classical photogrammetric softwares.

===Syntax===
The global syntax for OriExport is :
<pre>mm3d OriExport FullName Results NamedArgs</pre>

===Help===
You can access to the help by typing :
<pre>mm3d OriExport -help</pre>

Mandatory unnamed args :
* string :: {Full Directory (Dir+Pattern)}
* string :: {Results}
Named args :
* [Name=AddF] bool :: {Add format as first line of header, def= false}
* [Name=ModeExp] string :: {Mode export, def=WPK (Omega Phi Kapa)}

==Example==
An example with Cuxha data set :
<pre>mm3d OriExport Ori-All-Rel/Orientation-Abbey-IMG_034.*.jpg.xml res.txt</pre>

==Formalism==
===Output===
OriExport will generate the file res.txt containinig :
<pre>
Abbey-IMG_0340.jpg -4.304443 11.785803 136.229854 -5.491274 2.702560 -0.004106
Abbey-IMG_0341.jpg -3.775959 11.249636 137.040260 -6.109496 2.042527 0.097497
Abbey-IMG_0342.jpg -3.849398 11.231276 137.533559 -6.707432 1.351133 0.224315
Abbey-IMG_0343.jpg -3.921196 11.302498 137.899618 -7.334180 0.668316 0.362218
</pre>
Which correspond to :
<pre>ImageName X Y Z omega phi kappa</pre>
NB : The image coordinates are exported in the system you have chosen (often a local euclidean frame).

===Rotation matrix===
Matrix R gives rotation terms to compute parameters in matrix encoding with respect to omega-phi-kappa
angles given by the tool OriExport.

\begin{equation}
R=
\begin{pmatrix}
\cos(\phi)\cos(\kappa) & \cos(\phi)\sin(\kappa) & -\sin(\phi)\\
\cos(\omega)\sin(\kappa) + \sin(\omega)\sin(\phi)\cos(\kappa) & -\cos(\omega)\cos(\kappa) + \sin(\omega)\sin(\phi)\sin(\kappa) & \sin(\omega)\cos(\phi)\\
\sin(\omega)\sin(\kappa)-\cos(\omega)\sin(\phi)\cos(\kappa) & -\sin(\omega)\cos(\kappa)-\cos(\omega)\sin(\phi)\sin(\kappa) & -\cos(\omega)\cos(\phi)
\end{pmatrix}
\end{equation}

For example OriExport will give in degree:\\
\begin{equation}
\omega = 5.819826\\
\phi = 7.058795\\
\kappa = 12.262634
\end{equation}

The corresponding matrix encoding using R is:
<pre>
<ParamRotation>
<CodageMatr>
<L1>0.969777798578237427 -0.210783330505758815 0.122887790140630643</L1>
<L2>-0.199121821850641506 -0.974794184828703614 -0.100631989382226852</L2>
<L3>0.141001849092942777 0.0731210284736428379 -0.987305319416100224</L3>
</CodageMatr>
</ParamRotation>
</pre>

XifGps2Txt

2016-11-24T08:39:08Z

XavierR : Fix typo and errors

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
Often the GPS information is not in separate files but directly embedded in the EXIF metadata. The tools
[[XifGps2Xml]] and [[XifGps2Txt]] allow to do extract this information and convert it to text or XML file.

===Syntax===
The global syntax for XifGps2Txt is :
<pre>mm3d XifGps2Txt FullName NamedArgs</pre>

===Help===
You can access to the help by typing :
<pre>mm3d XifGps2Txt -help</pre>

====Mandatory unnamed args====
* string :: {Full Name}
====Named args====
* [Name=OutTxtFile] string :: {Def file created : ’GpsCoordinatesFromExif.txt’ }
* [Name=Sys] string :: {System to express output coordinates : WGS84_deg/WGS84_rad/GeoC ; Def=WGS84_deg}
* [Name=DefZ] REAL

If there is no GPS data into EXIF metadata, the output file will be created as an empty file.

===Example===
For example, with :
<pre>mm3d XifGps2Txt .*jpg</pre>
It returns the GpsCoordinatesFromExif.txt file:
<pre>2016-04-02_12-22-07.jpg 1.908783 47.902767 161.000000
2016-04-02_12-22-18.jpg 1.908758 47.902861 161.000000
2016-04-02_12-22-29.jpg 1.908717 47.902964 159.000000
2016-04-02_12-22-56.jpg 1.908556 47.902828 154.000000
2016-04-02_12-23-07.jpg 1.908506 47.902789 157.000000
2016-04-02_12-23-12.jpg 1.908511 47.902722 157.000000
...
</pre>

XifGps2Xml

2016-11-24T08:12:04Z

XavierR : Fix typo

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
Often the GPS information is not in separate files but directly embedded in the EXIF metadata. The tools
[[XifGps2Xml]] and [[XifGps2Txt]] allow to do extract this information and convert it to text or XML file.

===Syntax===
The global syntax for XifGps2Xmlt is :
<pre>mm3d XifGps2Xml FullName Orientation NamedArgs</pre>

===Help===
You can access to the help by typing :
<pre>mm3d XifGps2Xml -help</pre>

====Mandatory unnamed args :====
* string :: {Full Name}
* string :: {Orientation}
====Named args :====
* [Name=DoRTL] bool :: {Do Local Tangent RTL (def=true)}
* [Name=RTL] string :: {Name RTL}
* [Name=SysCo] string :: {System of coordinates, by default RTL created (RTLFromExif.xml)}
* [Name=DefZ] REAL

====Options :====
* DoRTL : Transform the coordinate in RTL.
* RTL : Name of the file which define the RTL.
* DefZ : Will allow to specify the altitude value, not implemanted for now.
* SysCo : Allow to change the coordinate system.

===Example===
For example, with :
<pre>mm3d XifGps2Xml .*jpg Test</pre>
* For each image, containing GPS data in EXIF, a file is created containing the GPS information in XML MicMac format.
* For example for Image100.jpg, Ori-Test/Orientation-Image100.jpg.xml is created, in XML MicMac format.
* The coordinate system is a local tangent sytem, with origin at center of images.
* The file RTLFromExif.xml contains the definition of this system in MicMac format.

Tapioca

2016-11-15T09:25:14Z

XavierR : /* Workflow */

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
Tapioca is a simple tool interface for computing tie points. I think Tapioca should be sufficient in 95% of cases. If it is not the case, you will have to refer to a more complex and powerful tool named [[Pastis]] which will be described later. In fact, Tapioca is only an interface to [[Pastis]].

===Syntax===
The global syntax for Tapioca is 
<pre>mm3d Tapioca UnNamedArgs NamedArgs</pre>

===Allowed commands===
*MulScale : Compute tie points for images in low resolution and then for high resolution.
*All : Compute tie points for all images in a given resolution.
*Line : Compute tie points for linear image canvas.
*File :
*Graph :

===Results===
Tapioca generate a directory named "Homol" ("Homol_SRes" for Tapioca MulScale) in your working directory which contain for each image of your canvas, a directory named "PastisImage_name". In this directory "Pastis" you will find a binary file (".dat") for each image linked with the first image by tie points. This binary files contains tie points. 
For example, in Gravillons dataset, all images are linked so this is the arborescence of the Gravillon Homol directory : 
[[Image:Tapioca_homol_arborescence.png|500px]]

===Workflow===
Tapioca, is generally the first command to launch in a MicMac process. 
[[Image:Picto-previous.png|20px]] Previous Command : ~ 
[[Image:Picto-next.png|20px]] Next Command : ([[HomolFilterMasq]],[[Schnaps]],) [[Tapas]].

===Visualize tie points===
NB : This tool works only for Linux OS. 
If you want to visualize tie points matched by Tapioca, you can run the command [[SEL]]:
<pre>mm3d SEL image_1 image_2 KH=NB</pre>
[[Image:tapioca_exemple_sift.png|x200px]]

==Tie points computation mode==
===All===
Tie points are looked for in all possible pair of images at the reduced resolution chosen by the user in the ''Size of image'' option.

====Help====
You can access to the help by typing :
<pre>mm3d Tapioca All -help</pre>

Mandatory unnamed args :
*string :: {Full Name (Dir+Pat)}
*INT :: {Size of image, in pixels}

Named args :
*[Name=ExpTxt] INT :: {Export files in text format (Def=false means binary)}
*[Name=PostFix] string :: {Add postfix in directory}
*[Name=ByP] INT :: {By process}
*[Name=Pat2] string :: {Second pattern}
*[Name=Detect] string
*[Name=Match] string
*[Name=NoMax] bool
*[Name=NoMin] bool
*[Name=NoUnknown] bool

Using '''-1''' as Image's size is equivalent to use full resolution image. But it's recommended to use rather a resolution to a scaling between 0.3 and 0.5.

====Example====
For example with the Ramses dataset, you can launch : 
<pre>mm3d Tapioca All "IMG.*CR2" 1000</pre>

For example with the Zhenjue dataset, you can launch : 
<pre>mm3d Tapioca All ".*JPG" 1500</pre>

===MulScale===
The mode MulScale can save significant computation time on large sets of images. Even if it is not optimal for all canvas, it has the benefit of being general and usable with any data set. In this mode, a first computation of tie points is made for all the pairs of images at a low resolution (so it is quite fast), chosen by the user through the ''Size of Low Resolution Images'' option. Then the computation is done at the ''Size of High Resolution Images'' only for the pairs having, at low resolution, a number of tie points exceeding a given threshold (''NbMinPt'').

====Help====
You can access to the help by typing :
<pre>mm3d Tapioca MulScale -help</pre>

Mandatory unnamed args :
*string :: {Full Name (Dir+Pat)}
*INT :: {Size of Low Resolution Images}
*INT :: {Size of High Resolution Images}

Named args :
*[Name=ExpTxt] INT :: {Export files in text format (Def=false means binary)}
*[Name=ByP] INT :: {By process}
*[Name=PostFix] string :: {Add postfix in directory}
*[Name=NbMinPt] INT :: {Minimum number of points}
*[Name=DLR] INT :: {Do Low Resolution}
*[Name=Pat2] string :: {Second pattern}
*[Name=Detect] string
*[Name=Match] string
*[Name=NoMax] bool
*[Name=NoMin] bool
*[Name=NoUnknown] bool

====Example====
For example with the Buddha dataset, you can launch :
<pre>mm3d Tapioca MulScale "IMG_[0-9]{4}.tif" 300 -1</pre>
For example with the Cuxa dataset, you can launch :
<pre>mm3d Tapioca MulScale "Abbey-IMG_.*.jpg" 200 800</pre>

===Line===
It often occurs that the photos canvas has a linear structure, for example, when you acquire photos of a facade walking along the street. In this case, you know that the <math>Kth</math> image can only have tie points with images in the interval [K - δ, K + δ] giving this information to Tapioca can save a lot of time. The argument ''Number of adjacent images to look for'' sets δ. The ''Circ'' option is used if the acquisition is circular (the first and last image see each other). All the other arguments have the same meaning as in the ''All'' mode.

====Help====
You can access to the help by typing :
<pre>mm3d Tapioca Line -help</pre>

Mandatory unnamed args :
*string :: {Full Name (Dir+Pat)}
*INT :: {Image size}
*INT :: {Number of adjacent images to look for (&#948)}

Named args :
*[Name=ExpTxt] INT :: {Export files in text format (Def=false means binary)}
*[Name=Jump] vector<int> :: {Densification by jump }
*[Name=PostFix] string :: {Add postfix in directory}
*[Name=ByP] INT :: {By process}
*[Name=Circ] INT :: {In line mode if it's a loop (begin ~ end)}
*[Name=ForceAdSupResol] bool :: {to force computation even when Resol
*[Name=Detect] string
*[Name=Match] string
*[Name=NoMax] bool
*[Name=NoMin] bool
*[Name=NoUnknown] bool

====Example====
For example with the Ramses dataset, you can launch :
<pre> mm3d Tapioca Line "IMG.*CR2" 3 1000</pre>

===Graph===

====Help====
You can access to the help by typing : 
<pre>mm3d Tapioca Graph -help</pre>

Mandatory unnamed args :
*string :: {Full images' pattern (directory+pattern)}
*INT :: {Processing size of image (for the greater dimension)}

Named args :
*[Name=ByP] INT :: {By process}
*[Name=Detect] string :: {executable used to detect keypoints}
*[Name=MaxPoint] INT :: {number of points used per image to construct the graph (default 200)}
*[Name=MinScale] REAL :: {if specified, points with a lesser scale are ignored}
*[Name=MaxScale] REAL :: {if specified, points with a greater scale are ignored}
*[Name=NbRequired] INT :: {number of matches to create a connexion between two images (default 1)}
*[Name=Out] string :: {name of the produced XML file}
*[Name=PrintGraph] bool :: {print result graph in standard output}

===File===
A file specifying a set of images to be matched is needed here. Such a file can either be generated manually or be produced with [[OriConvert]] when the images come with GPS information, the images to be matched together being within a given distance threshold of each others.

====Help====
You can access to the help by typing : 
<pre>mm3d Tapioca File -help</pre>

Mandatory unnamed args :
*string :: {XML-File of pair}
*INT :: {Resolution}

Named args :
*[Name=ExpTxt] INT :: {Export files in text format (Def=false means binary)}
*[Name=PostFix] string :: {Add postfix in directory}
*[Name=ByP] INT :: {By process}
*[Name=Detect] string
*[Name=Match] string
*[Name=NoMax] bool
*[Name=NoMin] bool
*[Name=NoUnknown] bool

====Example====
In the tutorial [[GrandLeez]], we use the option File for [[Tapioca]].
The file FileImagesNeighbour.xml contain for each images, his differents neighboors. If you open the file, you can see :
<pre>
<Cple>R0040439.JPG R0040519.JPG</Cple>
<Cple>R0040439.JPG R0040514.JPG</Cple>
<Cple>R0040439.JPG R0040444.JPG</Cple>
<Cple>R0040439.JPG R0040517.JPG</Cple>
<Cple>R0040439.JPG R0040438.JPG</Cple>
<Cple>R0040439.JPG R0040440.JPG</Cple>
<Cple>R0040439.JPG R0040441.JPG</Cple>
<Cple>R0040439.JPG R0040516.JPG</Cple>
<Cple>R0040439.JPG R0040442.JPG</Cple>
<Cple>R0040439.JPG R0040515.JPG</Cple>
<Cple>R0040439.JPG R0040443.JPG</Cple>
</pre>
It means, image R0040439.JPG is connected with all the images detailed in <Cple> tag. So you can run the tie point generation with [[Tapioca]] using this file :
<pre>mm3d Tapioca File FileImagesNeighbour.xml -1</pre>

=What Tie Points is?=

==Tie points on low contrast Images==
The current implementation of SIFT++ used in MicMac is not fully invariant to scaling/translation in radiometry. This may be a problem in case of acquisitions having a good SNR but with low contrast in the scene; in this case, thanks to good SNR there is potential information to get tie points, but as this information is assimilated to noise, it cannnot be extracted. To overcome this problem, it is possible to require that MicMac computes some contrast enhancement on images before computing SIFT points.

Tapioca

2016-11-15T09:22:13Z

XavierR : /* Workflow */

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
Tapioca is a simple tool interface for computing tie points. I think Tapioca should be sufficient in 95% of cases. If it is not the case, you will have to refer to a more complex and powerful tool named [[Pastis]] which will be described later. In fact, Tapioca is only an interface to [[Pastis]].

===Syntax===
The global syntax for Tapioca is 
<pre>mm3d Tapioca UnNamedArgs NamedArgs</pre>

===Allowed commands===
*MulScale : Compute tie points for images in low resolution and then for high resolution.
*All : Compute tie points for all images in a given resolution.
*Line : Compute tie points for linear image canvas.
*File :
*Graph :

===Results===
Tapioca generate a directory named "Homol" ("Homol_SRes" for Tapioca MulScale) in your working directory which contain for each image of your canvas, a directory named "PastisImage_name". In this directory "Pastis" you will find a binary file (".dat") for each image linked with the first image by tie points. This binary files contains tie points. 
For example, in Gravillons dataset, all images are linked so this is the arborescence of the Gravillon Homol directory : 
[[Image:Tapioca_homol_arborescence.png|500px]]

===Workflow===
Tapioca, is generally the first command to launch in a MicMac process. 
[[Image:Picto-previous.png|20px]] Previous Command : ~ 
[[Image:Picto-next.png|20px]] Next Command : [[HomolFilterMasq]], [[Tapas]].

===Visualize tie points===
NB : This tool works only for Linux OS. 
If you want to visualize tie points matched by Tapioca, you can run the command [[SEL]]:
<pre>mm3d SEL image_1 image_2 KH=NB</pre>
[[Image:tapioca_exemple_sift.png|x200px]]

==Tie points computation mode==
===All===
Tie points are looked for in all possible pair of images at the reduced resolution chosen by the user in the ''Size of image'' option.

====Help====
You can access to the help by typing :
<pre>mm3d Tapioca All -help</pre>

Mandatory unnamed args :
*string :: {Full Name (Dir+Pat)}
*INT :: {Size of image, in pixels}

Named args :
*[Name=ExpTxt] INT :: {Export files in text format (Def=false means binary)}
*[Name=PostFix] string :: {Add postfix in directory}
*[Name=ByP] INT :: {By process}
*[Name=Pat2] string :: {Second pattern}
*[Name=Detect] string
*[Name=Match] string
*[Name=NoMax] bool
*[Name=NoMin] bool
*[Name=NoUnknown] bool

Using '''-1''' as Image's size is equivalent to use full resolution image. But it's recommended to use rather a resolution to a scaling between 0.3 and 0.5.

====Example====
For example with the Ramses dataset, you can launch : 
<pre>mm3d Tapioca All "IMG.*CR2" 1000</pre>

For example with the Zhenjue dataset, you can launch : 
<pre>mm3d Tapioca All ".*JPG" 1500</pre>

===MulScale===
The mode MulScale can save significant computation time on large sets of images. Even if it is not optimal for all canvas, it has the benefit of being general and usable with any data set. In this mode, a first computation of tie points is made for all the pairs of images at a low resolution (so it is quite fast), chosen by the user through the ''Size of Low Resolution Images'' option. Then the computation is done at the ''Size of High Resolution Images'' only for the pairs having, at low resolution, a number of tie points exceeding a given threshold (''NbMinPt'').

====Help====
You can access to the help by typing :
<pre>mm3d Tapioca MulScale -help</pre>

Mandatory unnamed args :
*string :: {Full Name (Dir+Pat)}
*INT :: {Size of Low Resolution Images}
*INT :: {Size of High Resolution Images}

Named args :
*[Name=ExpTxt] INT :: {Export files in text format (Def=false means binary)}
*[Name=ByP] INT :: {By process}
*[Name=PostFix] string :: {Add postfix in directory}
*[Name=NbMinPt] INT :: {Minimum number of points}
*[Name=DLR] INT :: {Do Low Resolution}
*[Name=Pat2] string :: {Second pattern}
*[Name=Detect] string
*[Name=Match] string
*[Name=NoMax] bool
*[Name=NoMin] bool
*[Name=NoUnknown] bool

====Example====
For example with the Buddha dataset, you can launch :
<pre>mm3d Tapioca MulScale "IMG_[0-9]{4}.tif" 300 -1</pre>
For example with the Cuxa dataset, you can launch :
<pre>mm3d Tapioca MulScale "Abbey-IMG_.*.jpg" 200 800</pre>

===Line===
It often occurs that the photos canvas has a linear structure, for example, when you acquire photos of a facade walking along the street. In this case, you know that the <math>Kth</math> image can only have tie points with images in the interval [K - δ, K + δ] giving this information to Tapioca can save a lot of time. The argument ''Number of adjacent images to look for'' sets δ. The ''Circ'' option is used if the acquisition is circular (the first and last image see each other). All the other arguments have the same meaning as in the ''All'' mode.

====Help====
You can access to the help by typing :
<pre>mm3d Tapioca Line -help</pre>

Mandatory unnamed args :
*string :: {Full Name (Dir+Pat)}
*INT :: {Image size}
*INT :: {Number of adjacent images to look for (&#948)}

Named args :
*[Name=ExpTxt] INT :: {Export files in text format (Def=false means binary)}
*[Name=Jump] vector<int> :: {Densification by jump }
*[Name=PostFix] string :: {Add postfix in directory}
*[Name=ByP] INT :: {By process}
*[Name=Circ] INT :: {In line mode if it's a loop (begin ~ end)}
*[Name=ForceAdSupResol] bool :: {to force computation even when Resol
*[Name=Detect] string
*[Name=Match] string
*[Name=NoMax] bool
*[Name=NoMin] bool
*[Name=NoUnknown] bool

====Example====
For example with the Ramses dataset, you can launch :
<pre> mm3d Tapioca Line "IMG.*CR2" 3 1000</pre>

===Graph===

====Help====
You can access to the help by typing : 
<pre>mm3d Tapioca Graph -help</pre>

Mandatory unnamed args :
*string :: {Full images' pattern (directory+pattern)}
*INT :: {Processing size of image (for the greater dimension)}

Named args :
*[Name=ByP] INT :: {By process}
*[Name=Detect] string :: {executable used to detect keypoints}
*[Name=MaxPoint] INT :: {number of points used per image to construct the graph (default 200)}
*[Name=MinScale] REAL :: {if specified, points with a lesser scale are ignored}
*[Name=MaxScale] REAL :: {if specified, points with a greater scale are ignored}
*[Name=NbRequired] INT :: {number of matches to create a connexion between two images (default 1)}
*[Name=Out] string :: {name of the produced XML file}
*[Name=PrintGraph] bool :: {print result graph in standard output}

===File===
A file specifying a set of images to be matched is needed here. Such a file can either be generated manually or be produced with [[OriConvert]] when the images come with GPS information, the images to be matched together being within a given distance threshold of each others.

====Help====
You can access to the help by typing : 
<pre>mm3d Tapioca File -help</pre>

Mandatory unnamed args :
*string :: {XML-File of pair}
*INT :: {Resolution}

Named args :
*[Name=ExpTxt] INT :: {Export files in text format (Def=false means binary)}
*[Name=PostFix] string :: {Add postfix in directory}
*[Name=ByP] INT :: {By process}
*[Name=Detect] string
*[Name=Match] string
*[Name=NoMax] bool
*[Name=NoMin] bool
*[Name=NoUnknown] bool

====Example====
In the tutorial [[GrandLeez]], we use the option File for [[Tapioca]].
The file FileImagesNeighbour.xml contain for each images, his differents neighboors. If you open the file, you can see :
<pre>
<Cple>R0040439.JPG R0040519.JPG</Cple>
<Cple>R0040439.JPG R0040514.JPG</Cple>
<Cple>R0040439.JPG R0040444.JPG</Cple>
<Cple>R0040439.JPG R0040517.JPG</Cple>
<Cple>R0040439.JPG R0040438.JPG</Cple>
<Cple>R0040439.JPG R0040440.JPG</Cple>
<Cple>R0040439.JPG R0040441.JPG</Cple>
<Cple>R0040439.JPG R0040516.JPG</Cple>
<Cple>R0040439.JPG R0040442.JPG</Cple>
<Cple>R0040439.JPG R0040515.JPG</Cple>
<Cple>R0040439.JPG R0040443.JPG</Cple>
</pre>
It means, image R0040439.JPG is connected with all the images detailed in <Cple> tag. So you can run the tie point generation with [[Tapioca]] using this file :
<pre>mm3d Tapioca File FileImagesNeighbour.xml -1</pre>

=What Tie Points is?=

==Tie points on low contrast Images==
The current implementation of SIFT++ used in MicMac is not fully invariant to scaling/translation in radiometry. This may be a problem in case of acquisitions having a good SNR but with low contrast in the scene; in this case, thanks to good SNR there is potential information to get tie points, but as this information is assimilated to noise, it cannnot be extracted. To overcome this problem, it is possible to require that MicMac computes some contrast enhancement on images before computing SIFT points.

Schnaps

2016-11-15T09:14:51Z

XavierR : Fix typo

Discussion:Tapioca

2016-11-14T14:21:41Z

XavierR :

To Do:

* Improve latest paragraph (rewrite it?)
* Explain SFS using (settings file or @sfs)
* Explain Tie points computation ismade in "black and white" mode [is it always true?]
* Note that there is no masking option in tapioca (as reported in http://forum-micmac.forumprod.com/using-mask-with-tapioca-t1302.html)

--[[Utilisateur:XavierR|XavierR]] ([[Discussion utilisateur:XavierR|discussion]]) 14 novembre 2016 à 15:21 (CET)

Discussion:Tapioca

2016-11-14T14:20:45Z

XavierR : To Do

To Do:

- Improve latest paragraph (rewrite it?)
- Explain SFS using (settings file or @sfs)
- Explain Tie points computation ismade in "black and white" mode [is it always true?]
- Note that there is no masking option in tapioca (as reported in http://forum-micmac.forumprod.com/using-mask-with-tapioca-t1302.html)

TestKey

2016-11-14T14:18:40Z

XavierR : Fix typo

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
TestKey is a basic tool for testing a regular expression for image pattern selection.

===Syntax===
The global syntax for TestKey is :
<pre>mm3d TestKey pattern</pre>

===Results===
TestKey print on the screen which images are included in the image pattern. If the pattern isn't correct, micmac print an error message, so you can easily check if your pattern is correct or not.
By default it is limited to 10 Name, the Nb optionale parameters can increase this default value.

===Workflow===
TestKey didn't take part of any workflow, it's just a tool to test an image pattern.

===Help===
You can access to the help by typing :
<pre>mm3d TestKey -help</pre>

Mandatory unnamed args :
*string :: {Full Directory (Dir+Pattern)}
Named args :
*[Name=Nb] INT :: {Nb Max printed (def=10)}

===Example===
In example, you can launch this command in the Zhenjue dataset :
<pre>mm3d TestKey "DSC_313[2-9].JPG"</pre>

Tapioca

2016-11-14T14:02:16Z

XavierR : Réorganisation

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
Tapioca is a simple tool interface for computing tie points. I think Tapioca should be sufficient in 95% of cases. If it is not the case, you will have to refer to a more complex and powerful tool named [[Pastis]] which will be described later. In fact, Tapioca is only an interface to [[Pastis]].

===Syntax===
The global syntax for Tapioca is 
<pre>mm3d Tapioca UnNamedArgs NamedArgs</pre>

===Allowed commands===
*MulScale : Compute tie points for images in low resolution and then for high resolution.
*All : Compute tie points for all images in a given resolution.
*Line : Compute tie points for linear image canvas.
*File :
*Graph :

===Results===
Tapioca generate a directory named "Homol" ("Homol_SRes" for Tapioca MulScale) in your working directory which contain for each image of your canvas, a directory named "PastisImage_name". In this directory "Pastis" you will find a binary file (".dat") for each image linked with the first image by tie points. This binary files contains tie points. 
For example, in Gravillons dataset, all images are linked so this is the arborescence of the Gravillon Homol directory : 
[[Image:Tapioca_homol_arborescence.png|500px]]

===Workflow===
Tapioca, is generally the first command to launch in a MicMac process. 
[[Image:Picto-previous.png|20px]] Previous Command : ~ 
[[Image:Picto-next.png|20px]] Next Command : [[Tapas]].

===Visualize tie points===
NB : This tool works only for Linux OS. 
If you want to visualize tie points matched by Tapioca, you can run the command [[SEL]]:
<pre>mm3d SEL image_1 image_2 KH=NB</pre>
[[Image:tapioca_exemple_sift.png|x200px]]

==Tie points computation mode==
===All===
Tie points are looked for in all possible pair of images at the reduced resolution chosen by the user in the ''Size of image'' option.

====Help====
You can access to the help by typing :
<pre>mm3d Tapioca All -help</pre>

Mandatory unnamed args :
*string :: {Full Name (Dir+Pat)}
*INT :: {Size of image, in pixels}

Named args :
*[Name=ExpTxt] INT :: {Export files in text format (Def=false means binary)}
*[Name=PostFix] string :: {Add postfix in directory}
*[Name=ByP] INT :: {By process}
*[Name=Pat2] string :: {Second pattern}
*[Name=Detect] string
*[Name=Match] string
*[Name=NoMax] bool
*[Name=NoMin] bool
*[Name=NoUnknown] bool

Using '''-1''' as Image's size is equivalent to use full resolution image. But it's recommended to use rather a resolution to a scaling between 0.3 and 0.5.

====Example====
For example with the Ramses dataset, you can launch : 
<pre>mm3d Tapioca All "IMG.*CR2" 1000</pre>

For example with the Zhenjue dataset, you can launch : 
<pre>mm3d Tapioca All ".*JPG" 1500</pre>

===MulScale===
The mode MulScale can save significant computation time on large sets of images. Even if it is not optimal for all canvas, it has the benefit of being general and usable with any data set. In this mode, a first computation of tie points is made for all the pairs of images at a low resolution (so it is quite fast), chosen by the user through the ''Size of Low Resolution Images'' option. Then the computation is done at the ''Size of High Resolution Images'' only for the pairs having, at low resolution, a number of tie points exceeding a given threshold (''NbMinPt'').

====Help====
You can access to the help by typing :
<pre>mm3d Tapioca MulScale -help</pre>

Mandatory unnamed args :
*string :: {Full Name (Dir+Pat)}
*INT :: {Size of Low Resolution Images}
*INT :: {Size of High Resolution Images}

Named args :
*[Name=ExpTxt] INT :: {Export files in text format (Def=false means binary)}
*[Name=ByP] INT :: {By process}
*[Name=PostFix] string :: {Add postfix in directory}
*[Name=NbMinPt] INT :: {Minimum number of points}
*[Name=DLR] INT :: {Do Low Resolution}
*[Name=Pat2] string :: {Second pattern}
*[Name=Detect] string
*[Name=Match] string
*[Name=NoMax] bool
*[Name=NoMin] bool
*[Name=NoUnknown] bool

====Example====
For example with the Buddha dataset, you can launch :
<pre>mm3d Tapioca MulScale "IMG_[0-9]{4}.tif" 300 -1</pre>
For example with the Cuxa dataset, you can launch :
<pre>mm3d Tapioca MulScale "Abbey-IMG_.*.jpg" 200 800</pre>

===Line===
It often occurs that the photos canvas has a linear structure, for example, when you acquire photos of a facade walking along the street. In this case, you know that the <math>Kth</math> image can only have tie points with images in the interval [K - δ, K + δ] giving this information to Tapioca can save a lot of time. The argument ''Number of adjacent images to look for'' sets δ. The ''Circ'' option is used if the acquisition is circular (the first and last image see each other). All the other arguments have the same meaning as in the ''All'' mode.

====Help====
You can access to the help by typing :
<pre>mm3d Tapioca Line -help</pre>

Mandatory unnamed args :
*string :: {Full Name (Dir+Pat)}
*INT :: {Image size}
*INT :: {Number of adjacent images to look for (&#948)}

Named args :
*[Name=ExpTxt] INT :: {Export files in text format (Def=false means binary)}
*[Name=Jump] vector<int> :: {Densification by jump }
*[Name=PostFix] string :: {Add postfix in directory}
*[Name=ByP] INT :: {By process}
*[Name=Circ] INT :: {In line mode if it's a loop (begin ~ end)}
*[Name=ForceAdSupResol] bool :: {to force computation even when Resol
*[Name=Detect] string
*[Name=Match] string
*[Name=NoMax] bool
*[Name=NoMin] bool
*[Name=NoUnknown] bool

====Example====
For example with the Ramses dataset, you can launch :
<pre> mm3d Tapioca Line "IMG.*CR2" 3 1000</pre>

===Graph===

====Help====
You can access to the help by typing : 
<pre>mm3d Tapioca Graph -help</pre>

Mandatory unnamed args :
*string :: {Full images' pattern (directory+pattern)}
*INT :: {Processing size of image (for the greater dimension)}

Named args :
*[Name=ByP] INT :: {By process}
*[Name=Detect] string :: {executable used to detect keypoints}
*[Name=MaxPoint] INT :: {number of points used per image to construct the graph (default 200)}
*[Name=MinScale] REAL :: {if specified, points with a lesser scale are ignored}
*[Name=MaxScale] REAL :: {if specified, points with a greater scale are ignored}
*[Name=NbRequired] INT :: {number of matches to create a connexion between two images (default 1)}
*[Name=Out] string :: {name of the produced XML file}
*[Name=PrintGraph] bool :: {print result graph in standard output}

===File===
A file specifying a set of images to be matched is needed here. Such a file can either be generated manually or be produced with [[OriConvert]] when the images come with GPS information, the images to be matched together being within a given distance threshold of each others.

====Help====
You can access to the help by typing : 
<pre>mm3d Tapioca File -help</pre>

Mandatory unnamed args :
*string :: {XML-File of pair}
*INT :: {Resolution}

Named args :
*[Name=ExpTxt] INT :: {Export files in text format (Def=false means binary)}
*[Name=PostFix] string :: {Add postfix in directory}
*[Name=ByP] INT :: {By process}
*[Name=Detect] string
*[Name=Match] string
*[Name=NoMax] bool
*[Name=NoMin] bool
*[Name=NoUnknown] bool

====Example====
In the tutorial [[GrandLeez]], we use the option File for [[Tapioca]].
The file FileImagesNeighbour.xml contain for each images, his differents neighboors. If you open the file, you can see :
<pre>
<Cple>R0040439.JPG R0040519.JPG</Cple>
<Cple>R0040439.JPG R0040514.JPG</Cple>
<Cple>R0040439.JPG R0040444.JPG</Cple>
<Cple>R0040439.JPG R0040517.JPG</Cple>
<Cple>R0040439.JPG R0040438.JPG</Cple>
<Cple>R0040439.JPG R0040440.JPG</Cple>
<Cple>R0040439.JPG R0040441.JPG</Cple>
<Cple>R0040439.JPG R0040516.JPG</Cple>
<Cple>R0040439.JPG R0040442.JPG</Cple>
<Cple>R0040439.JPG R0040515.JPG</Cple>
<Cple>R0040439.JPG R0040443.JPG</Cple>
</pre>
It means, image R0040439.JPG is connected with all the images detailed in <Cple> tag. So you can run the tie point generation with [[Tapioca]] using this file :
<pre>mm3d Tapioca File FileImagesNeighbour.xml -1</pre>

=What Tie Points is?=

==Tie points on low contrast Images==
The current implementation of SIFT++ used in MicMac is not fully invariant to scaling/translation in radiometry. This may be a problem in case of acquisitions having a good SNR but with low contrast in the scene; in this case, thanks to good SNR there is potential information to get tie points, but as this information is assimilated to noise, it cannnot be extracted. To overcome this problem, it is possible to require that MicMac computes some contrast enhancement on images before computing SIFT points.

MicMac tools

2016-11-10T09:22:19Z

XavierR : Ajout Schnaps et HomolFilterMask

== About all commands ==
All commands come with an inline Help that can be accessed by typing :

<pre>mm3d CommandName -help</pre>

Commands have Unnamed and Named arguments. The Unnamed are mandatory and must be given in order while the Named can be given in any order. For instance:

<pre>mm3d CommandName UnnamedValue1 UnnamedValue2 NamedArg1=NamedValue1 NamedArg2=NamedValue2</pre>

If you have a version of MicMac that include the QT tools (binaries from the [http://logiciels.ign.fr/?Telechargement,20 IGN download page] or self compiled with the QT option activated), each command come with a GUI containing the options to fill and a file selection tool when appropriate. These GUI can be called using the command with a ''v'' prefix:

<pre>mm3d vCommandName</pre>

== Commands ==
*[[AperiCloud]]
*[[Apero]]
*[[Bascule]]
*[[C3DC]]
*[[Campari]]
*[[CenterBascule]]
*[[CheckDependencies]],to do...
*[[ChgSysCo]],to do...
*[[GCPBascule]]
*[[GCPConvert]]
*[[GCPCtrl]],to do...
*[[GrShade]]
*[[HomolfilterMask]],to do...
*[[Malt]]
*[[Nuage2Ply]]
*[[NuageBascule]]
*[[OriConvert]]
*[[PIMs]],to improve...
*[[PIMs2MNT]]
*[[PIMs2Ply]]
*[[RepLocBascule]]
*[[SaisieAppuisInit]]
*[[SaisieAppuisInitQT]]
*[[SaisieAppuisPredic]]
*[[SaisieAppuisPredicQT]]
*[[SaisieBasc]]
*[[SaisieBascQT]]
*[[SaisieMasq]]
*[[SaisieMasqQT]]
*[[SBGlobBascule]]
*[[ScaleIm]]
*[[ScaleNuage]]
*[[Schnaps]], to improve
*[[SEL]]
*[[Tapas]]
*[[Tapioca]]
*[[Tarama]]
*[[Tawny]]
*[[Tequila]]
*[[TestKey]]
*[[TiPunch]]
*[[To8Bits]]
*[[CmpCalib]]

Schnaps

2016-11-10T09:20:04Z

XavierR : Création de page

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==

Schnaps is a global order-agnostic tie point reduction tool.

This command is used to clean and reduce tie points before any orientation, and without needing any order in the pictures. Its limitation is the user memory: it can't be used if computer RAM is lower than Homol directory size.

===Syntax===
The global syntax for Schnaps is :
<pre>mm3d Schnaps ImagePattern</pre>

===Workflow===
AperiCloud is a tool dedicated to tie point reduction. So you have to use it after tie points computation by Tapioca and before orientation computation by Tapas (or Martini). It could also be used after a first tiepoint reduction using mask(s) with HomolFilterMasq 
[[Image:Picto-previous.png|20px]] Previous Command : [[Tapioca]],[[HomolFilterMasq]] 
[[Image:Picto-next.png|20px]] Next Command : [[Tapas]],[[Martini]]. 


===Help===
You can access to the help by typing :
<pre>mm3d Schnaps -help</pre>

Mandatory unnamed args :
* string :: {Pattern of images}
Named args :
* [Name=HomolIn] string :: {Input Homol directory suffix (without "Homol")}
* [Name=NbWin] INT :: {Minimal homol points in each picture (default: 1000)}
* [Name=HomolOut] string :: {Output Homol directory suffix (default: _mini)}
* [Name=ExpTxt] bool :: {Ascii format for in and out, def=false}
* [Name=VeryStrict] bool :: {Be very strict with homols (remove any suspect),def=false}
* [Name=ShowStats] bool :: {Show Homol points stats before and after filtering, def=false}
* [Name=PoubelleName] string :: {Where to write suspicious pictures names, def="Schnaps_poubelle.txt"}
* [Name=minPercentCoverage] REAL :: {Minimum % of coverage to avoid adding to poubelle, def=30}

==Examples==

===Basic Example===
You can launch this command on most dataset with :
<pre>mm3d Schnaps «.*JPG »</pre>

By default Schnaps uses the \Homol" directory and creates a "\Homol_mini" directory for output, which will need to be specified in the following commands, generally with SH arguemnt. For example, with Tapas:
<pre>mm3d Tapas RadialExtended ".*JPG" SH=_mini</pre>

===After HomolFilterMasq===
Here, you have to specify the good homol directory. If you used default settings, it should be:
<pre>mm3d Schnaps ".*JPG" HomolIn=MasqFiltered</pre>

GCPConvert

2016-10-12T10:06:18Z

XavierR : Uncertainty in GCP file

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
The command GCPConvert is used to:
*transform a set of ground control points from most text format to MicMac’s Xml format.
*transform the ground control points into an euclidean coordinate system, suitable for MicMac.

===Allowed commands===
* AppEgels
* AppGeoCub
* AppInFile
* AppXML

===Syntax===
The global syntax for GCPConvert is :
<pre>mm3d GCPConvert FormatSpecification GCPFile NamedArgs</pre>

===Help===
You can access to the help by typing :
<pre>mm3d GCPConvert -help</pre>

Mandatory unnamed args :
*string :: {[[GCPConvert#Formatting_the_input_GCP_file|Format specification]]}
*string :: {GCP File}
Named args :
*[Name=Out] string :: {Xml Out File}
*[Name=ChSys] string :: {Change coordinate file}
*[Name=MulCo] REAL :: {Multiplier of result (for development and testing use)}
*[Name=MulInc] bool :: {Multiplier also incertitude ? (for development and testing use)}

===Example===
Launching this command,
<pre>mm3d GCPConvert AppInFile CP3D_Format.txt</pre>
You should get a file like this:
<pre><?xml version="1.0" ?>
<DicoAppuisFlottant>
<OneAppuisDAF>
<Pt>301.610 939.1341 144.75</Pt>
<NamePt>30</NamePt>
<Incertitude>1 1 1</Incertitude>
</OneAppuisDAF>
<OneAppuisDAF>
<Pt>301.412 937.530 144.787</Pt>
<NamePt>31</NamePt>
<Incertitude>1 1 1</Incertitude>
</OneAppuisDAF>
</DicoAppuisFlottant></pre>

===Uncertainty in output XML file===
As seen in previous example, the uncertainty of each ground control point is fixed by default at the value of one ground unit in each direction of the coordinate system:
<pre><Incertitude>1 1 1</Incertitude></pre>

In case of using the generated GCP file with Campari for bundle adjustment, you'll have to specify a factor which will be alter this uncertainty. So, if uncertainty is equal for each direction and each point, it's easier to specify it by this way.
In the following example, factor of '''0.002''' generates an uncertainty of '''2 mm''' in a metric coordinate system.
<pre>mm3d Campari ".*JPG" MEP_Basc2 MEP_Terrain GCP=[Targets.xml,0.002,Targets_Final-S2D.xml,0.5]</pre>

==Formatting the input GCP file ==
If you don't use an AppXML formatted file (in fact a MicMac's XML file), the input file has to be a '''space or tabulation separated values file''' (no comma or other symbols). You can use 'Egels' or 'GeoCub' format, or describe your file as explained below.

===AppGeoCub===
Text file is formatted as:
<pre>PointNumber X Y Z</pre>
Lines beginning with '%' are considered as comments.

===AppEgels===
Text file is formatted as:
<pre>PointNumber VariableNonImported X Y Z</pre>
Lines beginning with '#' are considered as comments.

This file format is used by some IGN/ENSG softwares developed by Yves Egels[http://yves.egels.free.fr/Soft/telecharger.html].

===AppInFile===
The first line describes name and position of the rows. It begins by '#F= ', where
*the first character '#' means that all line beginning by a # will be a comment;
*the two characters 'F=' mean that this is really a format specification;
'#F= ' followed by the format specification :
*'N' means the name of the point;
*'X', 'Y', 'Z' means the coordinates;
*'Ix', 'Iy', 'Iz' means the accuracy (not mandatory);
*S means a string which has not to be interpreted;
separated by spaces.

You can reorder this format as you want.

''Example 1:''
<pre>#F= N X Y Z Ix Iy Iz
157 233.28 144.03 103.05 0.00332 0.0034 0.0039
158 317.011 -0.00000 0.0000 0.0053 0.0060 0.0071</pre>
*N means the first string of each line is the name of the point;
*X, Y, Z means that this strings number 2, 3 and 4 are the coordinates;
*Ix, Iy, Iz means that this strings number 5, 6 and 7 are the accuracy;

''Example 2:''
<pre>#F= N S X Y Z
300 3 94.208685 658.506787 42.39556
301 3 95.323427 656.409116 43.502239
302 3 97.008135 654.424482 45.084237</pre>
*N means the first string of each line is the name of the point;
*S means the 2nd string has not to be interpreted;
*X, Y, Z means that this strings number 3, 4 and 5 are the coordinates.

==Known limitations==
===GCPConverts add many decimals to coordinates===
As reported [[http://forum-micmac.forumprod.com/gcpconvert-add-many-decimals-to-coordinates-t1267.html]], GCPConvert alters slightly values during the conversion, by adding non significant decimals.
So instead of taking back this file:
<pre><?xml version="1.0" ?>
<DicoAppuisFlottant>
<OneAppuisDAF>
<Pt>301.610 939.1341 144.75</Pt>
<NamePt>30</NamePt>
<Incertitude>1 1 1</Incertitude>
</OneAppuisDAF>
<OneAppuisDAF>
<Pt>301.412 937.530 144.787</Pt>
<NamePt>31</NamePt>
<Incertitude>1 1 1</Incertitude>
</OneAppuisDAF>
</DicoAppuisFlottant></pre>
You may rather obtain this one:
<pre><?xml version="1.0" ?>
<DicoAppuisFlottant>
<OneAppuisDAF>
<Pt>301.61000000000001 939.13400000000001 144.75</Pt>
<NamePt>30</NamePt>
<Incertitude>1 1 1</Incertitude>
</OneAppuisDAF>
<OneAppuisDAF>
<Pt>301.41199999999998 937.52999999999997 144.78700000000001</Pt>
<NamePt>31</NamePt>
<Incertitude>1 1 1</Incertitude>
</OneAppuisDAF>
</DicoAppuisFlottant></pre>

Campari

2016-10-10T13:58:08Z

XavierR :

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==

Campari is a tool for compensation of heterogeneous measures (tie points and ground control points).

===Syntax===
The global syntax for Campari is :

<pre>mm3d Campari FullDirectory InputOrientation OutputOrientation NamedArgs</pre>

===Help===
You can access to the help by typing :
<pre>mm3d Campari -help</pre>

Mandatory unnamed args :
* string :: {Full Directory (Dir+Pattern)}
* string :: {Input Orientation}
* string :: {Output Orientation}

Named args :
*[Name=GCP] vector :: {[GrMes.xml,GrUncertainty,ImMes.xml,ImUnc]}
*[Name=EmGPS] vector :: {Embedded GPS [Gps-Dir,GpsUnc, ?GpsAlti?], GpsAlti if != Plani}
*[Name=GpsLa] Pt3dr :: {Gps Lever Arm, in combination with EmGPS}
*[Name=SigmaTieP] REAL :: {Sigma use for TieP weighting (Def=1)}
*[Name=FactElimTieP] REAL :: {Fact elimination of tie point (prop to SigmaTieP, Def=5)}
*[Name=CPI1] bool :: {Calib Per Im, Firt time}
*[Name=CPI2] bool :: {Calib Per Im, After first time, reUsing Calib Per Im As input}
*[Name=FocFree] bool :: {Foc Free (Def=false)}
*[Name=PPFree] bool :: {Principal Point Free (Def=false)}
*[Name=AffineFree] bool :: {Affine Parameter (Def=false)}
*[Name=AllFree] bool :: {Affine Parameter (Def=false)}
*[Name=DetGCP] bool :: {Detail on GCP (Def=false)}
*[Name=Visc] REAL :: {Viscosity in Levenberg-Marquardt like resolution (Def=1.0)}
*[Name=ExpTxt] bool :: {Export in text format (Def=false)}
*[Name=ImMinMax] vector :: {Im max and min to avoid tricky pat}
*[Name=DegAdd] INT :: {When specified, degree of additional parameter}
*[Name=DegFree] INT :: {When specified degree of freedom of parameters generics}
*[Name=DRMax] INT :: {When specified degree of freedom of radial parameters}
*[Name=PoseFigee] bool :: {Does the external orientation of the cameras are frozen or free (Def=false, i.e. camera poses are free)}

By default, the bundle adjustment computed by Campari only affects camera orientation. Changing the value of '''FocFree''' and/or '''PPFree''' and/or '''AffineFree''', or '''AllFree''' to '''1''' permits to refine also camera calibration.

===Examples===
====Using GCP file====
For example, in the Mur Saint Martin dataset, you can launch :
<pre>mm3d Campari ".*JPG" MEP-Basc2 MEP-Terrain GCP=[MurSaintMartin.xml,0.02,MesureBasc.xml,0.5]</pre>

====With embedded GPS data, with refinement of camera calibration====
In the "Grand-Leez" dataset, adding GPS information in the bundle adjustment has a positive impact on the refinement of the camera orientation, in particular on the camera calibration.
<pre>Campari "R.*.JPG" BL72 BL72-Campari EmGPS=[GPS-BL72,2] FocFree=1 PPFree=1</pre>

Campari

2016-10-10T13:56:38Z

XavierR : Campari is able to refine camera calibration

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==

Campari is a tool for compensation of heterogeneous measures (tie points and ground control points).

===Syntax===
The global syntax for Campari is :

<pre>mm3d Campari FullDirectory InputOrientation OutputOrientation NamedArgs</pre>

===Help===
You can access to the help by typing :
<pre>mm3d Campari -help</pre>

Mandatory unnamed args :
* string :: {Full Directory (Dir+Pattern)}
* string :: {Input Orientation}
* string :: {Output Orientation}

Named args :
*[Name=GCP] vector :: {[GrMes.xml,GrUncertainty,ImMes.xml,ImUnc]}
*[Name=EmGPS] vector :: {Embedded GPS [Gps-Dir,GpsUnc, ?GpsAlti?], GpsAlti if != Plani}
*[Name=GpsLa] Pt3dr :: {Gps Lever Arm, in combination with EmGPS}
*[Name=SigmaTieP] REAL :: {Sigma use for TieP weighting (Def=1)}
*[Name=FactElimTieP] REAL :: {Fact elimination of tie point (prop to SigmaTieP, Def=5)}
*[Name=CPI1] bool :: {Calib Per Im, Firt time}
*[Name=CPI2] bool :: {Calib Per Im, After first time, reUsing Calib Per Im As input}
*[Name=FocFree] bool :: {Foc Free (Def=false)}
*[Name=PPFree] bool :: {Principal Point Free (Def=false)}
*[Name=AffineFree] bool :: {Affine Parameter (Def=false)}
*[Name=AllFree] bool :: {Affine Parameter (Def=false)}
*[Name=DetGCP] bool :: {Detail on GCP (Def=false)}
*[Name=Visc] REAL :: {Viscosity in Levenberg-Marquardt like resolution (Def=1.0)}
*[Name=ExpTxt] bool :: {Export in text format (Def=false)}
*[Name=ImMinMax] vector :: {Im max and min to avoid tricky pat}
*[Name=DegAdd] INT :: {When specified, degree of additional parameter}
*[Name=DegFree] INT :: {When specified degree of freedom of parameters generics}
*[Name=DRMax] INT :: {When specified degree of freedom of radial parameters}
*[Name=PoseFigee] bool :: {Does the external orientation of the cameras are frozen or free (Def=false, i.e. camera poses are free)}

By default, the bundle adjustment computed by Campari only affects camera orientation. Changing the value of '''FocFree''' and/or '''PPFree''' and/or '''AffineFree''', or '''AllFree''' to '''1''' permits to refine also camera calibration.

===Examples===
==Using GCP file==
For example, in the Mur Saint Martin dataset, you can launch :
<pre>mm3d Campari ".*JPG" MEP-Basc2 MEP-Terrain GCP=[MurSaintMartin.xml,0.02,MesureBasc.xml,0.5]</pre>

==With embedded GPS data, with refinement of camera calibration==
In the "Grand-Leez" dataset, adding GPS information in the bundle adjustment has a positive impact on the refinement of the camera orientation, in particular on the camera calibration.
<pre>Campari "R.*.JPG" BL72 BL72-Campari EmGPS=[GPS-BL72,2] FocFree=1 PPFree=1</pre>

AperiCloud

2016-10-10T13:15:56Z

XavierR :

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
AperiCloud is used for generating a visualization of and sparse 3D model and cameras position, computed by [[Tapas]] for example.

===Syntax===
The global syntax for AperiCloud is :
<pre>mm3d AperiCloud FullName Orientation NamedArgs</pre>

===Results===
AperiCloud, generate a sparse 3D cloud (".ply") with the position and orientation of each camera. If you don't use "Out" option, the file will be stored in your working directory at the name : AperiCloud-Ori_Name.ply. You can use MeshLab to visualize the file. 
[[Image:01_Gravillonn_AO.jpg|x200px]]
[[Image:Pierrerue2.png|x200px]]
[[Image:Exercice_Fontaine1.png|x200px]]

===Workflow===
AperiCloud is a tool dedicated to visualization of orientations. So you can use it every times you process a orientation. When you have processed the final orientation, you can define a 3D mask with the ".ply" file generated by AperiCloud (SaisieMasqQT). 
[[Image:Picto-previous.png|20px]] Previous Command : [[Tapas]],[[GCPBascule]],[[Campari]] 
[[Image:Picto-next.png|20px]] Next Command : [[SaisieMasqQT]]. 


===Help===
You can access to the help by typing :
<pre>mm3d AperiCLoud -help</pre>

Mandatory unnamed args :
*string :: {Full name (Dir+Pattern)}
*string :: {Orientation directory}
Named args :
*[Name=ExpTxt] INT :: {Point in txt format ? (Def=false)}
*[Name=Out] string :: {Result (Def=AperiCloud.ply)}
*[Name=Bin] INT :: {Ply in binary mode (Def=true)}
*[Name=RGB] INT :: {Use RGB image to texturate points (Def=true)}
*[Name=SeuilEc] REAL :: {Max residual (Def=10)}
*[Name=LimBsH] REAL :: {Limit ratio base to height (Def=1e-2)}
*[Name=WithPoints] bool :: {Do we add point cloud? (Def=true) }
*[Name=CalPerIm] bool :: {If a calibration per image was used (Def=false)}
*[Name=Focs] Pt2dr :: {Interval of Focal}
*[Name=WithCam] bool :: {With Camera (Def=true)}
*[Name=ColCadre] Pt3di :: {Col of camera rect Def= 255 0 0 (Red)}
*[Name=ColRay] Pt3di :: {Col of camera rect Def= 0 255 0 (Green)}
*[Name=SH] string :: {Set of Hom, Def="", give MasqFiltered for result of HomolFilterMasq}

===Example===

In example, you can launch this command in the Mur Saint Martin dataset :
<pre>mm3d AperiCloud «.*JPG » Out=MEP </pre>

PIMs2MNT

2016-09-23T11:46:02Z

XavierR : Fix and add

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
===Syntax===

The global syntax for PIMs2MNT is :
<pre>mm3d PIMs2MNT Type NamedArgs</pre>

===Help===
You can access to the help by typing :
<pre>mm3d PIMs2MNT -help</pre>

Mandatory unnamed args :
*string :: {Dir or PIM-Type (QuickMac ....)}
Named args :
*[Name=DS] REAL :: {Downscale, Def=1.0}
*[Name=Repere] string :: {Coordinate system (Euclid or Cyl)}
*[Name=Pat] string :: {Pattern, def = all existing clouds}
*[Name=DoMnt] bool :: { Compute DTM , def=true (use false to return only ortho)}
*[Name=DoOrtho] bool :: {Generate ortho photo, def=false}
*[Name=MasqImGlob] string :: {Global Masq for ortho: if used, give full name of masq (e.g. MasqGlob.tif) }
*[Name=Debug] bool :: {Debug !!!}
*[Name=UseTA] bool :: {Use TA as filter when exist (Def=false)}
*[Name=RI] REAL :: {Resol Im, def=1 }

===Example===
For example in the Cuxa Auto dataset, you can launch :
<pre>mm3d PIMs2Mnt BigMac DoMnt=1 DoOrtho=1</pre>