[Hps] Monitoring the experiment and storing information in the logbook
Stepan Stepanyan
stepanya at jlab.org
Wed Oct 6 22:46:29 EDT 2021
Dear all,
We appreciate your participation and your hard work during the shifts. Monitoring the ongoing run, acting accordingly on alarms or when things changed is very important for collecting high-quality data. Storing certain information in the logbook is critical for preserving the status of the experiment over time and is benefits everyone else who is following the experiment. However, it seems there is no uniform agreement on how and what information to be dump in the logbook. Often we have unnecessary entries of GUIs and strip charts that either does not change or have been stored otherwise in DBs (e.g in MYA). I added some more clarification to the ”Remote shifts” wiki on this.
I want to clarify here what we want to have in the logbook, and how often, as well as what does not need to be stored in the logbook.
0) No need to store MYA strip charts unless it is to indicate a problem
1) Monitoring plots, ECal, Hodo, SVT, Recon - must be stored at the beginning of the run and after 2-3 hours if run last that long
2) main scaler GUI, trigger GUI - ones per run
3) ECal and hodoscope scalers - ones per run
4) cameras: SVT chiller, and downstream viewer - no more than ones per shift
5) SVT summary GUI and SVT temperatures GUI - no more than ones per shift
Regards, Stepan
RC
More information about the Hps
mailing list