[Casa-framework] update on previous mp comments
Lindsey Davis
ldavis at nrao.edu
Wed Oct 25 14:45:46 EDT 2006
Hi Everyone,
Awhile back I sent in some comments on the mptool and how I would like
it to work when displaying multiple data sets. I just thought I would
let everyone know that the scenario I outlined below appears to be working
in version #1489 and was not in #1480! Thanks everyone.
Joe's workaround using the single builtin mp tool and multiple data set
opens now works for me as well. In the previous version I was using the
new open would blow away the plotting window ...
By the way is the proper way to cleanly close the plotting window
pl.close
This works but ?
Lindsey
>
>Hi,
>
>Since I started a thread on multiple mp tools I thought I would tell people
>where I ended up with this.
>
>For what I want to do the 2 instances of casapy work best and involve
>the least setup and typing.
>
>However I thought I would try something like the following as well.
>
>1. Create my own mp tool instances mpraw and mpred
>
>2. Open the data sets
>mpraw.open <raw_data_set>
>mpred.open <reduced_data_set>
>
>3. Set the plot options
>mpraw.plotoptions subplot=211
>mpred.plotoptions subplot=212
>
>4. Set the data options
>mpraw.setdata ...
>mpred.setdata ...
>
>5. Make the plots
>mpraw.vistime ...
>mpred.vistime ...
>
>6. Repeat 5 for all plot types of interest. Reset data selections and
>repeat 5 for all plots of interest.
>
>7. Close the data sets.
>mpraw.close
>mpred.close
>
>This should result in the minimum amount of setup and typing. It all
>seems to work except step 6. If I try to follow vistime by vischannel
>plots, keeping the plot setup and data selection the same, I get plotting
>errors. What seems to be happening is that the plot still thinks it
>should have a time axis not a channel axis. Interestingly enough I can do
>vischannels plots followed by vistimes plots, but the next vischannels
>cause the same axis realted error I saw the first time. From this I
>conclude that this scheme should work in principal, but there is an axis
>reset bug somewhere. Is this true or is this scheme flawed ?
>
>By the way what started me off on this was 1) translating the pipeline user
>test visibility plotting instructions from Glish to Casapy, 2) trying to
>examine the raw and reduced pipeline test data sets with casapy in the
>most efficient way.
>
>
>
>
> Lindsey
More information about the Casa-framework
mailing list