Next: Revision History
Up: Bugs and Release Notes
Previous: Functional changes from previous
Contents
This section contains the list of bugs corrected much longer ago...
- Corrected 28-Jun-2021 magentaUV_SHIFT bug correction for "false" mosaics (ID and MOFF columns)
- Corrected 28-Jun-2021 magentaUV_SORT bug correction for magenta/FILE option
- Discovered and Corrected 27-Oct-2021 magentaMAP_INTEGRATE lead to wrong units
and noise level.
- Discovered and Corrected 04-Apr-2021 magentaMULTISCALE was using an incorrect convergence
strategy since years... Results were sub-optimal, and convergence was unduly slow.
- Discovered and Corrected 31-Jan-2021 magentaUV_MAP /RANGE was producing
a wrong velocity/frequency axis since 11-Dec-2020. (a line of code had disappeared).
- Discovered and Corrected 10-Dec-2020 magentaMODEL after magentaUV_FIT was
ending with an undue error (bug present since 2-Jun-202
- corrected 8-Dec-2020 Mosaic offsets were not accounted for properly
since 19-Jun-2019. The reason was a misplaced exclamation mark that
transformed a key instruction into a comment in the code file.
Anomalous behaviour of the Mosaic mode were reported end of November,
and a test case isolated on Dec 7 for analysis, leading a prompt correction.
- corrected 26-Oct-2020 Several bugs in magentaUV_MERGE
made it fail on some (usually large) data files, sometimes depending
on the order in which they were given (discovered 15-Oct-2020).
- corrected 14-Sep-2020 Incorrect transfer of self-calibration solution in magentaAPPLY
and magentaSELFCALAPPLY on some UV data set from ALMA.
- corrected 11-Sep-2020 magentaKEPLER was off by 1 pixel.
- corrected 11-Sep-2020 Blanking was not updated in magentaMASK APPLY
- magentaUV_SHORT /REMOVE does not properly delete the SHORT%
variable in some cases, in particular if command magentaXY_SHORT is (or has been)
used (discovered 15-Feb-2020, still pending, difficult to reproduce).
- corrected 10-Jul-2020 [rgb]1,0,0IMAGER occasionally crashed after
a sequence of magentaUV_MAP /CONT and magentaUV_RESTORE commands,
because of a map size mismatch. This size mismatch occured when the
baseline min-max of the UV data set are inconsistent with the UV data.
(discovered 07-Jul-2020).
- corrected 10-Jun-2020
magentaKEPLER does not handle blueKEPLER_X0 and blueKEPLER_Y0 properly.
- corrected 20-May-2020
magentaFITS fails on large (300 GBytes..) UVFITS files.
(discovered 15-Feb-2020).
- corrected 19-Mar-2020 magentaMODEL /MINVAL threshold was erroneously
transformed between Jy/beam and K.
- corrected 10-Mar-2020 magentaMAP_RESAMPLE may crash on some combination of values
(discovered 10-Mar-2020).
- corrected 10-Mar-2020
magentaVIEW may fails the blueRANGE is
non zero and the 3rd axis increment is negative.
- corrected 05-Mar-2020
magentaUV_MAP fails after magentaUV_RESIDUAL and magentaSELECT UV_RESIDUAL
if the initial UV data set was not sorted in XY.
- corrected 05-Mar-2020
magentaMULTI with non-zero value for blueCLEAN_NITER did not set up
properly the number of components (it finds 0). magentaSHOW CCT and
magentaUV_RESTORE could not be used after.
Next: Revision History
Up: Bugs and Release Notes
Previous: Functional changes from previous
Contents
Gildas manager
2023-06-01