MicMac - Contributions de l’utilisateur [fr]

Install MicMac Ubuntu

2024-06-07T04:57:25Z

Harlock :

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 ==

The MicMac project is now hosted on the GitHub platform.

=== Install Git ===

<pre>sudo apt-get install git</pre>

=== Install other prerequisites ===
<pre> sudo apt-get install make imagemagick libimage-exiftool-perl exiv2 proj-bin qt5-default cmake build-essential</pre>

=== Download the source ===
Go to the installation directory, where you want to install MicMac.

For “optimisation” reasons, the project files were divided into three GitHub sub-projects:

* https://github.com/micmacIGN/micmac : contains the source code of MicMac

* https://github.com/micmacIGN/Documentation : contains the documentation/manuals

* https://github.com/micmacIGN/Papers : contains some publications and other reports concerning MicMac

To retrieve the source code to micmac folder:
<pre>
git clone https://github.com/micmacIGN/micmac.git micmac
</pre>

== Build from sources ==
===Automatically===
The script_jenkins.sh available in micmac repository (or here : [https://github.com/micmacIGN/micmac/blob/master/script_jenkins_unix.sh]) can be used for an automatic compilation from sources.

=== Manually ===

From the installation directory, move to the 'micmac' directory :
<pre>cd micmac/</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 -DWITH_QT5=1 -DWITH_CPP11=1 ..</pre>

<div class="toccolours mw-collapsible mw-collapsed" style="background-color: Lavender">
<h6 style="font-family: Helvetica:font-size: 40px">About option -DWITH_QT5=1</h6>
<div class="mw-collapsible-content">

Use this option if you want to use tools GUI such : SaisieAppuisInitQT, SaisieMasqQT etc... If not, simply use :
<pre>cmake ../</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.

</div>
</div>

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).

==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.<br>
Add the following lines at the bottom of the file :<br>
<code>export PATH=/''micmac_install_directory''/micmac/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.<br>

===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 :<br>
<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/micmac") and type:
<pre>
git pull
</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. If qt5-default is not available, try : <code>sudo apt install qtbase5-dev qtchooser qt5-qmake qtbase5-dev-tools</code>
*<code>No CMAKE_CXX_COMPILER could be found. </code> => install g++ (sudo apt-get install g++)
*<code>...Could not find a package configuration file provided by "Qt5OpenGL"...</code> => install libqt5opengl5-dev
[[Category:Installation]]

Malt

2022-07-23T06:59:16Z

Harlock : Add error messages

[[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> <br>

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>

==Error messages==
* outside reading file in RLE mode : occurs in rare cases where mask image size doesn't match image size.

Tapioca

2021-12-13T03:22:51Z

Harlock : Correction commande mm3d SEL

[[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 <br>
<pre>mm3d Tapioca UnNamedArgs NamedArgs</pre>

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

===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 "Pastis<i>Image_name</i>". 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.<br>
For example, in Gravillons dataset, all images are linked so this is the arborescence of the Gravillon Homol directory :<br>
[[Image:Tapioca_homol_arborescence.png|500px]]

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

===Visualize tie points===
NB : This tool works only for Linux OS.<br>
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 : <br>
<pre>mm3d Tapioca All "IMG.*CR2" 1000</pre>

For example with the Zhenjue dataset, you can launch : <br>
<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" 1000 3</pre>

===Graph===

====Help====
You can access to the help by typing :<br>
<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 :<br>
<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 <i>FileImagesNeighbour.xml</i> 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 <i>R0040439.JPG</i> 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.

Tapas

2021-12-03T04:38:28Z

Harlock : Added "very singular matrix in Gausj" error message.

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
Tapas is a tool offering most of the posssibilities of [[Apero]] for computing purely relative orientations

===Syntax===
The global syntax for Tapas is
<pre>mm3d Tapas ModeCalib NamedArgs</pre>

=== Allowed commands ===
This allowed commands, correspond to the distorsion model you want to use :
*<b>RadialBasic</b> : for Classic Lens
*<b>RadialStd</b> : for Classic Lens
*<b>RadialExtended</b> : Classic Lens with extra distorsion parameters.
*<b>FraserBasic</b>
*<b>Fraser</b>
*<b>FishEyeEqui</b> : for FishEye Lens
*<b>FE_EquiSolBasic</b>
* FishEyeBasic
* FishEyeStereo
*<b>Four</b>
*<b>AddFour</b>
*<b>AddPolyDeg</b>
* Ebner
* Brown
* AutoCal
* Figee
* HemiEqui

==== Description ====

{| class="wikitable"
|+ Description of the basic distortion models easily accessible in MicMac
!scope=col|Command
!scope=col|PPA/PPS
!scope=col|Polynomial correction
!scope=col|Decentric/Affine correction
!scope=col|Number of parameters to estimate
|-
| <center><code>RadialBasic</code></center> || <center>Equals</center> || <center>r³, r⁵, r⁷</center> || <center>No</center> || <center>5</center>
|-
| <center><code>RadialStd</code></center> || <center>Different</center> || <center>r³, r⁵, r⁷</center> || <center>No</center> || <center>8</center>
|-
| <center><code>RadialExtended</code></center> || <center>Different</center> || <center>r³, r⁵, r⁷, r⁹, r¹¹</center> || <center>No</center> || <center>10</center>
|-
| <center><code>FraserBasic</code></center> || <center>Equals</center> || <center>r³, r⁵, r⁷</center> || <center>Yes</center> || <center>10</center>
|-
| <center><code>Fraser</code></center> || <center>Different</center> || <center>r³, r⁵, r⁷</center> || <center>Yes</center> || <center>12</center>
|}
Source : https://www.int-arch-photogramm-remote-sens-spatial-inf-sci.net/XL-3-W3/327/2015/isprsarchives-XL-3-W3-327-2015.pdf

===Results===
Tapas produce a directory named "Ori-Out_name" which contain :
*Camera calibration file : AutoCal[...].xml with camera parameters : focal length, PPP, distorsion parameters.
<pre>
<?xml version="1.0" ?>
<ExportAPERO>
<CalibrationInternConique>
<KnownConv>eConvApero_DistM2C</KnownConv>
<PP>3036.5765679584747 1998.71167135734891</PP> %Position of PPS in image
<F>4037.08453810194351</F> %Focal length
<SzIm>6000 4000</SzIm> %Image size
<CalibDistortion>
<ModRad> %Coefficient of distorsion
<CDist>3052.42394103968081 2001.86999748472294</CDist>
<CoeffDist>-4.50469053927919027e-09</CoeffDist>
<CoeffDist>3.40541430467215144e-16</CoeffDist>
<CoeffDist>6.26870361086794563e-25</CoeffDist>
<CoeffDistInv>4.51807038353698039e-09</CoeffDistInv>
<CoeffDistInv>-2.83621415930942252e-16</CoeffDistInv>
<CoeffDistInv>-1.28602811626265918e-23</CoeffDistInv>
<CoeffDistInv>5.99729269914569738e-31</CoeffDistInv>
</ModRad>
</CalibDistortion>
</CalibrationInternConique>
</ExportAPERO>
</pre>
*Orientation file for each picture : Orientation-image_name.xml with :camera orientation (3D similarity), tie points used for orientation etc...
<pre>
<?xml version="1.0" ?>
<ExportAPERO>
<OrientationConique>
<OrIntImaM2C>
<I00>0 0</I00>
<V10>1 0</V10>
<V01>0 1</V01>
</OrIntImaM2C>
<TypeProj>eProjStenope</TypeProj>
<ZoneUtileInPixel>true</ZoneUtileInPixel>
<FileInterne>Ori-Arbitrary/AutoCal_Foc-16000_Cam-ILCE6000.xml</FileInterne> %Camera model
<RelativeNameFI>true</RelativeNameFI>
<Externe>
<AltiSol>-8.50917595677101524</AltiSol>
<Profondeur>9.9233022137615734</Profondeur>
<Time>-1.00000000000000002e+30</Time>
<KnownConv>eConvApero_DistM2C</KnownConv>
<Centre>0.33581992261091842 -26.3001714173638206 0.000147586637632812767</Centre> %Position of the PPS in arbitrary system
<IncCentre>1 1 1</IncCentre>
<ParamRotation>
<CodageMatr> %Boresight matrix (arbitrary system)
<L1>-0.981263794354502505 -0.155204851492389134 0.11416137684098876</L1>
<L2>-0.192442661386862057 0.818245676864819083 -0.541700871672157969</L2>
<L3>-0.00933744972389951265 -0.553520971929031491 -0.832782892275888531</L3>
</CodageMatr>
</ParamRotation>
</Externe>
...
</pre>
When you use Tapas, a important part of informations are displaying directly in the terminal window, like image resiual or number of tie points used per images. Don't forget to look at this residuals when you use Tapas, for a good orientation you can decrease under 0.5px. All this informations are stocked in a file named "Residual.xml"

===Workflow===
Tapas process internal and relative orientation, you it's placed just after Tapas. The way to visualize relative orientation is to use AperiCloud.<br>
[[Image:Picto-previous.png|20px]] Previous Command : [[Tapioca]]<br>
[[Image:Picto-next.png|20px]] Next Command : [[AperiCloud]].

==RadialBasic==
a subset of previous model: radial distortion with limited degrees of freedom ; adapted when there is a risk of divergence of RadialExtended; in this model there are 5 degrees of freedom : 1 for focal length , 2 for principal point and distortion center 3 , 2 for coefficients of radial distortion (r3 and r5 ).

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

Mandatory unnamed args :
*string :: {Calibration model}
*string :: {Full Directory (Dir+Pattern)}

Named args :
*[Name=ExpTxt] INT :: {Export in text format (Def=false)}
*[Name=Out] string :: {Directory of Output Orientation}
*[Name=InCal] string :: {Directory of Input Internal Orientation (Calibration)}
*[Name=InOri] string :: {Directory of Input External Orientation}
*[Name=DoC] INT :: {Do Compensation}
*[Name=ForCalib] INT :: {Is for calibration (Change def value of LMV and prop diag)?}
*[Name=Focs] Pt2dr :: {Keep images with focal length inside range [A,B] (A,B in mm) (Def=keep all)}
*[Name=VitesseInit] INT
*[Name=PPRel] Pt2dr :: {Principal point shift}''</span style>
*[Name=Decentre] INT :: {Principal point is shifted (Def=false)}''</span style>
*[Name=PropDiag] REAL :: {Hemi-spherik fisheye diameter to diagonal ratio}''</span style>
*[Name=SauvAutom] string :: {Save intermediary results to, Set NONE if dont want any}''</span style>
*[Name=ImInit] string :: {Force first image}''</span style>
*[Name=MOI] bool :: {MOI}''</span style>

==RadialExtended==
A model with radial distortion.

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

Mandatory unnamed args :
*string :: {Calibration model}
*string :: {Full Directory (Dir+Pattern)}

Named args :
*[Name=ExpTxt] INT :: {Export in text format (Def=false)}
*[Name=Out] string :: {Directory of Output Orientation} ''</span style>
*[Name=InCal] string :: {Directory of Input Internal Orientation (Calibration)}
*[Name=InOri] string :: {Directory of Input External Orientation}
*[Name=DoC] INT :: {Do Compensation}
*[Name=ForCalib] INT :: {Is for calibration (Change def value of LMV and prop diag)?}
*[Name=Focs] Pt2dr :: {Keep images with focal length inside range [A,B] (A,B in mm) (Def=keep all)}
*[Name=VitesseInit] INT
*[Name=PPRel] Pt2dr :: {Principal point shift}
*[Name=Decentre] INT :: {Principal point is shifted (Def=false)}
*[Name=PropDiag] REAL :: {Hemi-spherik fisheye diameter to diagonal ratio}
*[Name=SauvAutom] string :: {Save intermediary results to, Set NONE if dont want any}
*[Name=ImInit] string :: {Force first image}
*[Name=MOI] bool :: {MOI}
*[Name=DBF] INT :: {Debug (internal use : DebugPbCondFaisceau=true)
*[Name=Debug] bool :: {Partial file for debug}
*[Name=DegRadMax] INT :: {Max degree of radial, default model dependent}
*[Name=DegGen] INT :: {Max degree of general polynome, default model dependent (generally 0 or 1)}
*[Name=LibAff] bool :: {Free affine parameter, Def=true}
*[Name=LibDec] bool :: {Free decentric parameter, Def=true}
*[Name=LibPP] bool :: {Free principal point, Def=true}
*[Name=LibCP] bool :: {Free distorsion center, Def=true}
*[Name=LibFoc] bool :: {Free focal, Def=true}
*[Name=RapTxt] string :: {RapTxt}
*[Name=LinkPPaPPs] REAL :: {Link PPa and PPs (double)}
*[Name=FrozenPoses] string :: {List of frozen poses (pattern)}
*[Name=SH] string :: {Set of Hom, Def="", give MasqFiltered for result of HomolFilterMasq}
*[Name=RefineAll] bool :: {More refinement at all step, safer and more accurate, but slower, def=true}

===Example===
For example with the Mur Saint Martin dataset, you can launch :
<pre>Tapas RadialExtended "IMGP41((6[7-9])|([7-8][0-9])).JPG"</pre>

==Fraser==
a radial model, with decentric and affine parameters there are 12 degrees of freedom: 1 for focal length , 2 for principal point, 2 for distortion center , 3 for coefficients of radial distorsion (r3 , r5 r7 ), 2 for decentric parameters, 2 for affine parameters; the optional parameters LibAff and LibDec (def value true) can be set to false if decentric of affine parameters must stay frozen.

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

Mandatory unnamed args :
*{Calibration model}
*string :: {Full Directory (Dir+Pattern)}

Named args :
*[Name=ExpTxt] INT :: {Export in text format (Def=false)}
*[Name=Out] string :: {Directory of Output Orientation}
*[Name=InCal] string :: {Directory of Input Internal Orientation (Calibration)}
*[Name=InOri] string :: {Directory of Input External Orientation}
*[Name=DoC] INT :: {Do Compensation}
*[Name=ForCalib] INT :: {Is for calibration (Change def value of LMV and prop diag)?}
*[Name=Focs] Pt2dr :: {Keep images with focal length inside range [A,B] (A,B in mm) (Def=keep all)}
*[Name=VitesseInit] INT
*[Name=PPRel] Pt2dr :: {Principal point shift}
*[Name=Decentre] INT :: {Principal point is shifted (Def=false)}
*[Name=PropDiag] REAL :: {Hemi-spherik fisheye diameter to diagonal ratio}
*[Name=SauvAutom] string :: {Save intermediary results to, Set NONE if dont want any}
*[Name=ImInit] string :: {Force first image}
*[Name=MOI] bool :: {MOI}
*[Name=DBF] INT :: {Debug (internal use : DebugPbCondFaisceau=true) }
*[Name=Debug] bool :: {Partial file for debug}
*[Name=DegRadMax] INT :: {Max degree of radial, default model dependent}
*[Name=DegGen] INT :: {Max degree of general polynome, default model dependent (generally 0 or 1)}
*[Name=LibAff] bool :: {Free affine parameter, Def=true}
*[Name=LibDec] bool :: {Free decentric parameter, Def=true}
*[Name=LibPP] bool :: {Free principal point, Def=true}
*[Name=LibCP] bool :: {Free distorsion center, Def=true}
*[Name=LibFoc] bool :: {Free focal, Def=true}
*[Name=RapTxt] string :: {RapTxt}
*[Name=LinkPPaPPs] REAL :: {Link PPa and PPs (double)}
*[Name=FrozenPoses] string :: {List of frozen poses (pattern)}
*[Name=SH] string :: {Set of Hom, Def="", give MasqFiltered for result of HomolFilterMasq}
*[Name=RefineAll] bool :: {More refinement at all step, safer and more accurate, but slower, def=true}
*[Name=ImMinMax] vector :: {Image min and max (may avoid tricky pattern ...)}
*[Name=EcMax] REAL :: {Final threshold for residual, def = 5.0 }

==FraserBasic==
same as previous with for principal point and distortion center constrained to have the same value (so 10 degree of freedom)

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

Mandatory unnamed args :
*string :: {Calibration model}
*string :: {Full Directory (Dir+Pattern)}

Named args :
*[Name=ExpTxt] INT :: {Export in text format (Def=false)}
*[Name=Out] string :: {Directory of Output Orientation}
*[Name=InCal] string :: {Directory of Input Internal Orientation (Calibration)}
*[Name=InOri] string :: {Directory of Input External Orientation}
*[Name=DoC] INT :: {Do Compensation}
*[Name=ForCalib] INT :: {Is for calibration (Change def value of LMV and prop diag)?}
*[Name=Focs] Pt2dr :: {Keep images with focal length inside range [A,B] (A,B in mm) (Def=keep all)}
*[Name=VitesseInit] INT
*[Name=PPRel] Pt2dr :: {Principal point shift}
*[Name=Decentre] INT :: {Principal point is shifted (Def=false)}
*[Name=PropDiag] REAL :: {Hemi-spherik fisheye diameter to diagonal ratio}
*[Name=SauvAutom] string :: {Save intermediary results to, Set NONE if dont want any}
*[Name=ImInit] string :: {Force first image}
*[Name=MOI] bool :: {MOI}
*[Name=DBF] INT :: {Debug (internal use : DebugPbCondFaisceau=true) }
*[Name=Debug] bool :: {Partial file for debug}
*[Name=DegRadMax] INT :: {Max degree of radial, default model dependent}
*[Name=DegGen] INT :: {Max degree of general polynome, default model dependent (generally 0 or 1)}
*[Name=LibAff] bool :: {Free affine parameter, Def=true}
*[Name=LibDec] bool :: {Free decentric parameter, Def=true}
*[Name=LibPP] bool :: {Free principal point, Def=true}
*[Name=LibCP] bool :: {Free distorsion center, Def=true}
*[Name=LibFoc] bool :: {Free focal, Def=true}
*[Name=RapTxt] string :: {RapTxt}
*[Name=LinkPPaPPs] REAL :: {Link PPa and PPs (double)}
*[Name=FrozenPoses] string :: {List of frozen poses (pattern)}
*[Name=SH] string :: {Set of Hom, Def="", give MasqFiltered for result of HomolFilterMasq}
*[Name=RefineAll] bool :: {More refinement at all step, safer and more accurate, but slower, def=true}
*[Name=ImMinMax] vector :: {Image min and max (may avoid tricky pattern ...)}
*[Name=EcMax] REAL :: {Final threshold for residual, def = 5.0 }

==FishEyeEqui==
a model adapted for diagonal fisheyes equilinear ( with atan physicall model com- pleted with polynomial parameters there are 14 degrees of freedom: 1 for focal length , 2 for principal point, 2 for distorsion center , 5 for coefficients of radial distortion (r3 , r5 r7 ), 2 for decentric parameters, 2 for affine parameters; by default the ray defining the useful mask is 95% of the diagonal.

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

Mandatory unnamed args :
*string :: {Calibration model}
*string :: {Full Directory (Dir+Pattern)}

Named args :
*[Name=ExpTxt] INT :: {Export in text format (Def=false)}
*[Name=Out] string :: {Directory of Output Orientation}
*[Name=InCal] string :: {Directory of Input Internal Orientation (Calibration)}
*[Name=InOri] string :: {Directory of Input External Orientation}
*[Name=DoC] INT :: {Do Compensation}
*[Name=ForCalib] INT :: {Is for calibration (Change def value of LMV and prop diag)?}
*[Name=Focs] Pt2dr :: {Keep images with focal length inside range [A,B] (A,B in mm) (Def=keep all)}
*[Name=VitesseInit] INT
*[Name=PPRel] Pt2dr :: {Principal point shift}
*[Name=Decentre] INT :: {Principal point is shifted (Def=false)}
*[Name=PropDiag] REAL :: {Hemi-spherik fisheye diameter to diagonal ratio}
*[Name=SauvAutom] string :: {Save intermediary results to, Set NONE if dont want any}
*[Name=ImInit] string :: {Force first image}
*[Name=MOI] bool :: {MOI}
*[Name=DBF] INT :: {Debug (internal use : DebugPbCondFaisceau=true) }
*[Name=Debug] bool :: {Partial file for debug}
*[Name=DegRadMax] INT :: {Max degree of radial, default model dependent}
*[Name=DegGen] INT :: {Max degree of general polynome, default model dependent (generally 0 or 1)}
*[Name=LibAff] bool :: {Free affine parameter, Def=true}
*[Name=LibDec] bool :: {Free decentric parameter, Def=true}
*[Name=LibPP] bool :: {Free principal point, Def=true}
*[Name=LibCP] bool :: {Free distorsion center, Def=true}
*[Name=LibFoc] bool :: {Free focal, Def=true}
*[Name=RapTxt] string :: {RapTxt}
*[Name=LinkPPaPPs] REAL :: {Link PPa and PPs (double)}
*[Name=FrozenPoses] string :: {List of frozen poses (pattern)}
*[Name=SH] string :: {Set of Hom, Def="", give MasqFiltered for result of HomolFilterMasq}
*[Name=RefineAll] bool :: {More refinement at all step, safer and more accurate, but slower, def=true}
*[Name=ImMinMax] vector :: {Image min and max (may avoid tricky pattern ...)}
*[Name=EcMax] REAL :: {Final threshold for residual, def = 5.0 }

==HemiEqui==
same model as previous, but by default the ray defining the useful mask s 52% of the diagonal; adapted to hemispheric equilinear fisheye.

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

Mandatory unnamed args :
*string :: {Calibration model}
*string :: {Full Directory (Dir+Pattern)}

Named args :
*[Name=ExpTxt] INT :: {Export in text format (Def=false)}
*[Name=Out] string :: {Directory of Output Orientation}
*[Name=InCal] string :: {Directory of Input Internal Orientation (Calibration)}
*[Name=InOri] string :: {Directory of Input External Orientation}
*[Name=DoC] INT :: {Do Compensation}
*[Name=ForCalib] INT :: {Is for calibration (Change def value of LMV and prop diag)?}
*[Name=Focs] Pt2dr :: {Keep images with focal length inside range [A,B] (A,B in mm) (Def=keep all)}
*[Name=VitesseInit] INT
*[Name=PPRel] Pt2dr :: {Principal point shift}
*[Name=Decentre] INT :: {Principal point is shifted (Def=false)}
*[Name=PropDiag] REAL :: {Hemi-spherik fisheye diameter to diagonal ratio}
*[Name=SauvAutom] string :: {Save intermediary results to, Set NONE if dont want any}
*[Name=ImInit] string :: {Force first image}
*[Name=MOI] bool :: {MOI}
*[Name=DBF] INT :: {Debug (internal use : DebugPbCondFaisceau=true) }
*[Name=Debug] bool :: {Partial file for debug}
*[Name=DegRadMax] INT :: {Max degree of radial, default model dependent}
*[Name=DegGen] INT :: {Max degree of general polynome, default model dependent (generally 0 or 1)}
*[Name=LibAff] bool :: {Free affine parameter, Def=true}
*[Name=LibDec] bool :: {Free decentric parameter, Def=true}
*[Name=LibPP] bool :: {Free principal point, Def=true}
*[Name=LibCP] bool :: {Free distorsion center, Def=true}
*[Name=LibFoc] bool :: {Free focal, Def=true}
*[Name=RapTxt] string :: {RapTxt}
*[Name=LinkPPaPPs] REAL :: {Link PPa and PPs (double)}
*[Name=FrozenPoses] string :: {List of frozen poses (pattern)}
*[Name=SH] string :: {Set of Hom, Def="", give MasqFiltered for result of HomolFilterMasq}
*[Name=RefineAll] bool :: {More refinement at all step, safer and more accurate, but slower, def=true}
*[Name=ImMinMax] vector :: {Image min and max (may avoid tricky

== Error messages ==
* Pt Out Cam in ElCamera::F2toPtDirRayonL3 : occurs when an image in a sequence have been rotated before processing (happens sometime when dealing with old aerial scans)
* very singular matrix in Gausj : choose a distortion model with a lower number of parameters to estimate.

Tapas

2021-12-03T03:57:17Z

Harlock : Add error messages list

TestLib

2021-11-02T07:33:29Z

Harlock : Ajout de la commande SeamlineFeathering

== SeamlineFeathering ==

./mm3d TestLib SeamlineFeathering -help

Mandatory unnamed args :
* string :: {ortho pattern}
Named args :
* [Name=Out] string :: {Name of resulting map}
* [Name=Dist] INT :: {Distance for seamline feathering blending, in chamfer 32 distance : 0-244, default 50. Processing time increases considerably with large values}
* [Name=Lambda] REAL :: {lambda value for gaussian distance weighting, def 0.4.}
* [Name=Label] string :: {label/index map (tif) previously computed by Tawny. If not provided, generate a new label map based on incidence value}
* [Name=ComputeRE] bool :: {Compute Radiometric Equalization models with TestLib EROS. def false}
* [Name=ApplyRE] bool :: {Apply Radiometric Equalization? require to dertermine models of radiometric equalization beforehand (mm3d TestLib EROS or ComputeRE==1). def false}
* [Name=FileRE] string :: {Name of xml file with models of Radiometric Equalization, def 'RadiomEgalModels.xml'. }
* [Name=SzBox] Pt2di :: {Size [pix] of mosaic tile for multiprocess computation, def=[10000,10000].}
* [Name=SzTile] Pt2di :: {Size [pix] of mosaic tile for writing result, def=[25000,25000].}
* [Name=Buffer] INT :: {Buffer [pix] to apply for each tile in order to avoid edge effect, def=300.}
* [Name=Debug] bool :: {Write intermediate results for debug purpose.}
* [Name=TmpDir] string :: {Directory for intermediate results generated in debug mode.}

Discussion:Tapioca

2020-02-17T05:13:57Z

Harlock : Tapioca Line arguments' order

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)

== image size ==

Image size for mandatory Arg #2 is the image width, as specified in DocMicMac. I think it might be good to be more specific than just size. Thanks

== Tapioca Line ==
In description the arguments should be put this way :

<pre>Tapioca Line name size number</pre>

But in the example, size and number was inverted :

<pre> mm3d Tapioca Line "IMG.*CR2" 3 1000</pre>

I have changed this, but if anybody could check I am correct.

Tapioca

2020-02-17T05:07:52Z

Harlock : Correction of Tapioca Line example : the arguments' order has been inverted.

[[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 <br>
<pre>mm3d Tapioca UnNamedArgs NamedArgs</pre>

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

===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 "Pastis<i>Image_name</i>". 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.<br>
For example, in Gravillons dataset, all images are linked so this is the arborescence of the Gravillon Homol directory :<br>
[[Image:Tapioca_homol_arborescence.png|500px]]

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

===Visualize tie points===
NB : This tool works only for Linux OS.<br>
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 : <br>
<pre>mm3d Tapioca All "IMG.*CR2" 1000</pre>

For example with the Zhenjue dataset, you can launch : <br>
<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" 1000 3</pre>

===Graph===

====Help====
You can access to the help by typing :<br>
<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 :<br>
<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 <i>FileImagesNeighbour.xml</i> 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 <i>R0040439.JPG</i> 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.

SaisieMasqQT

2019-09-22T11:11:48Z

Harlock : Mask definition

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

SaisieMasqQT is the same tool as [[SaisieMasq]], available on all platforms (Linux, Windows, MacOS). SaisieMasqQT can be run several ways. You can run command mm3d SaisieMasqQT and drag-and-drop files in the application window, or open files from File menu, or you can run command mm3d SaisieMasqQT + arguments mm3d SaisieMasqQT -l to load last edited file. A visual interface for argument edition is also available with command: <pre>mm3d vSaisieMasqQT </pre>

SaisieMasqQT has the same arguments as [[SaisieMasq]]. Some light differences with [[SaisieMasq]] processing workflow should be noticed: you need to draw a polygon first, and then apply an action (add to mask, remove from mask, etc.). You can get a complete list of possibles actions typing F1.

"Mask" defines the area to be treated, which appears green in the view window (counterintuitively, the area outside the mask is the one actually hidden for treatment).

[[Image:SaisieMasqQT_Fontaine.png|thumb|180px|The green area ("mask") is here used for correlation]]

Main actions are :
* F2: display image in full screen
* Wheel roll: zoom
* Wheel click: move image
* Shift+wheel click: zoom fast
* Left click: add a point to polygon
* Right click: close polygon
* Space: Add to mask
* Suppr: Remove from mask
* Right click (close to a point): delete point
* Echap: delete polygon
* Shift + click & drag: insert point
* Ctrl+S: save mask image and Xml file
* Ctrl+Q: quit

Some parameters can be edited in the Settings menu: image gamma, application language, display settings, etc. These parameters are stored, and are used at next application launch, so set them once to fit your own purpose. As SaisieMasqQT can edit both images and 3d point clouds, application has different behavior, depending on which data you deal with. As a result, Settings menu, and help window dialog (F1), will change depending on the loaded data. Be careful about this!

Some special features have been added to SaisieMasqQT, which may differ from original SaisieMasq :
* modify current selection, with Shift+Click to insert a point, or Click+drag to move a point
* modify previous actions, with menu Windows/Show polygons list
* measure image distances, with Rule tool

To modify previous actions, you can undo/redo last actions with Ctrl+Z/Shift+Ctrl+Z, and you can edit list of previous actions, with menu Windows/Show polygons list: click on the actions in the list in the right window, then edit polygon (by adding or moving points), or double-click on the action name (column Mode) to change action. Apply changes clicking Return, or go in the Menu Mask edition and select Confirm changes.

Note: if you want to change application language, go in the Settings menu, apply changes and restart
application.

===Syntax===
SaisieMasqQT can be run several ways. You can run command mm3d SaisieMasqQT and drag-and-drop files in the application window, or open files from File menu, or you can run command :

<pre>mm3d SaisieMasqQT + arguments</pre>

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

SaisieMasqQT [filename] [option=]

*[filename] string : open file (image or ply or camera xml)

Options

*[Name=SzW] Pt2di : set window size (default=[900,700])
*[Name=Post] string : change postfix output file (default=_Masq)
*[Name=Name] string : set output filename (default=input+_Masq)
*[Name=Gama] REAL : apply gamma to image
*[Name=Attr] string : string to add to postfix

NB:
SaisieMasqQT can be run without any argument
Visual interface for argument edition available with command: <pre>mm3d vSaisieMasqQT</pre>

===Example===
For example, with the Mur Saint-Martin dataset you can launch :
<pre>mm3d SaisieMasqQT IMGP4173.JPG Attr=MonPlan</pre>

* '''How to use SaisieMasqQT explained in this tutorial :'''
{{#ev:youtube|https://www.youtube.com/watch?v=dMxhD7UBEGE}}

Install MicMac Ubuntu

2018-07-10T05:30:03Z

Harlock : "Install Github" -> "Install Git" (Github is not Git)

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 ==

The MicMac project is now hosted on the GitHub platform.
''On the former Mercuriel server (https://geoportail.forge.ign.fr/hg/culture3d), no source code updates will be applied (7017 is the latest revision).''

=== Install Git ===

<pre>sudo apt-get install git</pre>

=== Download the source ===
Go to the installation directory, where you want to install MicMac.

For “optimisation” reasons, the project files were divided into three GitHub sub-projects:

* https://github.com/micmacIGN/micmac : contains the source code of MicMac

* https://github.com/micmacIGN/Documentation : contains the documentation/manuals

* https://github.com/micmacIGN/Papers : contains some publications and other reports concerning MicMac

To retrieve the source code to micmac folder:
<pre>
git clone https://github.com/micmacIGN/micmac.git micmac
</pre>

== Build from sources ==
===Automatically===
The script_jenkins.sh available in micmac repository (or here : [https://github.com/micmacIGN/micmac/blob/master/script_jenkins_unix.sh]) can be used for an automatic compilation from sources.

=== Manually ===

From the installation directory, move to the 'micmac' directory :
<pre>cd micmac/</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 -DWITH_QT5=1 -DWITH_CPP11=1 ..</pre>

<div class="toccolours mw-collapsible mw-collapsed" style="background-color: Lavender">
<h6 style="font-family: Helvetica:font-size: 40px">About option -DWITH_QT5=1</h6>
<div class="mw-collapsible-content">

Use this option if you want to use tools GUI such : SaisieAppuisInitQT, SaisieMasqQT etc... If not, simply use :
<pre>cmake ../</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.

</div>
</div>

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).

==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.<br>
Add the following lines at the bottom of the file :<br>
<code>export PATH=/''micmac_install_directory''/micmac/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.<br>

===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 :<br>
<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/micmac") and type:
<pre>
git pull
</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
*<code>No CMAKE_CXX_COMPILER could be found. </code> => install g++ (sudo apt-get install g++)
*<code>...Could not find a package configuration file provided by "Qt5OpenGL"...</code> => install libqt5opengl5-dev
[[Category:Installation]]

Install MicMac Ubuntu

2017-06-12T06:56:30Z

Harlock : /* Troubleshooting */

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 ==

The MicMac project is now hosted on the GitHub platform.
''On the former Mercuriel server (https://geoportail.forge.ign.fr/hg/culture3d), no source code updates will be applied (7017 is the latest revision).''

=== Install GitHub ===

<pre>sudo apt-get install git</pre>

=== Download the source ===
Go to the installation directory, where you want to install MicMac.

For “optimisation” reasons, the project files were divided into three GitHub sub-projects:

* https://github.com/micmacIGN/micmac : contains the source code of MicMac

* https://github.com/micmacIGN/Documentation : contains the documentation/manuals

* https://github.com/micmacIGN/Papers : contains some publications and other reports concerning MicMac

To retrieve the source code to micmac folder:
<pre>
git clone https://github.com/micmacIGN/micmac.git micmac
</pre>

== Build from sources ==
===Automatically===
The script_jenkins.sh available in micmac repository (or here : [https://github.com/micmacIGN/micmac/blob/master/script_jenkins_unix.sh]) can be used for an automatic compilation from sources.

=== Manually ===

From the installation directory, move to the 'micmac' directory :
<pre>cd micmac/</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 -DWITH_QT5=1 ..</pre>

<div class="toccolours mw-collapsible mw-collapsed" style="background-color: Lavender">
<h6 style="font-family: Helvetica:font-size: 40px">About option -DWITH_QT5=1</h6>
<div class="mw-collapsible-content">

Use this option if you want to use tools GUI such : SaisieAppuisInitQT, SaisieMasqQT etc... Instead, use :
<pre>cmake ../</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.

</div>
</div>

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).

==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.<br>
Add the following lines at the bottom of the file :<br>
<code>export PATH=/''micmac_install_directory''/micmac/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.<br>

===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 :<br>
<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/micmac") and type:
<pre>
git pull
</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
*<code>No CMAKE_CXX_COMPILER could be found. </code> => install g++ (sudo apt-get install g++)
*<code>...Could not find a package configuration file provided by "Qt5OpenGL"...</code> => install libqt5opengl5-dev
[[Category:Installation]]

Install MicMac Ubuntu

2017-06-12T06:50:44Z

Harlock : /* Errors with cmake */

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 ==

The MicMac project is now hosted on the GitHub platform.
''On the former Mercuriel server (https://geoportail.forge.ign.fr/hg/culture3d), no source code updates will be applied (7017 is the latest revision).''

=== Install GitHub ===

<pre>sudo apt-get install git</pre>

=== Download the source ===
Go to the installation directory, where you want to install MicMac.

For “optimisation” reasons, the project files were divided into three GitHub sub-projects:

* https://github.com/micmacIGN/micmac : contains the source code of MicMac

* https://github.com/micmacIGN/Documentation : contains the documentation/manuals

* https://github.com/micmacIGN/Papers : contains some publications and other reports concerning MicMac

To retrieve the source code to micmac folder:
<pre>
git clone https://github.com/micmacIGN/micmac.git micmac
</pre>

== Build from sources ==
===Automatically===
The script_jenkins.sh available in micmac repository (or here : [https://github.com/micmacIGN/micmac/blob/master/script_jenkins_unix.sh]) can be used for an automatic compilation from sources.

=== Manually ===

From the installation directory, move to the 'micmac' directory :
<pre>cd micmac/</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 -DWITH_QT5=1 ..</pre>

<div class="toccolours mw-collapsible mw-collapsed" style="background-color: Lavender">
<h6 style="font-family: Helvetica:font-size: 40px">About option -DWITH_QT5=1</h6>
<div class="mw-collapsible-content">

Use this option if you want to use tools GUI such : SaisieAppuisInitQT, SaisieMasqQT etc... Instead, use :
<pre>cmake ../</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.

</div>
</div>

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).

==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.<br>
Add the following lines at the bottom of the file :<br>
<code>export PATH=/''micmac_install_directory''/micmac/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.<br>

===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 :<br>
<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/micmac") and type:
<pre>
git pull
</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
*<code>No CMAKE_CXX_COMPILER could be found. </code> => Try to install g++ (sudo apt-get install g++)
[[Category:Installation]]

StatIm

2017-02-18T08:20:57Z

Harlock : Description added.

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
Display grey value of a given pixel of a greyscale tif image, or average value of an aera. Hence, could be used to retrieve altitudes from 16 bits depth maps.

Applied to a color image, it gives first channel (usually red) value.
===Syntax===
The global syntax for StatIm is<br>

<pre>mm3d StatIm FullName Origin Size</pre>

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

Mandatory unnamed args :
* string :: {Image name}
* Pt2di :: {Point or Origin of rectangle}
Named args :
* [Name=Sz] Pt2di :: {Size of rectangle (Def=[1,1])}

===Output===
* ZMoy : average grey (or first channel) value, or average altitude for depth map.
* Sigma
* ZMinMax : minimum and maximum grey values or altitudes.

==Example==
<pre>mm3d StatIm DSC_6217.TIF [0,0] Sz=[4288,2848]</pre>

StatIm

2017-02-17T14:20:47Z

Harlock : Page creation.

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
Basic stats on a tif image.
===Syntax===
The global syntax for StatIm is<br>

<pre>mm3d StatIm FullName Origin Size</pre>

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

Mandatory unnamed args :
* string :: {Image name}
* Pt2di :: {Point or Origin of rectangle}
Named args :
* [Name=Sz] Pt2di :: {Size of rectangle (Def=[1,1])}

===Output===
* ZMoy : average grey (or first channel) value
* Sigma
* ZMinMax : minimum and maximum grey values

===Example===
<pre>mm3d StatIm DSC_6217.TIF [0,0] Sz=[4288,2848]</pre>

Tawny

2017-02-16T03:46:05Z

Harlock : formule numbers and some complement in args descriptions.

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
The simplified tool for generating ortho mosaic is Tawny, it is an interface to the [[Porto]] tool. The use of Tawny is quite simple because it assumes that the data have been correctly prepared and organized during the matching process. Practically this is done when the matching has been made using [[Malt]] and it is recommended to only use Tawny in conjunction with [[Malt]]. In Ortho Mode, Malt has created a set of individual ortho images, associated mask, incidence image, . . . in a directory Ortho-MEC-Malt/
The job of Tawny is essentially to merge these data and to optionally do some radiometric equalization.

For the radiometric equalization, Tawny will compute for each individual ortho image <math>O_i</math> a polynom <math>P_i</math> such that, <math>∀(i, j, x, y)</math> where ortho image <math>O_i</math> and <math>O_j</math> are both defined in at the ground coordinates <math>(x, y)</math> we have the relation:
*<math>O_i(x, y)*P_i(x, y) = O_j(x, y)*P_j(x, y)</math>    (1)

The problem with such formula is that it can lead to important drift in radiometry. So there is also a global polynom R that is computed, this polynom is such that:
*<math>O_i(x, y)*P_i(x, y)*R(x, y) = O_i(x, y)</math>    (2)

The radiometry of each image used for the ortho photo will finally be <math>O_i(x, y)P_i(x, y)R(x, y)</math>. Of course for equation (1) and (2), there is much more observations than unknowns and they are solved using least mean square. The user can control the radiometric equalization by specifying the degree of the polynom.

===Syntax===
The global syntax for Tawny is :
<pre>mm3d Tawny Directory NamedArgs</pre>

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

Mandatory unnamed args :
*string :: {Data directory}

Named args :
*[Name=DEq] INT :: {Degree of equalization (degree of polynoms Oi), Def=1}
*[Name=DEqXY] Pt2di :: {Degree of equalization, if diff in X and Y}
*[Name=AddCste] bool :: {Add unknown constant for equalization (Def=false)}
*[Name=DegRap] INT :: {Degree of rappel to initial values (degree of global polynom R), Def = 0}
*[Name=DegRapXY] Pt2di :: {Degree of rappel to initial values when different in X and Y, Def = 0}
*[Name=RGP] bool :: {Rappel glob on physically equalized, Def = true}
*[Name=DynG] REAL :: {Global Dynamic (to correct saturation problems)}
*[Name=ImPrio] string :: {Pattern of image with high prio, def=.*}
*[Name=SzV] INT :: {Sz of Window for equalization (Def=1, means 3x3)}
*[Name=CorThr] REAL :: {Threshold of correlation to validate homologous (Def 0.7)}
*[Name=NbPerIm] REAL :: {Average number of point per image (Def = 1e4)}
*[Name=L1F] bool :: {Do L1 Filter on couple, def=true (change when process is blocked)}
*[Name=SatThresh] REAL :: {Threshold determining saturation value (pixel >SatThresh will be ignored)}
*[Name=Out] string :: {Name of output file (in the folder)}

===Example===
For example in the Mur Saint Martin dataset (or whenever "[[Malt]] Ortho" was used without the "DirMEC" option changed), you can launch :
<pre>mm3d Tawny Ortho-MEC-Malt/</pre>

Nuage2Ply

2017-02-10T05:34:54Z

Harlock : /* Help */ Correction signe Offs example (cf Additional comments)

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
Nuage2Ply is used to convert a depth map (or DEM when applicable) to a point cloud in ply format. The color of an image can be projected to the points (option "attr"). In case of a DEM (classically computed by "[[Malt]] Ortho"), the ortho-image mosaic computed by [[Tawny]] can be used.

===Syntax===
The global syntax for Nuage2Ply is :
<pre>mm3d Nuage2Ply XMLFile NamedArgs</pre>

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

Mandatory unnamed args :
*string :: {Name of XML file}
Named args :
*[Name=Sz] Pt2dr :: {Sz (to crop)}
*[Name=P0] Pt2dr :: {Origin (to crop)}
*[Name=Out] string :: {Name of result (default toto.xml => toto.ply)}
*[Name=Scale] REAL :: {Do change the scale of result (def=1, 2 mean smaller)}
*[Name=Attr] string :: {Image to colour the point}
*[Name=Comments] vector<std::string> :: {Commentary to add in the ply file (Def=None)}
*[Name=Bin] INT :: {Generate Binary or Ascii (Def=1, Binary)}
*[Name=Mask] string :: {Supplementary mask image}
*[Name=SeuilMask] REAL :: {Theshold for supplementary mask}
*[Name=Dyn] REAL :: {Dynamic of attribute}
*[Name=DoPly] INT :: {Do Ply, def = true}
*[Name=DoXYZ] INT :: {Do XYZ, export as RGB image where R=X,G=Y,B=Z}
*[Name=Normale] INT :: {Add normale (Def=false, usable for Poisson)}
*[Name=NormByC] INT :: {Replace normal (Def=0, 2=optical center 1=point to center vector)}
*[Name=ExagZ] REAL :: {To exagerate the depth, Def=1.0}
*[Name=RatioAttrCarte] REAL
*[Name=Mesh] bool :: {Do mesh (Def=false)}
*[Name=64B] bool :: {To generate 64 Bits ply, Def=false, WARN = do not work properly with meshlab or cloud compare}
*[Name=Offs] Pt3dr :: {Offset in points to limit 32 Bits accuracy problem ; example : Offs=[300000,5000000,0]}
*[Name=NeighMask] string :: {Mask for neighboors when larger than point selection (for normals computation)}
*[Name=ForceRGB] bool :: {Force RGB even with gray image (Def=true because of bug in QT)}

===Additional comments===
The RatioAtrCarte that scaled the image to the same size as the depth map (or DEM) is automatically computed since mid 2014.

The Offs parameter exist to compensate for the maximum number of digits per number that can be stored in a 32bits ply file, too low to store accurate coordinates in a system like UTM where the coordinates are offseted by millions (Typical coordinate (Easting, Northing) looks like : 425170 8763100). The offset substract the given values to the points coordinates:
<pre>Pt orig = [425170 8763100 100]
Offs = [420000 8760000 100]
Pt Cor = [2170 3100 0]</pre>

===Example===
For example, with the Ramses dataset, you can launch :
<pre> mm3d Nuage2Ply NuageImProf_STD-MALT_Etape_8.xml Attr=../Ortho-MEC-Malt/Ortho-Eg-Test-Redr.tif RatioAttrCarte=2 Scale=2 </pre>

Nuage2Ply

2017-02-01T11:51:23Z

Harlock : Example for offset syntax

[[Image:picto-liste.png|25px]] [[Command|List of commands]]
==Description==
Nuage2Ply is used to convert a depth map (or DEM when applicable) to a point cloud in ply format. The color of an image can be projected to the points (option "attr"). In case of a DEM (classically computed by "[[Malt]] Ortho"), the ortho-image mosaic computed by [[Tawny]] can be used.

===Syntax===
The global syntax for Nuage2Ply is :
<pre>mm3d Nuage2Ply XMLFile NamedArgs</pre>

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

Mandatory unnamed args :
*string :: {Name of XML file}
Named args :
*[Name=Sz] Pt2dr :: {Sz (to crop)}
*[Name=P0] Pt2dr :: {Origin (to crop)}
*[Name=Out] string :: {Name of result (default toto.xml => toto.ply)}
*[Name=Scale] REAL :: {Do change the scale of result (def=1, 2 mean smaller)}
*[Name=Attr] string :: {Image to colour the point}
*[Name=Comments] vector<std::string> :: {Commentary to add in the ply file (Def=None)}
*[Name=Bin] INT :: {Generate Binary or Ascii (Def=1, Binary)}
*[Name=Mask] string :: {Supplementary mask image}
*[Name=SeuilMask] REAL :: {Theshold for supplementary mask}
*[Name=Dyn] REAL :: {Dynamic of attribute}
*[Name=DoPly] INT :: {Do Ply, def = true}
*[Name=DoXYZ] INT :: {Do XYZ, export as RGB image where R=X,G=Y,B=Z}
*[Name=Normale] INT :: {Add normale (Def=false, usable for Poisson)}
*[Name=NormByC] INT :: {Replace normal (Def=0, 2=optical center 1=point to center vector)}
*[Name=ExagZ] REAL :: {To exagerate the depth, Def=1.0}
*[Name=RatioAttrCarte] REAL
*[Name=Mesh] bool :: {Do mesh (Def=false)}
*[Name=64B] bool :: {To generate 64 Bits ply, Def=false, WARN = do not work properly with meshlab or cloud compare}
*[Name=Offs] Pt3dr :: {Offset in points to limit 32 Bits accuracy problem ; example : offs=[-300000,-5000000,0]}
*[Name=NeighMask] string :: {Mask for neighboors when larger than point selection (for normals computation)}
*[Name=ForceRGB] bool :: {Force RGB even with gray image (Def=true because of bug in QT)}

===Example===
For example, with the Ramses dataset, you can launch :
<pre> mm3d Nuage2Ply NuageImProf_STD-MALT_Etape_8.xml Attr=../Ortho-MEC-Malt/Ortho-Eg-Test-Redr.tif RatioAttrCarte=2 Scale=2 </pre>