---+ This topic aims to collect each changes commited in the beta version in provision of the future [[AmberDrsReleaseNotes][release]]. If you are interested by the beta release, please contact the [[http://www.jmmc.fr/support][jmmc user support]] to get access to the download page. 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 ---+ <span class="red">V3.0.4 (or whatever it will be) </span> <br>Here comes a new amdlib version aimed at speedup!: 1 the reduced Chi2 of the fringe fit is kept and stored in the raw visibilities OI-FITS files. To be complete, we should add in a next release the possibility to select visibilities according to this chi2 in =amdlibPerform[Frame]Selection=. 1 contrary to a well enforced useage, tagged values are no more blanked when it is possible. I should have set up a switch to permit this, but it would have been too complicated. So only the flags will really tell if a value is deemed wrong or not, which is what the OI-FITS norm expects, in fact. 1 The =amdlibComputeOiData= program has now a fast (switch =-Z0=) and a fussy (switch =-Z2=) mode. The "fussy" mode is the same as before: inversion of the full covariance matrix previous to complex coherent flux extraction, iteration on piston fit until high precision is reached. The fast mode considers that the covariance matrix is diagonal and the piston is evaluated with less precision. For most cases (especially when the S/N is not bad), the fast mode is enough. And it is fast, especially since the matrix routines have been optimized also. The =-Z1= switch is reserved for an intermediate, "clever" mode based on S/N, that I have not developed yet. 1 The full =O3= optimization with inlining etc is set by default in the =Makefile=. Moreover, the really slow parts of code have been parallelized with =OpenMp pragma=. The speed of =amdlibComputeOiData= (which is the only program really time-consuming in amdlib) scales now roughly with the number of cores, and is now limited by the =cfitsio= reading and writing of files. With =gcc= and modern computers this should be transparent, but one has to test it on several platforms. 1 All these changes have been reported in the =Yorick= interface. To set the speed switch to fast, use =amdlibSetPreference,"fastMode",0=. <br> Additionnally, this version closes two "tickets" we had: 1 Ticket 93: the VISDATA AND VISERR columns in OI_VIS (which are not OI-FITS compliant but ESO compliant) now store the Complex Coherent Fluxes & error (not the complex visibilities). One may use these values (on the RAW OI-FITS obviously) to add, combine and average the coherent fluxes as it likes. 1 Ticket 92: In case of selection averaging (=amdlibPerformFrameSelection=), the phase closure is retained as soon as two baselines are OK (in older versions (amdlib2 and amdlib3.0.1, etc) the phase closure would be deemed valid if the 3 baselines were retained by the selection criterium, giving really too few values for something which is essentially robust). ---+ <span class="red">V3.0.3b2 *not yet online*</span> [[http://trac.jmmc.fr/jmmc-sw/log/jmmc-sw/AMBER/trunk/amdlib?action=stop_on_copy&mode=stop_on_copy&rev=&stop_rev=10488&limit=100&verbose=on][Commits after V3.0.3b1 revision on trunk]] ---+ <span class="red">V3.0.3b1 put online for beta tester on 2011-04-18 (SVN r10488)</span> * 'catalogsDir' preference is now properly defined for the users who are using the binary packages * appendOiData now properly tags appended 'OIDATA_RAW' files as OIDATA_RAW. * amdlibSearchAllStarDiameters now use the UD in H-band. It uses the estimation from only one catalog, the one with the best confidence (in order: Merand, Borde, JSDC). * slight changes in Piston estimation (should be more robust). * a memory leak in amdlibComputePiston2T (typo follwing the change above) has been corrected (10 May 2011). %TWISTY{showlink="Show commit messages from V3_0_2 to V3_03_b1..."}% <verbatim> 2011-04-18 22:31 mella * amdlib/include/amdlibProtected.h: V3.0.3b1 2011-04-18 19:27 duvert * amdlib/src/amdlibUtils.c: Solves Ticket #119 2011-04-12 20:24 fmillour * yoco/packages/yocoGui.i: in yocoGuiErrorBox: add default justify parameter 2011-04-12 20:17 fmillour * yoco/packages/yocoDoc.i: doc work + reactivate yocoDocUdateFunctionsCalls 2011-04-12 20:15 fmillour * yoco/packages/yocoMath.i: update doc 2011-04-05 22:47 duvert * amdlib/src/amdlibVisibilities.c: removed binning information when not binning... 2011-04-05 22:46 duvert * amdlib/src/amdlibMatrix.c: added amdlibRefractiveAirIndex() 2011-04-05 07:39 lebouquj * amdlib/yorick/amdlibCalibrate.i: Update documentation. 2011-04-04 17:47 lebouquj * amdlib/yorick/amdlibCalibrate.i: amdlibSearchAllStarDiameters now use the UD in H-band. It uses the estimation from only one catalog, the one with the best confidence (better confidence are Merand, Borde, JSDC). 2011-03-27 07:02 lebouquj * yoco/packages/oiFitsUtils/oiFitsUtils.i: Fix a bug in oiFitsPloitTfTime. 2011-03-26 04:03 lebouquj * yoco/packages/oiFitsUtils/oiFitsUtils.i: Change the position of legends. 2011-03-26 03:50 lebouquj * amdlib/yorick/amdlibCalibrate.i: Now the default calibration is done not taking into account the FINITO DIT because this is not supported by Paranal 2011-03-25 16:39 duvert * amdlib/src/amdlibPiston.c: solves ticket 82 AND 84 The chi2 as programmed was using the variance of the values (as in any well-behaved chi2). The problem is, in LR mode, the variance on the correlated flux is such (due to the transmission in each band) that only a few channels in the center of the band were really important for the fit, resulting in shallow minima end even aliasing. Also, the constant phase fitted is not realistic since the fringes are distorded by the atmospheric differential piston. Solved (!) by ignoring the variance of the correlated flux measurements, and reducing somewhat the allowed exploration range for the piston, -1.2R to 1.2R. Looks good on any data I have. Modified the method to retrieve from the chi2 an estimate of the goodness of fits and a first approximation to the piston measurement error. Sufficient to tag between good and bad fits for normal useage, including piston closure (note that -C option forces piston closure only for tagged pistons or piston noise above limit given by option -j). 2011-03-22 12:54 mella * amdlib/src/amdlib.sh: Define INTROOT so the yorick code can use it (first reason was for catalogsDir default preference value) 2011-03-18 13:43 lebouquj * yoco/packages/oiFitsUtils/oiFitsUtils.i: Create oiFitsCleanDataFromDummy </verbatim> %ENDTWISTY%
This topic: Jmmc/Software
>
JmmcAmberDrs
>
AmberDrsReleaseNotes
>
AmberDrsReleaseNotesInPrep
Topic revision: r25 - 2011-06-14 - GuillaumeMella
Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback