This topic aims to collect each changes commited in the beta version in provision of the future release. It mainly concerns the "core" of amdlib, i.e., the C code library and all the amdlibXXX shell commands and their numerous options. Note that while the namesake amdlib Yorick interface, which presents simpler options and add visualization tools, should be preferred over the shell commands for the general user, reading these notes can be enlightening.

If you are interested by the beta release, please contact the jmmc user support to get access to the download page.

V3.0.6b2

• corrected bug reported by Armin Gabasch (ESO) where a zeroing of arrays used in amdlibComputeSpectralCalibration was not properly done depending on processor architecture. Possibly explains in retrospect some spectral calibration problems.
• update yorick revision (yorick-2.2.00x) that fixes some bugs encountered by linux users on recent machines.
• update specCalShifts in amdlibComputeP2vm with the default value for LR and MR but HR since the intervention of 2013-01.Ticket #451
• reduce the length of the INFO field into the browser, to better display info (fix bug on some linux boxes). Ticket #456

V3.0.6b1

• amdlibCalibrateAllOiData now reorder the baselines before writting the OIDATA product file so that they should appear in the same order as in the RAW data (if not possible, an warning is issued). Ticket #367.
• Patch (to be tested thoroughly): The repositioning errors of the grating/prism turret are not taken into account by the existing observation software (on the instrument at Paranal). Consequently the wavelength for each spectral channel may be inaccurate: they are shifted by an unknown amount (between 0 and 15 pixels). This is somewhat corrected during the computation of the P2VM matrix (command amdlibComputeP2vm) by measuring the position of the phase shift between the system of fringes in H and the one in K. The autoShift mode (option -a) of amdlib has been introduced to this effect. However, there have been reports that the wavelength were sometimes shifted by an enormous and unphysical amount, mainly in recent (> 2011) observations. It seems that the algorithm is too sensitive to the exactness of the displacement of the photometric channels (another AMBER curse due to misalignment of the roof prisms used to separate photometric channels). With this patch, computation of the p2vm proceeds in 2 steps. The first step uses 'global photometry' to get an estimate of the wavelength shift, since with global photometry one does not depend anymore on the photometric channels displacement. The second step is done as usual and computes the rest of the p2vm values. Note that in LR mode the value of the photometric channels displacement is really important since we need to separate the J H and K bands! Please be aware that this step is crucial and should not be used without double-checks of the wavelength table (example: if you notice that your wavelength range is within the visible, well, something's wrong!)

Old note: There was a naming convention problem concerning beta packages V3.1b1 to V3.1b4 . Some have been distributed (between jully 2010 and March 2011) and correspond to some previous versions of the V3.0.2. Impacted Users have been warned and wrong numbered tags have been removed from the source code repository. Apologize for inconvenience -- Guillaume