No reported bug since a while from abroad, but new features and subtle issues
discovered while developping !
- 30-Nov-2024 Improve behaviour of commands
UV_MERGE, UV_LINEARIZE, UV_PREVIEW
for non regular frequency axis, in particular add mode
STITCH to
UV_MERGE
- 05-Nov-2024
MAP_POLAR improvement
- 21-Oct-2024
READ UV now support Stokes parameter handling.
-
Corrected 25-Oct-2024
CLEAN /RESTART was broken (in some cases)
since 13-Jun-2024, when dynamic arrays were introduced fro Clean components.
It was ignoring components when a MASK was used.
-
Corrected 10-Oct-2024
VIEW FileName/NOPAUSE was still pausing.
-
Corrected 10-Oct-2024
VIEW FileName/NOPAUSE was still pausing.
- Added 07-Oct-2024
PROPER_MOTION now accepts an optional epoch
- Added 01-Oct-2024
UV_STAT /PLOT command for a graphic display
of results (beam shapes or weight distribution)
- Added 15-Sep-2024
UV_CHOP command to split UV tables in several
sub-entities (e.g. per date, per pointing, etc...)
- Added 15-Sep-2024
REPORT command to generate summary PDF reports
after
PIPELINE execution.
- Added 29-Aug-2024
AMPLITUDE command to rescale antenna gains.
-
Corrected 22-Jul-2024 Ensure
UV_RESTORE works for Mosaics after command
GCLEAN.
-
Discovered 17-Jul-2024,
Corrected Same day
PIPELINE
produced line contaminated continuum data in mode
SPLIT, in two (different)
occasions. 1) Spectral lines not in catalog were not filtered, contrary to expectations.
2) Because of different weights (sometimes null) at edges due to window shifts (e.g.
Doppler correction), the filtering was including inconsistent continuum emission.
The later case is only partially solved, and may require trimming edge channels
of the UV tables.
- Added 16-Jul-2024 Command
GCLEAN, a Clean using the GAUSS
method for multi-scale decomposition. For Mosaics as well as Single Fields.
- Added 03-Jul-2024 Better support of FITS:
SET FORMAT command and associate
WRITE keywords
- 13-Jun-2024 Use a dynamic Clean Component List to save memory, and remove
obsolete code.
-
Corrected 24-May-2024 FITS files produced by Casa did not include the
celestial frame. Although FITS mandates that J2000.0 (FK5) should be used in such case,
ALMA actually produces data only in the ICRF reference frame. As GILDAS and
IMAGER are using FK5, coordinates were not necessarily matching. Solved
by setting the frame to ICRF when importing ALMA data (based on observatory).
Proper solution requires a correction in Casa.
- Added 07-May-2024 Simpler syntax for
SPECIFY and
MOMENTS commands.
