[daip] 31DEC17 LINUX midnite job (dave, 20170329.034308)
aipsmgr at nrao.edu
aipsmgr at nrao.edu
Tue Mar 28 23:43:36 EDT 2017
dave update report for 31DEC17 on Wed Mar 29 03:43:35 UTC 2017 (UT)
Copies and compiles:
AIPSUPD - Using CVS for copying files.
UPDCVS - cvs copy of 31DEC17 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)
U 31DEC17/TIMESTAMP
P 31DEC17/APL/PGM/NOTST/FITLD.FOR
P 31DEC17/APL/PGM/NOTST/IMLOD.FOR
P 31DEC17/APL/PGM/NOTST/UVLOD.FOR
P 31DEC17/HIST/CHANGE.DOC
P 31DEC17/UPDATE/COMLNK.UPD
U 31DEC17/UPDATE/COMLNK.UPD.SUM
U 31DEC17/UPDATE/LASTCVS.DAT
P 31DEC17/UPDATE/PUTBCK.UPD
U 31DEC17/UPDATE/PUTBCK.UPD.SUM
P 31DEC17/UPDATE/REASONS.UPD
U 31DEC17/UPDATE/REASONS.UPD.SUM
P 31DEC17/UPDATE/WHATISOUT.UPD
U 31DEC17/UPDATE/WHATISOUT.UPD.SUM
UPDCVS - cvs update of 31DEC17 completed
UPDCVS - cvs update of TEXT completed
AIPSUPD - UPDCVS apparently worked
UPDCONTROL - /home/AIPS/31DEC17/LINUX/UPDATE/LASTREMOVE.DAT = 20170328.034215
UPDCONTROL - /home/AIPS/31DEC17/LINUX/UPDATE/LASTCOPY.DAT = 20170328.034215
UPDCONTROL - /home/AIPS/31DEC17/LINUX/UPDATE/LASTCOMRPL.DAT = 20170328.034215
UPDCONTROL - /home/AIPS/31DEC17/LINUX/UPDATE/LASTCOMLNK.DAT = 20170328.034215
UPDCONTROL - Everything seems in order
UPDCOMRPL: COMRPLs
UPDCOMRPL: currently in /home/AIPS/31DEC17/LINUX/UPDATE
UPDCOMLNK: COMLNKs
28-MAR-2017 21:26:16 20170328 TST APGNOT FITLD.FOR egreisen
28-MAR-2017 21:26:01 20170328 TST APGNOT IMLOD.FOR egreisen
28-MAR-2017 21:26:04 20170328 TST APGNOT UVLOD.FOR egreisen
UPDCOMLNK: currently in /home/AIPS/31DEC17/LINUX/UPDATE
UPDCOMLNK: /home/AIPS/31DEC17/APL/PGM/NOTST/FITLD.FOR
UPDCOMLNK: /home/AIPS/31DEC17/APL/PGM/NOTST/IMLOD.FOR
UPDCOMLNK: /home/AIPS/31DEC17/APL/PGM/NOTST/UVLOD.FOR
UPDCONTROL - Reasons for file updates on Wed Mar 29 03:43:17 UTC 2017 (UT)
28-MAR-2017 21:25:53 20170328 TST APGNOT IMLOD.FOR excessive response to bad number
28-MAR-2017 21:25:53 20170328 TST APGNOT UVLOD.FOR excessive response to bad number
28-MAR-2017 21:25:54 20170328 TST APGNOT FITLD.FOR excessive response to bad number
28-MAR-2017 21:27:29 20170328 TST HIST CHANGE.DOC fitld at al
CHANGE.DOC entries:
15003. March 28, 2017 FITLD IMLOD UVLOD Eric
The number parser caused these tasks to quit on bad numbers
when the keyword is not structurally significant. Changed
them to report bad numbers but set the value to 0 except when
reading number points on an axis, PCOUNT, GCOUNT, and other
required and structural keywords.
Moved nowhere.
15004. March
More information about the Daip
mailing list