Bug:You cannot flag data when
both averaging and iteration are turned on.
There are modes of operation in which plotxy
is known to be excessively slow.
For data with a large
number of spectral windows and/or channels, iteration
(e.g. over baseline) will be very slow.
Using the extendflag options will greatly
slow down the flagging in plotxy. You will
see an excessively long delay
after hitting the Flag button, with lots of logger messages
as it goes through each flag. Fixing this requires a refactoring
of plotxy which is underway starting in Patch 4 development.
Currently, plotxy requires that all the scratch
columns are present in the MS. If you get an error
to the effect:
Invalid Table operation: Table: cannot add a column
then use clearcal() to force these
columns to be made in the MS. Note that this will
clear anything in all scratch columns (in case some
were actually there and being used).
Update: As of Patch 3.0 plotxy will
make missing scratch columns for you, however...
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
you casapy session (exit and start again) to
free up the cache.
Update: As of Patch 4, 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
cal-table was created.