Diagnosis of DDM16 processing


Subject: Diagnosis of DDM16 processing
From: Erik Katsavounidis (Erik.Katsavounidis@lngs.infn.it)
Date: Sat May 13 2000 - 10:28:48 EDT


Summary of DDM16 processing.

Multiple entries (4) were allowed and use of cluster wide FAST queues
were used. This was practically a failure. Job was launched multiple
times and in various parts in order to complete.

Notice that VAX fast queues (WSGS06_FAST/WSGS07_FAST) are NOT always
enough in terms of cpu limit in order to handle the DRIVER jobs.

198 files processed: #1 was RUN007505 , #198 was RUN080931

Subj: MYSTATS LOG ERRORS RUN7539 DDM16 SIZE= 1-NO
Fatal error occured during PHRASE decoding. It did not process full
file. Disabled PHRASE processing (using MY_MONITOR_1RUN_NO49)
and file was fully processed.

Subj: MYSTATS LOG ERRORS RUN7579 DDM16 SIZE= 1-NO
Error occured in a non-PHRASE event, most likely due to high optimization
flags. NOT WORTH DEBUGGING.

Subj: MYSTATS LOG ERRORS RUN7666 DDM16 SIZE= 1-NO
Error occured in a PHRASE event.

Subj: MYSTATS LOG ERRORS RUN7698 DDM16 SIZE= 1-NO
Error occured in a PHRASE event.

Subj: CALIB: DDM16 RUN007596 CAL0 (HIST)/1 (STAT)
Subj: CALIB: DDM16 RUN007598 CAL0 (HIST)/1 (STAT)
Subj: CALIB: DDM16 RUN007600 CAL0 (HIST)/1 (STAT)
Subj: CALIB: DDM16 RUN007644 CAL0 (HIST)/1 (STAT)

The above four runs are calibration ones (of QUESTIONABLE quality),
originally missing from the DISK$MACRO2:[MACROCAL.DOCS]CAL_RUN_LIST.TXT file.
File is now updated.



This archive was generated by hypermail 2a24 : Sat May 13 2000 - 10:28:53 EDT