[daip] 31DEC10 LINUX midnite job (dave, 20101117.044451)
aipsmgr at nrao.edu
aipsmgr at nrao.edu
Tue Nov 16 23:45:14 EST 2010
dave update report for 31DEC10 on Wed Nov 17 04:45:14 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/APL/PGM/NOTST/TYAPL.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
P 31DEC10/UPDATE/WHATISOUT.UPD
U 31DEC10/UPDATE/WHATISOUT.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 = 20101116.044319
UPDCONTROL - /home/AIPS/31DEC10/LINUX/UPDATE/LASTCOPY.DAT = 20101116.044319
UPDCONTROL - /home/AIPS/31DEC10/LINUX/UPDATE/LASTCOMRPL.DAT = 20101116.044319
UPDCONTROL - /home/AIPS/31DEC10/LINUX/UPDATE/LASTCOMLNK.DAT = 20101116.044319
UPDCONTROL - Everything seems in order
UPDCOMRPL: COMRPLs
UPDCOMRPL: currently in /home/AIPS/31DEC10/LINUX/UPDATE
UPDCOMLNK: COMLNKs
16-NOV-2010 23:06:53 20101116 TST APGNOT TYAPL.FOR amiodusz
UPDCOMLNK: currently in /home/AIPS/31DEC10/LINUX/UPDATE
UPDCOMLNK: /home/AIPS/31DEC10/APL/PGM/NOTST/TYAPL.FOR
UPDCONTROL - Reasons for file updates on Wed Nov 17 04:45:10 UTC 2010 (UT)
16-NOV-2010 23:06:41 20101116 TST APGNOT TYAPL.FOR flagging valid data
16-NOV-2010 23:11:17 20101116 TST HIST CHANGE.DOC TYAPL
CHANGE.DOC entries:
13327. November 11, 2010 TYAPL Amy
For the situation where there was data on a new source with a
time stamp before the first entries in the SY table the
subroutine GETSY in TYAPL would read the entire SY table looking
for bounding times, not finding any. Then since the table had
been read it would not be able to find bounding times for any
time thereafter and all the weights would be set negative,
effectively flagging the data. I fixed GETSY in an inelegant
way, and this change should probably be propigated to the
subroutine that reads TY tables.
Moved nowhere.
13328. November
More information about the Daip
mailing list