[daip] 31DEC05 LINUX midnite job (dave, 20051109.044337)

[aipsmgr at aoc.nrao.edu]

dave update report for 31DEC05 on Wed Nov  9 04:44:06 UTC 2005 (UT)

Copies and compiles:

AIPSUPD - Using CVS for copying files.
UPDCVS - cvs update of 31DEC05 completed
UPDCVS - cvs update of TEXT completed
AIPSUPD - UPDCVS apparently worked

UPDCONTROL - /home/AIPS/31DEC05/LINUX/UPDATE/LASTREMOVE.DAT = 20051108.044233
UPDCONTROL - /home/AIPS/31DEC05/LINUX/UPDATE/LASTCOPY.DAT = 20051108.044233
UPDCONTROL - /home/AIPS/31DEC05/LINUX/UPDATE/LASTCOMRPL.DAT = 20051108.044233
UPDCONTROL - /home/AIPS/31DEC05/LINUX/UPDATE/LASTCOMLNK.DAT = 20051108.044233

UPDCONTROL - Everything seems in order

UPDCOMRPL: COMRPLs


UPDCOMRPL: currently in /home/AIPS/31DEC05/LINUX/UPDATE

UPDCOMLNK: COMLNKs

08-NOV-2005 20:51:15 20051108 TST APGNOT   CLCOR.FOR     lkogan

UPDCOMLNK: currently in /home/AIPS/31DEC05/LINUX/UPDATE
UPDCOMLNK: /home/AIPS/31DEC05/APL/PGM/NOTST/CLCOR.FOR


UPDCONTROL - Reasons for file updates on Wed Nov  9 04:43:51 UTC 2005 (UT)

08-NOV-2005 20:50:46 20051108 TST APGNOT   CLCOR.FOR     warning about load the INFILE (EOP) too early
08-NOV-2005 20:59:43 20051108 TST HIST     CHANGE.DOC    CLCOR:warning about too early INFILE load

CHANGE.DOC entries:

11965.  November 8, 2005        CLCOR                      Leonia
        If the INFILE (opcode 'EOP') is loaded long ahead of the
        observation, then the last date with real data in the file
        can be too close to the OBSDAT or even precede it. The
        using the INFILE may be wrong in such a case.
        So CLCOR is terminated now in such a case and the relevant
        warning is issued.
        Moved nowhere.

11966.  November