[daip] 31DEC17 LINUX midnite job (dave, 20170224.154601)

[aipsmgr at nrao.edu]

dave update report for 31DEC17 on Fri Feb 24 15:46:17 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/DBCON.FOR
P 31DEC17/HELP/DBCON.HLP
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
UPDCVS - cvs update of 31DEC17 completed
UPDCVS - cvs update of TEXT completed
AIPSUPD - UPDCVS apparently worked

UPDCONTROL - /home/AIPS/31DEC17/LINUX/UPDATE/LASTREMOVE.DAT = 20170224.044215
UPDCONTROL - /home/AIPS/31DEC17/LINUX/UPDATE/LASTCOPY.DAT = 20170224.044215
UPDCONTROL - /home/AIPS/31DEC17/LINUX/UPDATE/LASTCOMRPL.DAT = 20170224.044215
UPDCONTROL - /home/AIPS/31DEC17/LINUX/UPDATE/LASTCOMLNK.DAT = 20170224.044215

UPDCONTROL - Everything seems in order

UPDCOMRPL: COMRPLs


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

UPDCOMLNK: COMLNKs

24-FEB-2017 15:40:06 20170224 TST APGNOT   DBCON.FOR     egreisen

UPDCOMLNK: currently in /home/AIPS/31DEC17/LINUX/UPDATE
UPDCOMLNK: /home/AIPS/31DEC17/APL/PGM/NOTST/DBCON.FOR


UPDCONTROL - Reasons for file updates on Fri Feb 24 15:46:13 UTC 2017 (UT)

24-FEB-2017 15:39:06 20170224 TST HIST     CHANGE.DOC    dbcon
24-FEB-2017 15:39:54 20170224 TST APGNOT   DBCON.FOR     frequency scaling VERY WRONG
24-FEB-2017 15:39:55 20170224 TST HLPFIL   DBCON.HLP     warnings about frequencies

CHANGE.DOC entries:

14983.  February 24, 2017           DBCON              Eric
        A BAD ERROR was made May 28, 2014 in DBCON.  If the 2 data
        sets differed in frequency (after shifting of the reference
        pixel), the U-V-W of the second data set was scaled by the
        ratio of the frequencies.  This is not correct - the u-v-w
        with no scaling are in wavelengths at the observation and
        should not be changed.  (A shift of reference pixel does
        require a modest re-scaling based only on the frequencies in
        the particular data set.)  I have restored the correct code in
        DBCON and added a loud warning message to the Fortran and the
        help file.  The output of mixed frequencies should NEVER EVER
        be processed by a task that needs to change U-V-W since it
        cannoy fully know the frequencies to use.  The most obvious of
        these is UVFIX.
        Moved to 31DEC16 this date.

14984.  February