[daip] 31DEC05 LINUX midnite job (dave, 20051014.034346)

[aipsmgr at aoc.nrao.edu]

dave update report for 31DEC05 on Fri Oct 14 03:44:30 UTC 2005 (UT)

Copies and compiles:

AIPSUPD - Using CVS for copying files.
UPDCVS - cvs update of 31DEC05 completed
UPDCVS - cvs update of TEXT completed
AIPSUPD - UPDCVS apparently worked

UPDCONTROL - /home/AIPS/31DEC05/LINUX/UPDATE/LASTREMOVE.DAT = 20051013.034234
UPDCONTROL - /home/AIPS/31DEC05/LINUX/UPDATE/LASTCOPY.DAT = 20051013.034234
UPDCONTROL - /home/AIPS/31DEC05/LINUX/UPDATE/LASTCOMRPL.DAT = 20051013.034234
UPDCONTROL - /home/AIPS/31DEC05/LINUX/UPDATE/LASTCOMLNK.DAT = 20051013.034234

UPDCONTROL - Everything seems in order

UPDCOMRPL: COMRPLs


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

UPDCOMLNK: COMLNKs

13-OCT-2005 20:49:03 20051013 TST QPGNOT   FRING.FOR     amiodusz

UPDCOMLNK: currently in /home/AIPS/31DEC05/LINUX/UPDATE
UPDCOMLNK: /home/AIPS/31DEC05/Q/PGM/NOTST/FRING.FOR


UPDCONTROL - Reasons for file updates on Fri Oct 14 03:44:00 UTC 2005 (UT)

13-OCT-2005 10:58:27 20051013 TST SYSUNIX  XASERVERS     quotes
13-OCT-2005 10:58:29 20051013 TST SYSUNIX  UNIXSERVERS   quotes
13-OCT-2005 20:48:40 20051013 TST QPGNOT   FRING.FOR     FREQS calaculated badly with optimization
13-OCT-2005 20:56:27 20051013 TST HIST     CHANGE.DOC    FRING

CHANGE.DOC entries:

11939.  October 13, 2005            FRING                    Amy
        When the Intel compiler optimized the loop that calculated the
        frequencies (FREQS) the accuracy was degraded enough (errors
        on the order of a few hundred kHz), that it triggered a
        "FREQUENCIES NOT ON A UNIFORM GRID" warning.  Changed the
        FREQS array to double precision, which seems to force the Intel
        compiler not to optimize the do loop in question, and the
        calculated FREQS now have a high degree of accuracy.
        Moved nowhere.

11940.  October