Known Issues

Most Important Issues

  • VLA data taken on 20 September 2017 and later contain an additional Tcal entry for solar observations. CASA 5.0 and earlier will fail in gencal to calculate requantizer gains. Use CASA 5.1 and later for such data. 
  • If you're using CASA 4.2.2, and you want to use a data set that was filled with CASA 4.3.0 or later, you may encounter an error about missing spws. To fix, run "!fixspwbackport msname" within CASA on Linux. msname is the name of the MeasurementSet.
  • Restructuring of the clean task is ongoing and tclean is actively being developed. Standard imaging is commissioned in tclean, but is still undergoing internal testing; please report bugs you find to the Helpdesk. The task clean is no longer being actively maintained. 
  • Currently, gaincal will not find good solutions if any correlation (including cross-correlation) in the data is completely flagged. As an interim solution one may split the unflagged data in a separate file and then perform gaincal
  • Plotting the virtual model in plotms fails when it was created in clean with imagermode='mosaic' and ftmachine='mosaic', or gridmode='aprojection'. And it also fails in tclean when gridder='mosaic' or gridder='awproject'
  • CASA is not using LD_LIBRARY_PATH anymore but CASALD_LIBRARY_PATH to avoid confusion.      
  • cvel is calculating the velocity incorrectly for ephemeris objects. We recommend to use mstransform or its offspring cvel2, although the latter should be used with care as it is not fully commissioned yet.


  • importasdm: if you see errors like " ::asdm2MS locale::facet::_S_create_c_locale name not valid", there is a problem with your locale shell environment variables. One way of getting importasdm to work is to run:
    export LC_ALL=“en_US.UTF-8”
    export LANG=“en_US.UTF-8”
    before starting CASA. This issue can happen on machines which have a locale setting which makes the output of decimal fractions use a comma instead of a decimal point.
    Starting CASA 5.4.0, the locale settings are done within CASA and should no longer be an issue

NFS mounted disks

  • It is not recommended that you run CASA (e.g. have your data) on disks that are NFS mounted. It can be done, but in some cases the files will be NFS locked and this can crash CASA or its tasks. In this case, you have to restart CASA.
  • If you receive messages like xvfb timeout you may try to clean out your /tmp folder, then restart CASA.


  • a bug in ipython (v. 5.1.0) can cause error messages like below. This error occassionally happens when using tget. This is an iphyon issue when the databases are not synchrionized in their line numbering and will start a new log file. The next iphyon update will likey contain a fix.  

    ERROR! Session/line number was not unique in database. History logging moved to new session 318

    CASA <2>:

    ERROR! Session/line number was not unique in database. History logging moved to new session 318



  • Currently, bandpass will not find good solutions if any correlation (including cross-correlation) in the data is completely flagged. As an interim solution one may split the unflagged data in a separate file and then perform bandpass



  • The fluxscale task will generate incorrect results if the flux density calibrator field specified in the reference parameter is also specified among the other calibrators in the transfer parameter.  The auto-genereated transfer field list (transfier='') works ok.



  • Polarization position angle calibration poltype='X' or 'Xf' will be sensitive to any unmodelled position shift in the specified calibrator linear polarization model relative to the centroid location of total intensity (typically the phase center).  Excess phase due to the position shift will introduce a bias in the cross-hand phase calibration (which is the same as position angle calibration in the circular feed basis).   For this reason, it is best to use truly point-like (in all polarizations) calibrators, if possible, or accurate resolved models.


  • sometimes setjy does not properly overwrite a current model in the header of the ms (virtual scratch column). It is recommended to use delmod if a model exists and shall be overwritten.

plotcal (also check the matplotlib section for plotcal issues)

  • When plotcal does not release a calibration table properly but keeps it in lock, try to hit the quit button in the plotcal GUI first. Then redisplay the table.
  • If you use plotcal on a caltable, it will then be put into the cache of the table system. If you try to re-run a solve (e.g. gaincal, bandpass, blcal, polcal) with the same caltable name and append=F to overwrite, then when it tries to delete the original caltable it cannot due to the cache. You will see an error like:

    SEVERE  gaincal::Calibrater::solve
    Caught exception: Invalid Table operation: SetupNewTable
    ngc5921.demo.gcal is already opened
    (is in the table cache)

    Either use a different output caltable name, or restart your CASA session (exit and start again) to free up the cache. You can use the rmtables task to delete tables.
  • BPOLY solutions from bandpass must be plotted versus frequency and not channel. BPOLY and B solutions can only be overlaid if xaxis = 'freq'.
  • GSPLINE and G solutions from gaincal can be overlaid, though this has not been extensively tested.
  • Currently, plotcal needs to know the MS from which the caltable was derived to get indexing information. It does this using the name stored inside the table, which does not include the full path, but assumes the MS is in the same directory as the cal-table and has the same name it had when the caltable was created.
  • If there are flagged channels at the lower edge of the data, say, 0~4, and you select a channel and 'locate' it from plotcal, it will give the incorrect channel number (will count from the first unflagged channel, not zero).


  • Unflagging flagged points interactively in plotms does not work when data is time-averaged or channel-averaged.  The data in the plot appears to be unflagged, but if the data is reloaded or the averaging is removed, the data is still flagged.  This will be fixed in the next release.


  • fitorder should be kept low (<= 1) unless the line band is relatively narrow compared to the fit bands. If the image rms markedly rises in the middle line channels after uvcontsub, fitorder should probably be lowered.
  • fitorder > 0 does not work with solint > 'int'


  • SPW combination (combinespws=True) requires that all the SPWs selected have the same number of channels.

CASA cal library

  • The CASA cal library (docallib=True in applycal, gaincal, bandpass, etc.) may exhibit problems when calibration is unavailable for a subset of MS spectral windows.  Use of spwmap to (transparently, harmless) supply nominal calibration for these spectral windows may help avoid this problem.  For antenna position corrections, try spwmap=[0] to relieve a variety of this problem.

VLA Switched Power

  • In CASA v4.2.2 and higher, the weight calibration for EVLA switched power/Tsys corrections is still being investigated. Visibility corrections are ok. Since switched power calibration is not used by the EVLA pipeline (except for requantizer gain corrections, for which this problem is irrelevant), and since calwt=F remains the general recommendation, users should rely on statwt to generate appropriate data weights.


Synthesis Imaging


  • In the clean task, when the modelimage parameter is specified, and a previous model exists on disk with the name 'imagename.model', they are both added before prediction. This can happen if you restart clean to continue a deconvolution, but don't set modelimage='' before doing so.
  • clean expects that all input polarizations are present. E.g. if you have RR and LL dual polarization data and you flagged parts of RR but not LL, clean will ignore both polarizations in slice. It is possible to split out a polarization product with split and image separately. But you will not be able to combine these part-flagged data in the uv-domain.
  • Facets do not always work on Mac OS X. This is frequently due to a built in limit for the number of open files. Per default the setting is usually 256 (use ulimit -a to check). For facets in clean it might be required to set to a higher number, e.g. ulimit -n 2048. All commands must be issued from a bash shell outside CASA.
  • Mask editing in interactive clean does not work reliably when the input MS is in reference frames other than LSRK or TOPO. Two incarnations of the problem were encountered so far: (a) when working in GEO, as on solar system objects, mask editing is impossible. (b) When working in BARY, masks created in CASA 4.0 cannot be edited when they are used as input masks for interactive clean in CASA 4.1. and higher.
  • The Mac OS compilers are different to Linux compilers and some options are not available (e.g. opemmp and sincos). This causes some of the clean procedures, in particularly mosaicking, to be slower on MacOS than on Linux. 


  • MeasurementSets with the frequency axis in decreasing order are now mapped into images with frequencies in increasing order by default. 




  • The CASA viewer does not yet support the entire region shapes and parameters at this stage.
  • Viewer may not properly open saved region files.
  • With the new region panel being used now, It may be advisable to rename the $HOME/.casa/viewer/rc file that stores previous configurations of the viewer.          
  • Viewer - labels are not shown - this can be caused by a conflict between an installed version of PGPLOT and the version of PGPLOT that comes with the non-root version of CASA. If you do have PGPLOT installed in a standard location (e.g. /usr/lib), you may try moving it aside and see if it resolves the problems. If you do encounter this problem, please report it to the CASA team.
  • Some X11 settings can make the viewer unstable. We identified that the line
                Load "glx"
                in /etc/X11/xorg.conf
    is such a setting. If you don't need this line for aother applications, it would be better to have it removed.



  • some tasks, e.g. impv do not work well with GALACTIC coordinates.


  • When running uvmodelfit, the output componentlist does not contain the uncertainty in flux that the task calculates (and displays at the end of the fitting process).



  • corruption of simulated MS by an atmospheric phase screen is only available from the toolkit. simobserve and sm: Under some circumstances, running sm.setnoise and sm.corrupt, or simobserve with thermal noise, twice using the same project name, the noise can be applied a second time, doubling the noise level. Be sure to use different project names for creating different simulations with noise. See for the latest simulation information


Single Dish


  • Difficulty in allocating memory to import/processing of Band 9 (fast-mapped, double-circle) data. Use high-performance machines as workaround.
  • Please avoid using spectral window and channel selection by frequency range. It may occasionally fail. So far, this has only been reported on Mac OS but it may happen on Linux, too.


  • blmode = 'apply' fails when selected data contains SPWs with different number of channels.


  • Due to a limitation of current implementation, row or channel flag status may not be restored properly. This may happen when any rows are flagged.

sflagold and sdplotold

  • Data selection by raster causes an error when it is used in combination with field and/or timerange selection.


  • sdimaging task may fail when more than several MSes are chosen as inputs (infiles) to create single output image. It is because the file descriptor opened by the task exceeds the limit defined by OSes. You can relax the limit of the number of open file descriptors by the command, e.g., ulimit -n 4096 . Note the typical number of file descriptors opened by the task is 35/MS.       

sdcal and sdgaincal

  • Spectra with only one polarization cannot be calibrated.


  • The task intermittently seg faults on Mac OS.

The following issues in the previous releases are fixed

  • sdimprocess behaves differently for images with even and odd number of pixels in mode='basket'.
  • description of parameter 'direction' in Plone and help documents of sdimprocess is wrong.
  • sdsaveold seg faults when importing NOSTAR data with CHBIND larger than 1.
  • sdimaging is slow for MS with multiple antennas.