[daip] Fluxcal missing in the data

Eric Greisen egreisen at nrao.edu
Wed Oct 29 13:12:27 EDT 2014


On 10/29/2014 11:02 AM, Kamble, Atish wrote:
> Dear Eric,
>
>     I asked about the first of these data sets.  The one you sent me is
>     very very complex and lengthy.  I see nothing in the BDFLIST about a
>     calcode 'N'.  Instead I see numerous different "config"s - BDF2AIPS
>     loads only one of these at a time to separate output data sets.
>     Perhaps that is the origin of the listed source with no records.
>
>
> I load one config at a time and the issue that I am trying to resolve
> appears with any given configuration. I just chose to inform one test
> case. The way I load a chosen config is as follows:
>
> $
> default BDF2AIPS
> asdmfile 'MD:filename'
> outname 'filenameX'
> config X
> BDF2AIPS
> $
>
> replace X by code for the given configuration.
>
>     The thought with the 3C147 missing is that there was perhaps no time
>     to make the drive over the top to the cal source - people who
>     understand such things will look at them.  I sort of expect there to
>     be data even in that case - along with a flag saying "not on source"
>     - since the correlator correlates all the time.
>
>
> This one comes from Program 11B-197 on 17 Feb 2012. I don't know where
> the BDF2AIPS picks up ID as 'N' cause BDFLIST shows ID as 'P' or
> sometimes 'D'.
>
> There is no such a flag anywhere as you mention. But as you correctly
> say there must be some data. And I can say even further that the
> antennas were ON source since we have previously analysed many of these
> observations.
>
> Thanks,
> - Atish .
>
>
>

P stands for pointing and is omitted unless you ask for it to be 
included (it is not normal valid visibilities).  I will take a look at 
the 17 Feb data.

ERic Greisen



More information about the Daip mailing list