Runlog: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
The number of programs located in ''$CLON/src/runlog'' are running at various stages of the Data Aquisition process. | The number of programs located in ''$CLON/src/runlog'' are running at various stages of the Data Aquisition process. | ||
'''run_log_begin''' executed in the end of ''Prestart'' transition (see ''run_prestart_end.csh'' rcscript) | '''run_log_begin''' executed in the end of ''Prestart'' transition (see ''run_prestart_end.csh'' rcscript); it produces file $CLON_PARMS/run_log/archive/begin_<session>_<runnum>.txt, send data to ipc and dbrouter. | ||
'''run_log_comment''' executed in Event Recorder script of ''Prestart'' transition (see ''run_prestart_er.csh'' rcscript) | '''run_log_comment''' executed in Event Recorder script of ''Prestart'' transition (see ''run_prestart_er.csh'' rcscript) | ||
| Line 14: | Line 14: | ||
'''run_log_end_update''' can be run after run is finished to recover database information in case of end run failure. It assumes that ascii files were restored by running ''run_log_recovery''; Sergey B. developed that program being unaware of cron job, whole scheme must be reconsidered ... | '''run_log_end_update''' can be run after run is finished to recover database information in case of end run failure. It assumes that ascii files were restored by running ''run_log_recovery''; Sergey B. developed that program being unaware of cron job, whole scheme must be reconsidered ... | ||
Revision as of 08:49, 3 June 2009
The number of programs located in $CLON/src/runlog are running at various stages of the Data Aquisition process.
run_log_begin executed in the end of Prestart transition (see run_prestart_end.csh rcscript); it produces file $CLON_PARMS/run_log/archive/begin_<session>_<runnum>.txt, send data to ipc and dbrouter.
run_log_comment executed in Event Recorder script of Prestart transition (see run_prestart_er.csh rcscript)
run_log_files executed in the end of End transition (see run_end_end.csh rcscript); it reads files $CLON_PARMS/run_files/runfile_<session>_<runnumber>.txt written by Event Recorder, and updates database; if update was successful it tags these files; after file
run_log_end executed in the end of End transition (see run_end_end.csh rcscript), immediately after run_log_files
run_log_summary extract from database and print run summary for specified run(s)
run_log_recovery reprocess raw datafiles from raid disk(s) or /work/recovery directory and restores ascii files lost in case of end run failure.
run_log_end_update can be run after run is finished to recover database information in case of end run failure. It assumes that ascii files were restored by running run_log_recovery; Sergey B. developed that program being unaware of cron job, whole scheme must be reconsidered ...
CRON job is running every hour on clon10 to restore database in case if end of run failed. It starts script run_cleanup, which it turn runs following commands:
cd $CLON_PARMS/run_files run_log_files -a clasprod -s clasprod *.txt run_log_end -a clasprod -s clasprod *.txt run_file_clean *.txt
as result database got updated, new xml tags inserted into run_files, and after that run_files moved into archive subdirectory.