[daip] 31DEC10 LINUX midnite job (dave, 20100129.044440)

aipsmgr at nrao.edu aipsmgr at nrao.edu
Thu Jan 28 23:45:10 EST 2010


dave update report for 31DEC10 on Fri Jan 29 04:45:10 UTC 2010 (UT)

Copies and compiles:

AIPSUPD - Using CVS for copying files.
UPDCVS - cvs copy of 31DEC10 begun, 1st character means
 - U added, P updated, M your file differs from master
 - C you have a changed file needing work (error!)
 - ? you have a file not on the master (ignore)
? 31DEC10/LNX64/SYSTEM/RSYNC.MASTER
U 31DEC10/TIMESTAMP
P 31DEC10/APL/PGM/NOTST/CLCOR.FOR
P 31DEC10/HIST/CHANGE.DOC
P 31DEC10/UPDATE/COMLNK.UPD
U 31DEC10/UPDATE/COMLNK.UPD.SUM
U 31DEC10/UPDATE/LASTCVS.DAT
P 31DEC10/UPDATE/PUTBCK.UPD
U 31DEC10/UPDATE/PUTBCK.UPD.SUM
P 31DEC10/UPDATE/REASONS.UPD
U 31DEC10/UPDATE/REASONS.UPD.SUM
UPDCVS - cvs update of 31DEC10 completed
UPDCVS - cvs update of TEXT completed
AIPSUPD - UPDCVS apparently worked

UPDCONTROL - /home/AIPS/31DEC10/LINUX/UPDATE/LASTREMOVE.DAT = 20100128.044333
UPDCONTROL - /home/AIPS/31DEC10/LINUX/UPDATE/LASTCOPY.DAT = 20100128.044333
UPDCONTROL - /home/AIPS/31DEC10/LINUX/UPDATE/LASTCOMRPL.DAT = 20100128.044333
UPDCONTROL - /home/AIPS/31DEC10/LINUX/UPDATE/LASTCOMLNK.DAT = 20100128.044333

UPDCONTROL - Everything seems in order

UPDCOMRPL: COMRPLs


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

UPDCOMLNK: COMLNKs

29-JAN-2010 00:20:42 20100129 TST APGNOT   CLCOR.FOR     egreisen

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


UPDCONTROL - Reasons for file updates on Fri Jan 29 04:44:55 UTC 2010 (UT)

29-JAN-2010 00:20:20 20100129 TST APGNOT   CLCOR.FOR     messes up when 1 polarization
29-JAN-2010 00:36:56 20100129 TST HIST     CHANGE.DOC    clcor

CHANGE.DOC entries:

13079.  January 28, 2009           CLCOR                 Eric
        A variety of places did not check to see if all pointers to
        the CL record were valid.  It was then possible to write in
        RECORD(0) which damaged the SIN of the declination carried
        around in COMMON.  The symptom was an error in shifting phases
        for position shifts that were large enough - or scans that
        lasted long enough perhaps - when there is only one
        polarization.  When there are two polarizations all pointers
        are valid.  The error appeared in the code in March 2006.
        Moved nowhere - lets wait and then move to patch.
13080.  January




More information about the Daip mailing list