-- GillesDuvert - 01 Jul 2009 This is the V3.0 Help. New Options are in bold face .

amdlibComputeP2vm

 Usage: amdlibComputeP2vm [-h] [-L] [-v level] [-S <i>] [-s <o1>,<o2>,<o3>] <badPixelMap> <flatFieldMap> [<specDark> <specFile1> <specFile2> <specFile3>] <dark> <file1> ... <file9> <p2vmFile>
 or
        amdlibComputeP2vm [-h] [-v level] [-S <i>] [-s <o1>,<o2>,<o3>] <badPixelMap> <flatFieldMap> [<specDark> <specFile1> <specFile2>] <dark> <file1> ... <file4> <p2vmFile>
  where:
    <specDark>,<specFile1>... is the comma-separated list of     files to perform spectral calibration

Options:

```
-s <o1>,<o2>,<o3>
```
comma-separated list of shifts for the 3 photometric channels (EVEN with 2T: Use then a dummy 3rd value). If given, no spectral calibration is done, and these shifts are used instead. The correct value is more or less the one given in the ATF report and explained HERE. The value written in the raw data files and used by the programs if no such option is given is usually FALSE.
```
--S <i>
```
The wavelength table will be shifted by PIXELS this amount (+ is towards longer wavelengths). This to correct from spectrum-centering problems that appear mainly at Low Resolution.

--L <N>
linearize P2VM phase (experimental): instead of computing the phase between the real and imaginary part of the P2VM independently for each spectral element, filter the values with a boxcar of N wavelength. 20 is OK. Minimises noise. Not used if Low Res.

--N Normalize P2VM to visibility 1. It is a good idea to use this flag. Raw visibilties are more realistic.

-h help

-v verbosity level [0..4]

-t test

--D <nfram>
to drop the first frames. Absolutely MANDATORY until the bias effects on the camera have been mastered. Drop at least 3 Frames on 10, 20 on 100.

-n to avoid applying global bias estimate and correction. This should be used along with the -D option. If you drop frames, you do not need the global bias estimate.

The default command should be something like that:
-amdlibComputeP2vm -D3 -n -L20 -s <o1>,<o2>,<o3> <badPixelMap> <flatFieldMap> <dark> <file1> ... <file10> <p2vmFile>
Note that the Spec Files are NOT USED anymore .
amdlibComputeOiData

Usage: amdlibComputeOiData [-h] [-f] [-s] [-v level] [-b <num>] [-p PHASOR] [-e STATISTIC|THEORIC] [-c FLUX|FRG|OPD] [-r <ratio>] [-B J|H|K] <badPixelMap> <flatFieldMap> <p2vm> <dark> <input> <output> Options: -h help -v verbosity level [0..4] -f force the use of another P2VM -s split OI-FITS; one file per band -b <num> of frames to average (bin) over <num> frames -p PHASOR (default) for piston algorithm -e THEORIC (default) or STATISTIC for error bars estimation -c FRG, FLUX or OPD criterion for frame selection -r <ratio> for frame selection if 0<ratio<=1, its a ratio, else it is a threshold. flux are in (e), OPD in microns. -B J, H or K to select a spectral band

-J to tag Pistons with Jitter/Error gt. value (in microns)

-X to tag visibilities with chi2 gt. value. This removes P2VM fits of complex coherent fluxes that did not behave well, that is, above some chi2. The default is -X0 , that is: tag data whose chi2 is above the mean chi2 by 3 times the chi2 rms. -X -1 or any negative value tages nothing. Normally AMBER data gives a mean chi2 between 0.9 and 1.8. Thus, -X 1.8 would select "normal" frames.

-C to enhance piston precision using piston closure info. To be used with caution: The idea is to compute the piston on the baseliens with the smallest S/N as minus the sum of the two others. useful sometimes in Low Res.

-P to retain photometries gt. value (in e). Default is 0, and default should not normally cause problems.

-F to avoid using the continuum correction factor. This linearisation factor is part of the new way to reduce AMEBR data. Wizard only.

-D to drop the first frames. Absolutely MANDATORY until the bias effects on the camera have been mastered. Drop at least the first 20 or 30 frames if possible. For FINITO-assisted data when the number of frames is too small, just pray .

-n to avoid applying global bias estimate and correction. This should be used along with the -D option. If you drop frames, you do not need the global bias estimate.

-S to normalize star's spectrum by the spectrum of the P2VM (not exactly a transmission, the optical path being different: mostly useful in LowRes.). Wizard only.

The default command should be something like that:
amdlibComputeOiData -D30 -n -b 99999 -p PHASOR -e THEORIC -s <badPixelMap> <flatFieldMap> <p2vm> <dark> <input> <output>
Note that it is recommendend to avoid selection (option -b 9999) unless you are in Low Res, where selection on PISTON ( -c OPD -r 15 ) would be a good idea if you are interested in differential visibilities.
amdlibAppendOiData

Usage: amdlibAppendOiData [-h] [-v level] <inOiFitsFile1> <inOiFitsFile2> [... <inOiFitsFileN>] <outOiFitsFile> Options: -h help -v verbosity level [0..4]

amdlibPerformFrameSelection

Usage: amdlibPerformFrameSelection [-h] [-v level] [-c FLUX_THR|FLUX_PCG|FRG_THR|FRG_PCG|OPD_THR|OPD_PCG] [-r <ratio>] [-i <inSelFile>] [-o <outSelFile>] <inOiFitsFile> [<outOiFitsFile>] Options: -h help -v verbosity level [0..4] -c <criterion> for frame selection. Possible values are: FLUX_THR - threshold on flux (electron count) FLUX_PCG - percentage of frames kept based on flux selection FRG_THR - threshold on fringe SNR (number) FRG_PCG - percentage of frames kept based on fringe SNR selection OPD_THR - threshold on piston (microns) OPD_PCG - percentage of frames kept based on piston selection -r <value> frame selection value -i <inSelFile> input selection file -o <outSelFile> output selection file