[daip] 31DEC12 LINUX midnite job (dave, 20130725.172646)

[aipsmgr at nrao.edu]

dave update report for 31DEC12 on Thu Jul 25 17:27:23 UTC 2013 (UT)

Copies and compiles:

AIPSUPD - Using CVS for copying files.
UPDCVS - cvs copy of 31DEC12 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)
? 31DEC12/ERRORS
? 31DEC12/SUL/SYSTEM/NRAOAOC
U 31DEC12/TIMESTAMP
P 31DEC12/APL/PGM/PRTAB.FOR
P 31DEC12/HIST/CHANGE.DOC
P 31DEC12/UPDATE/COMLNK.UPD
U 31DEC12/UPDATE/COMLNK.UPD.SUM
U 31DEC12/UPDATE/LASTCVS.DAT
P 31DEC12/UPDATE/PUTBCK.UPD
U 31DEC12/UPDATE/PUTBCK.UPD.SUM
P 31DEC12/UPDATE/REASONS.UPD
U 31DEC12/UPDATE/REASONS.UPD.SUM
UPDCVS - cvs update of 31DEC12 completed
UPDCVS - cvs update of TEXT completed
AIPSUPD - UPDCVS apparently worked

UPDCONTROL - /home/AIPS/31DEC12/LINUX/UPDATE/LASTREMOVE.DAT = 20130717.193959
UPDCONTROL - /home/AIPS/31DEC12/LINUX/UPDATE/LASTCOPY.DAT = 20130717.193959
UPDCONTROL - /home/AIPS/31DEC12/LINUX/UPDATE/LASTCOMRPL.DAT = 20130717.193959
UPDCONTROL - /home/AIPS/31DEC12/LINUX/UPDATE/LASTCOMLNK.DAT = 20130717.193959

UPDCONTROL - Everything seems in order

UPDCOMRPL: COMRPLs


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

UPDCOMLNK: COMLNKs

25-JUL-2013 17:23:51 20130725 NEW APLPGM   PRTAB.FOR     egreisen

UPDCOMLNK: currently in /home/AIPS/31DEC12/LINUX/UPDATE
UPDCOMLNK: /home/AIPS/31DEC12/APL/PGM/PRTAB.FOR


UPDCONTROL - Reasons for file updates on Thu Jul 25 17:27:17 UTC 2013 (UT)

25-JUL-2013 17:23:29 20130725 NEW HIST     CHANGE.DOC    prtab
25-JUL-2013 17:23:43 20130725 NEW APLPGM   PRTAB.FOR     move to new

CHANGE.DOC entries:


14189.  July 25, 2013             PRTAB                  Eric
        June 10: The row selection (RPARM adverb) for integer-valued
        columns set the selection value to an integer.  This prevents
        setting the selction value to say 2.5 and the accuracy value
        to 0.6 to look at rows with either 2 or 3 in the specific
        column.  Changed it to keep the user-specified value as
        floating-point.
        jULY 25: Changed the scaling routine to read up to 50000
        records.  It read only 5000 before and that could end up
        finding no valid values in some of these new tables.  Adjusted
        handling of the columns some including when no max.min found
        in the 50000 and placement of the 'INDE'.
        Moved to patch this date.