An interferometric imaging package
Within the current release, posts addressing known bugs are organized into categories reflecting their respective statuses, which may include being fixed but pending distribution or still pending resolution. For information about resolved issues in prior releases, please access the documentation menu.
Bug corrected in the distributed version 4.0 (and beyond):
PIPELINE /MODE SURVEY was not working properly when strong lines were present in spectral window, because line subtracting was improperly done, and contaminated the full bandwidth.
Note that the PIPELINE /MODE ALL with NO Catalog was similarly affected, whereas other modes (including PIPELINE /MODE ALL with a Catalog) were not affected by this issue.
Bug corrected in the distributed version 4.0 (and beyond):
Description: PIPELINE crashes (in Survey mode): Continuum image could not be created.
This was due to incorrect channel flagging when a strong/broad line is present close to the edge of a frequency band. In some cases, too many (if not all) channels were flagged, resulting in no continuum channels.
Recommandation: you may test first the line identification with the UV_PREVIEW command before starting the imaging process with the PIPELINE (adjusting TAPER, SMOOTH and CLIP variables may help, if the problem persists in exotic cases).
Solved 29-Sep-2023: UV_MERGE Merging UV Tables in CONCATENATE or CONTINUUM modes was sometimes causing a crash or blocking Imager.
Solved 30-Sep-2023: READ Reading a Mosaic with more fields than the previous one was causing a crash.
Solved 03-Oct-2023: UV_MERGE Merging spectral line UV Tables in CONTINUUM Mode was leading to incorrect baseline lengths (Work-around: convert the Spectral line UV tables to Continuum ones first using UV_CONTINUUM and merge the later)
Solve 04-Oct-2023: UV_CORRELATE and UV_DETECT were fixed.
PIPELINE in SPLIT mode was creating “continuum” Tables with line emission included. (in versions up to v3.9-05)
Status: Solved but not in versions up to v3.9-05
TEMPORARY PATCH:
(not seen since a while…) VIEW CCT on data cubes may (rarely) cause occasional crashes. The origin of the bug is most likely related to the pencil colour handling in the graphic library, but yet unidentified. Work around: try again, it may work !
(confirmed 04-Jan-2023) CLEAN may stop with Zero iteration if it already did so because of improper input parameters before, even after resetting the parameters. Probably a missing initialization of some Logical variable. Unfortunately, the only Work-around so far is to restart imager.
01010101010101010101010101010101010101010101010101010
Please, to see a list of pending and solved bugs:
bug category widget visible on many pages of the sitebugs submenu of the support menu