Skip to content
Snippets Groups Projects
Commit a800a033 authored by Carmelo Pellegrino's avatar Carmelo Pellegrino
Browse files

launch the DAQ before the DM (and, hence, the detector). This resolves issue #3.

parent 78713682
No related branches found
No related tags found
No related merge requests found
......@@ -169,16 +169,16 @@ cat ${rs_file} | sed -e "s/RUNNUMBER/${run_number}/" >${DM_DATA_DIR}/dm.detector
run_start_time=`nowUTC`
# Launch the DM
dm_driver ${run_duration_seconds} | mono ${DM_EXE_DIR}/DetectorControl.exe --control --reset &
PROCS=(${PROCS[*]} $!)
# Launch the DAQ
log "Launching the DAQ with the following command line: daq.sh ${run_number} ${run_start_time} ${run_duration_seconds} ${DAQ_SERVER} ${DAQ_USER} "
daq_driver_log_file=~/.km3_private/daq_driver_${run_number}.log
daq.sh ${run_number} ${run_start_time} ${run_duration_seconds} ${DAQ_SERVER} ${DAQ_USER} >${daq_driver_log_file} &
PROCS=(${PROCS[*]} $!)
# Launch the DM
dm_driver ${run_duration_seconds} | mono ${DM_EXE_DIR}/DetectorControl.exe --control --reset &
PROCS=(${PROCS[*]} $!)
# Put notification mark in the system tray
zenity --notification --text="Run ${run_number} is on going." &
PROCS=(${PROCS[*]} $!)
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment