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

[aipsmgr at nrao.edu]

dave update report for 31DEC10 on Tue Jul  6 03:44:38 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/ERRORS
? 31DEC10/APL/DEV/UNIX/ZCREA2.C.save
? 31DEC10/LNX64/SYSTEM/RSYNC.MASTER
U 31DEC10/TIMESTAMP
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
P 31DEC10/Y/PGM/NOTST/UVHGM.FOR
UPDCVS - cvs update of 31DEC10 completed
UPDCVS - cvs update of TEXT completed
AIPSUPD - UPDCVS apparently worked

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

UPDCONTROL - Everything seems in order

UPDCOMRPL: COMRPLs


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

UPDCOMLNK: COMLNKs

05-JUL-2010 19:34:56 20100705 TST YPGNOT   UVHGM.FOR     egreisen

UPDCOMLNK: currently in /home/AIPS/31DEC10/LINUX/UPDATE
UPDCOMLNK: /home/AIPS/31DEC10/Y/PGM/NOTST/UVHGM.FOR


UPDCONTROL - Reasons for file updates on Tue Jul  6 03:44:34 UTC 2010 (UT)

05-JUL-2010 19:34:45 20100705 TST YPGNOT   UVHGM.FOR     rms ??
05-JUL-2010 21:54:33 20100705 TST YPGNOT   UVHGM.FOR     addressing error
05-JUL-2010 22:36:35 20100705 TST HIST     CHANGE.DOC    uvhgm

CHANGE.DOC entries:

13201.  July 5, 2010            UVHGM                   Eric
        For some reason, the fancy fitting routines sometimes think
        that the arrays are orthogonal.  Added a simplistic mean and
        rms fit to use in such cases.
        Found the reason for the failure on Intel 64-bit compilations:
        an array was improperly declared (3,3) when it should have
        been (14,3) given the other probably excessive parameters in
        the task.
        Moved nowhere.

13202.  July