[daip] ACCOR needs to pay attention to flags.

Craig Walker cwalker at nrao.edu
Fri Sep 5 17:36:52 EDT 2014


ACCOR does not have an input to specify the flag table so I presume that 
it does not pay attention to flags.  Behavior with the data I am 
currently processing confirms that.  In this day of sometimes delayed 
level settings, it is not unlikely to get some bad points at the start 
of a scan.  In my case, those data are flagged.  But ACCOR sees them and 
gets a bad first solution.  That then affects additional data depending 
on the solint and smoothing used.  Using the standard inputs in 
VLBACALA, I have about 12 seconds of bad data corrupting the first 
minute of data, so about 50 seconds of what should be good data will
have to be flagged, or I will need to jump through hoops editing the SN 
table and rerunning CLCAL.

I suggest ACCOR be taught to pay attention to flags.

Datafile TA035C5_VLBI.MULTI.1 on /home/noatak2/AIPS/DA01

Cheers,

Craig

-- 
---------------------------------------------------------------------
     R. Craig Walker            Array Operations Center
     cwalker at nrao.edu           National Radio Astronomy Observatory
     Phone  575 835 7247        P. O. Box O
     Fax    575 835 7027        Socorro NM 87801   USA
---------------------------------------------------------------------



More information about the Daip mailing list