[daip] Source correction with CLCOR

[Eric Greisen]

Andrew Biggs wrote:
> Hi Eric. I've had a look at the source table and it seems to be okay:
> 
>      ROW   BANDWIDTH      RAEPO           DECEPO         EPOCH
> RAAPP           DECAPP
>   NUMBER   HZ             DEGREES         DEGREES        YEARS
> DEGREES         DEGREES
> 2   5.000000D+05    2.318386D+01   4.342574D+01   2.000000D+03
> 2.317896D+01   4.342230D+01
> 
> However, I just checked on the messages from FITLD and I see the following:
> 
> 
> localh> FITLD1: FRINI: 'BB_CHAN' COLUMN NOT FOUND
> localh> FITLD1: ATINI: 'POLCALA' COLUMN NOT FOUND
> localh> FITLD1: ATINI: 'POLCALB' COLUMN NOT FOUND
> localh> FITLD1: SOINI: 'RAOBS' COLUMN NOT FOUND
> localh> FITLD1: SOINI: 'DECOBS' COLUMN NOT FOUND
> 
> In the source table, the RAOBS and DECOBS columns have been set to the
> RAEPO and DECEPO values. Is this the problem?
> 
> 
>      ROW   RAOBS           DECOBS         LSRVEL         RESTFREQ
> PMRA           PMDEC
>   NUMBER   DEGREES         DEGREES        M/SEC          HZ
> DEG/DAY        DEG/DAY
> 2    2.318386D+01   4.342574D+01   0.000000D+00   0.000000D+00
> 0.000000D+00   0.000000D+00
> 
> 
> These are data out of the JIVE correlator, 2003.

the question is what the source table looked like before CLCOR got its 
hands on it.  CLCOR will correct the apparent RA and Dec but it seemed 
to have very large corrections to them and so very large corrections to 
phase.  My question of where the data came from is what task in AIPS 
read them in.  UVLOD and at least some places in FITLD try to correct 
the SU table by computing apparent coords.  The SOINI errors are about 
the new columns for pointing position and the code has a default 
solution to their absence. I guess the presence of those messages tells 
me that you came through the IDI path in FITLD.  Perhaps that does not 
do the source table correction.  Anyway, CLCOR should defend itself 
which should be easy to do.

Eric Greisen