Plotxy - detailed notes from testing DSS - 31jan07 ########################################################################## data and ms in: /home/sola/dss/casa.testing/casa/misc.testing/plotxy.testing HH80-81, W75N, IRAS 19410, IRAS 20293 A Array, X band Obs, 18may06 AS831_I060518.xp1 VLA Archive file, 30.2 MB in size ------------------------------------------------------ source /home/casa/casainit.csh which casapy /home/casa/linux_rhe/bin/casapy Note: every time I source aips++, it changes my library path and I have to re-source casa. ID Name Right Ascension Declination Epoch 0 1331+305 13:31:08.29 +30.30.32.96 J2000 ** fcal,400uvmax 1 1820-254 18:20:57.85 -25.28.12.58 J2000 ** hh8081 gcal 2 HH8081 18:19:12.10 -20.47.30.93 J2000 ** src 3 2007+404 20:07:44.94 +40.29.48.60 J2000 ** w75n gcal 4 W75N 20:38:36.49 +42.37.34.30 J2000 ** src 5 1925+211 19:25:59.61 +21.06.26.16 J2000 ** i19410 gcal 6 I19410 19:43:11.00 +23.44.35.00 J2000 ** src 7 2015+371 20:15:28.73 +37.10.59.50 J2000 ** i20293 gcal 8 I20293 20:31:12.40 +40.03.16.00 J2000 ** src ID #Chans Frame Ch1(MHz) Resoln(kHz) TotBW(kHz) Ref(MHz) Corrs 0 1 TOPO 8435.1 50000 50000 8435.1 RR RL LR LL 1 1 TOPO 8485.1 50000 50000 8485.1 RR RL LR LL casa importvla(archivefiles=['AS831_I060518.xp1'],vis='src.ms',bandname='X') # summary in 0.summary.txt Bad data as identified in AIPS++ (alter to be 0-based indexing): Need to quack the data 10s at the beginning of each scan index 10,(name = 15), just moved index 1 (name = 4), just moved index 5 (name = 6), no idea, just looks bad # field 1 1331 fcal: ant 10 amps decrease with time # field 2 8081 gcal: ant 10 amps low & variable # field 3 HH8081: ant 10 amps have higher scatter - looks bad # field 4 w75n gcal: ant 10 amps high & variable several ants have dropouts - flagged ant 5 - highly variable - ant looks bad ant 1 is high but appears stable. see how it calibrates (just moved). # field 5 w75n: flag ant 5,10 - gcal bad # field 6 i194 gcal: ant 10 amps high & variable ant 5 very scrappy - techs preparing it for move - don't trust ant 9 dropout on 1st scan first int bad, sideband amps wrong - flag # field 7 i19410: first int bad - flag # field 8 i202 gcal: lost ant 8 & 9 after t=13:23 one drop out in last 1/2 of data ants 7 & 6 ant 5 highly variable - flag # field 9 i20293: ant 5 bad. ants 8,9 - no cal data bracketing source at the end # data looks pretty clean now. # refant = index 12 (name=10) or 20 (name=9) - choose 20 (index 12 works equally well) After calibration I find: # I've got some bad data in 4th from the last slot (fieldid=7) # some solutions are clearly low Now, try to identify that same bad data in CASA using plotxy: ---------------------------------------------------------------------- # get a general sense of how good the data is: plot all source amps as a function of time plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', spwid=0) ##### Time axis is muddled (writing overlaps) when window is first brough up. Should be cleaned up. ##### Only the first source is shown. default should be -1 (all) but it appears to be just fieldid=0 plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', fieldid=-1, spwid=0) ##### no change in what is plotted. fieldid is not working... plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='', spwid=0) ##### no change in what is plotted. cannot select all field names plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=0) # using minimum match to find a number or letter in each source to select all of them... finally worked. # I see there is bad data but can't tell what it is. ##### I want the locate feature back - big time! This is the single most useful function to ID bad data. plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=1, plotsymbol='g.', overplot=True) # Time spent reading from disk : 23.96 sec. # Number of points being plotted : 4987442 # Python Plotting time : 14.2860720158 sec. ###### This is way too long, it took another 10 sec to get the data on the plot window after this message was generated. ##### Thu Feb 1 20:55:48 2007 WARN : [ msplot::setData()] failed! Setdata to spwid=1 is no longer working. spwid=0 is being displayed... Dach. Something is eating up resources - plotter window re-sizing takes many seconds and xload is showing a big load. This is true even though I'm not trying to plot any data. Something has gone bonkers after setdata stopped working. ############################################################ [ msplot::setData()] failed! exit casa and restart... --------------------------------------------------------------------- plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=0) # Time spent reading from disk : 10.12 sec. # Number of points being plotted : 1113925 # Python Plotting time : 2.64247107506 sec. plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=1, plotsymbol='g.', overplot=True) # Time spent reading from disk : 10.17 sec. # Number of points being plotted : 2227645 # Python Plotting time : 5.90987992287 sec. plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=1, plotsymbol='g,', overplot=True) # Time spent reading from disk : 10.21 sec. # Number of points being plotted : 3341365 # Python Plotting time : 7.41264796257 sec. OK, bad data is in both IFs. plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], plotsymbol = 'r, g,') # Time spent reading from disk : 10.18 sec. # Number of points being plotted : 4455290 # Python Plotting time : 10.02176404 sec. ##### Interesting, spwids are now different colors but they are blue & green, not red and green as I specified. Color mapping appears to be off. ##### Note that the number of points plotted increases by 1113925 each time I plot even though the actual number of points plotted doesn't increase. Something is going wrong with the data buffer? Or memory or something. This is bad. ######################################################## plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], plotsymbol = 'b, g,') # Time spent reading from disk : 24.21 sec. # Number of points being plotted : 7215087 # Python Plotting time : 16.3094160557 sec. # time spent reading from disk doubled, number of points it reports are plotted jumped dramatically, only one spwid is plotted in blue pixels. ##### Setdata has failed again - problem is repeatable. # Thu Feb 1 21:11:14 2007 WARN : [ msplot::setData()] failed! Plotter window resizing now takes ~ 30s to complete and xload is showing alot of activity. [ msplot::setData()] failed! exit and restart casa --------------------------------------------------------------------- stop recording timing for now and just restart each time setData fails. plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0], correlations='RR LL', plotsymbol = 'b, g,') ##### multiple plot symbol is not being applied to correlations. It only applies to spwids? # ALL field names: [1331+305, 1820-254, HH8081, 2007+404, W75N, 1925+211, I19410, 2015+371, I20293] So my selection should have given all fields but I'm not sure I see all the data. plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1331', spwid=[0], correlations='RR', plotsymbol = 'r,') [ msplot::setData()] failed! exit and restart casa --------------------------------------------------------------------- plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1331', spwid=[0], correlations='RR', plotsymbol = 'r,') plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1331', spwid=[0], correlations='LL', plotsymbol = 'k,', overplot=True) ##### I want to plot RR and LL at the same time and, when I do, I want them to be 2 different colors. If I plot multiple spwids, I want them to be different colors automatically too. plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1331', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') ##### default should be to plot 1 plot at a time. plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1331', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1', subplot=111) ###### subplot doesn't work during iteration, dach. [ msplot::setData()] failed! exit and restart casa --------------------------------------------------------------------- plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1331', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') ##### Antennas displayed in order are: 4 23 11 8 6 21 22 5 12 15 17 10 19 25 28 3 20 2 7 9 1 27 All but one antenna shows random bad data (only ant20 doesnt). I can't isolate which antenna is bad here. There should only be one bad ant - name 15, id 10. ##### The last plot should only show antenna 27 but it shows 3 - 2 are from the previous plot that it neglects to erase. Are the autocorrelations being plotted???? flagautocorr('src.ms') ##### that was it, bad data was the autocorrelations. So plotxy automatically plots autocorrelations. plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1331', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') # OK, now I can tell that name a15, id a10 is bad. plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') # name a15 is bad the entire track # flagdata only allows selection of an antenna by its ID... # use summary to mapp id to name... flagdata(vis='src.ms', antennaid=10) plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') [ msplot::setData()] failed! exit and restart casa --------------------------------------------------------------------- plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') ##### Dach - name a15, id a10 is still there. Antennas 17 and 27 are missing. Flag data doesn't work? flagdata(vis='src.ms', antennaid=10, unflag=True) plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') ##### all data is now flagged. Nothing remains. Well, the plotting was very fast... [ msplot::setData()] failed! exit and restart casa --------------------------------------------------------------------- dell -r src.ms importvla(archivefiles=['AS831_I060518.xp1'],vis='src.ms',bandname='X') See if this is repeatable: plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') ##### Thu Feb 1 22:21:22 2007 SEVERE : [ msplot::iterplotstart() ] Exception Reported: TPPlotter: From Python. : name 'nan' is not defined [ msplot::setData()] failed! exit and restart casa --------------------------------------------------------------------- plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') - worked this time but I forgot to delete the autocorrelations again. flagautocorr('src.ms') plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') # OK, name a17 exists (note, 20 & 27 appeared to have been flagged online). flagdata(vis='src.ms', antennaid=10) fldlist is ['1', 'h', '2', 'w'] Selected fields are: ['1331+305', '1820-254', 'HH8081', '1925+211', 'I19410', '2015+371', '1820-254', '2007+404', '1925+211', '2015+371', 'I20293'] Whole data set has been selected or use mode argument to select specific subset antenna flags fieldid flag spwid flag ##### I really hate it that the defaults are not used when I don't specify a parameter in a script. This used inputs from plotxy for all fields and spwids. OK here since I specified that antennaid10 should be the only thing flagged within that selection. But this could get you in a lot of trouble if you don't constantly go on line and check what global variables are run. This mode of running is OK if you are doing aips-like manual input from the command line, setting each parameter and then checking the inputs, but in a semi-manual script mode, it is horrid. plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') ##### All data looks flagged but antennaid selection appears to still be set (took me 30min to figure this out will all the setData crashes). dell -r src.ms importvla(archivefiles=['AS831_I060518.xp1'],vis='src.ms',bandname='X') flagautocorr('src.ms') plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') [ msplot::setData()] failed! exit and restart casa --------------------------------------------------------------------- plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') restore() inp flagdata flagdata(vis='src.ms', antennaid=10) # humm, different response # 0%....10....20....30....40....50....60....70....80....90....100% # 0%....10....20....30....40....50....60....70....80....90....100% # 0%....10....20....30....40....50....60....70....80....90....100% # 0%....10....20....30....40....50....60....70....80....90....100% # Thu Feb 1 22:39:01 2007 WARN autoflag::run(): # Unable to process this chunk with any active method. # etc... Before, mostly I got the % numbers and only 2 chunks got warnings in the middle of the dataset. Looks like something went wrong. restore() plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') [ msplot::setData()] failed! exit and restart casa - DACH !!!! This setData failure is VERY annoying. --------------------------------------------------------------------- restore() plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') ##### name a15 is still there.... DACH. So is flagdata working or not working. Start over. dell -r src.ms importvla(archivefiles=['AS831_I060518.xp1'],vis='src.ms',bandname='X') restore() flagautocorr('src.ms') restore() plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') ##### [ msplot::setData()] Exception Reported: Error in select expression: expression uses different table *** Error *** Repeated tries don't work. [ msplot::setData()] failed! exit and restart casa --------------------------------------------------------------------- plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') # exact same command now works... # all data is there as I expect. restore() inp flagdata flagdata(vis='src.ms', antennaid=10) # 0%....10....20....30....40....50....60....70....80....90....100% # after 4th chunk: # Thu Feb 1 22:51:31 2007 WARN autoflag::run(): # Unable to process this chunk with any active method. restore() plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') # as far as I can tell, no data has been flagged. ##### setData failures and flagdata not working to get out the worst bad data so I can find more is seriously hampering my ability to figure out how to use plotxy to identify bad data. ############################################################## restore() flagxy(vis='src.ms',antennaid=10, xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], plotsymbol = 'r, g,',) [ msplot::setData()] failed! exit and restart casa --------------------------------------------------------------------- restore() flagxy(vis='src.ms',antennaid=10, xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], plotsymbol = 'r, g,') # interesting, did not set diskwrite=True but it says I can write flags to disk. # I selected all data displayed (as much as I could). # Then typed 'w' to write flags to disk. # Then I got severe error: # Thu Feb 1 23:05:21 2007 SEVERE : # [msplot::flagdata()] Exception Reported: TPPlotter: From Python. # maybe it can't plot when it is all flagged? # q not shown as an option - it should be. restore() flagxy(vis='src.ms',antennaid=10, xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], plotsymbol = 'r, g,') # same error restore() plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') # same error [msplot::flagdata()] Exception Reported: TPPlotter: From Python. exit and restart casa --------------------------------------------------------------------- restore() plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') # odd, now name a17 (id a11) has a blank box. Its not even named on top. So it looks like flagxy also flags the wrong antenna Now I see, I'm looking at an aips++ generated antenna ID listing and it is 1-based.... That is why my name to id conversion is wrong. It doesn't help that the flagging routines are as flakey as plotxy. Totally hosed. start over yet again. dell -r src.ms importvla(archivefiles=['AS831_I060518.xp1'],vis='src.ms',bandname='X') flagautocorr('src.ms') plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') [msplot::flagdata()] Exception Reported: TPPlotter: From Python. exit and restart casa --------------------------------------------------------------------- plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') restore() inp flagdata flagdata(vis='src.ms', antennaid=9) # this should be name a15 - the bad one. # 0%....10....20....30....40....50....60....70....80....90....100% # after 4th chunk: # Thu Feb 1 23:18:15 2007 WARN autoflag::run(): # Unable to process this chunk with any active method. # just like last time. restore() plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') # OK, so first part of the data was flagged- for first source it looks like. it looks like the fieldid/field defaults are defaulting to the first source rather than all of them. try explicitely choosing all fields: restore() inp flagdata flagdata(vis='src.ms', antennaid=9, field='1 h 2 w') # only 2 chunks had the warning error. fieldNames: fieldIndex: [0, 1, 2, 5, 6, 7, 1, 3, 5, 7, 8] # W75N is not selected! # is field selector case sensitive? restore() plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 H 2 W', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') [ msplot::setData()] failed! exit and restart casa --------------------------------------------------------------------- restore() plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 H 2 W', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') # yep, field name selector is case sensitive. I don't think it should be. restore() inp flagdata flagdata(vis='src.ms', antennaid=9, field='W') restore() plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 H 2 W', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') ------------- finally, I got rid of name a15 (0id 9). Now I can see that name a6 (0id 4) is also hosed (as I expected). restore() inp flagdata flagdata(vis='src.ms', antennaid=4, field='1 2 W') restore() plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 2 W', spwid=[0,1], correlations='RR LL', plotsymbol = 'r, g,', iteration='antenna1') # data very close to zero is often plotted just below zero - it looks like there is a plot offsetting problem. # Now I know there are some more marginal antennas that go bad or # offline after a certain time and that have severe dropouts during the # gain cal that I need to get rid of. How to find and flag? ##### Man, do I wish I had a locate function... performance on plotxy is so bad that this laborously going through the data and trying to isolate the bad stuff is so bad that we should never expect users to have to deal with this. restore() plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 2 W', spwid=[0,1], correlations='RR LL', plotsymbol = 'r, g,', iteration='antenna1') [ msplot::setData()] failed! exit and restart casa --------------------------------------------------------------------- restore() plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 2 W', spwid=[0,1], correlations='RR LL', plotsymbol = 'r, g,', iteration='antenna1') # no colors but red are playing. restore() plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1331', spwid=[0,1], plotsymbol = 'r, g,', iteration='antenna1') # only red restore() plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1331', spwid=[0,1], plotsymbol = 'r, g,') # only red, how did I get this to have r and g without overplotting? restore() plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1331', spwid=[0], plotsymbol = 'r,') plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1331', spwid=[1], plotsymbol = 'g,',overplot=True) # Time spent reading from disk : 56.85 sec. # Number of points being plotted : 1043656 # Python Plotting time : 2.49539208412 sec. # stupid thing [ msplot::setData()] failed! exit and restart casa --------------------------------------------------------------------- restore() plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1331', spwid=[0], plotsymbol = 'r,') plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1331', spwid=[1], plotsymbol = 'g,',overplot=True) # looks cleanrestore() plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1820', spwid=[0], plotsymbol = 'r,') plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1820', spwid=[1], plotsymbol = 'g,',overplot=True) # darn, 1331 is also being plotted. Apparently, you just add names to the field list if you don't restore. dach. restore() plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1820', spwid=[0], plotsymbol = 'r,') plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1820', spwid=[1], plotsymbol = 'g,',overplot=True) [ msplot::setData()] failed! exit and restart casa --------------------------------------------------------------------- dach - yet again. Each time the default is to read all data so this takes forever. I can't control c or control d out of it so I just have to wait. I'm tired of dealing with this flakey behavior. I promised I would evaluate plotxy capabilities and tell developers what I needed to see but I expected the routines to work when I made this promise. I quit - this is not fair. Plotxy - recommendations and issues (plus some others) DSS - 1feb07 ########################################################################## - importvla task should have a switch with default=don't fill autocorrelations, but allows the user to set the switch to fill them if they wan. - I really hate it that the defaults are not used when I don't specify a parameter in a script. This gets me in a lot of trouble when I forget to constantly go on line and check what global variables are set. This mode of running is OK if you are doing aips-like manual input from the command line (which I dislike), setting each parameter and then checking the inputs, but in a semi-manual script mode, it is horrid. - plotxy only displays antenna names but flagdata only flags based on antenna id and flagxy only allows selection of antenna id to select a specific antenna to flag. This makes it VERY confusing. plotxy specific recommendations and bugs: -------------------------------------------------------- - Performance of plotxy and flagxy is horrid. This is a real downer. Without a locate function especially, laborously going through the data and trying to isolate the bad stuff is so bad that we should never expect users to have to deal with this. - I want the locate feature back - big time! This is the single most useful function to ID bad data. - Time axis is muddled (writing overlaps) when window is first brough up. Should be cleaned up. - fieldid is not working to select data, I can only use minimum match to get all fields plotted. We may be between implementation or this may be a bug. - Each time plotxy is run, the number of points reported as being plotted increases (even though actual points plotted do not increase), finally the plotting time increases and the time spent reading from disk increases until the whole system slows down. Finally, setData fails and I have to exit casa to get the resources to reset. Looks like a memory allocation or buffering problem that finally tickles a setData problem. Very bad. I had to restart casa many, many times just to get through this test session. - plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], plotsymbol = 'r, g,') This produced blue and green pixels, not red and green. Color mapping may be off? - I need to be able to plot multiple types of data with different colors without having to overplot (especially during iteration where overplotting is not an option). You choose the color, I don't care. But if I specify spwid=[0,1], I want them to show up in different colors. If I specify RR & LL and RL & LR, I want them in different colors too. Please implement what msplot does with colors when I don't select the plotsymbol color specifically. - default during iteration='antenna1' should be to plot one subplot at a time, and then show all the antenna subplots in a grid at the end. - subplot=111 does not work during iteration. Subplotting should work it should allow the user to choose how many plots are shown during each iteration. - During iteration, if I stop the iteration, the screen goes blank. It should keep up the last plot so we can see that image. - During iteration, antennas displayed in order are: 4 23 11 8 6 21 22 5 12 15 17 10 19 25 28 3 20 2 7 9 1 27 The last plot should only show antenna 27 but it shows 3 - 2 are from the previous plot that it neglects to erase. - plotxy shows the autocorrelations and doesn't identify them as being any different from the correlated data. - plotxy shows only antenna name while flagdata allows selection based only on antennaid. Dach. - plotxy and flagxy field parameter is apparently case-sensitive. I would prefer that this not be case sensitive but if you are going to do this, hey, at least mention this in the online help for this parameter. This caused me no end of trouble until I figured it out. - data very close to zero is often plotted just below zero - it looks like there is a plot offsetting problem. - semi-repeatable SEVERE error # 1 (happened more than once): plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') ##### Thu Feb 1 22:21:22 2007 SEVERE : [ msplot::iterplotstart() ] Exception Reported: TPPlotter: From Python. : name 'nan' is not defined - non-repeatable SEVERE error # 2: plotxy(vis='src.ms', xaxis='time', yaxis='amp', datacolumn='data', field='1 h 2 w', spwid=[0,1], correlations='RR', plotsymbol = 'r, g,', iteration='antenna1') ##### [ msplot::setData()] Exception Reported: Error in select expression: expression uses different table *** Error *** This is exactly the same thing I've always been running, it just won't take it now. I had to exit and restart casa and then all worked as it should.