Closed kunathj closed 2 years ago
~- [ ] Ensure having a single monitoring loop only~
Must be in top comment, otherwise it cannot be converted into an issue automatically.
Even with the (new) raw.bin
data writing format, the monitoring loop (conversion, event building, snapshots/data quality plots) is faster than the TB data influx on decent hardware (e.g. the PC used for monitoring during the DESY TB). The monitor_newest.py
wrapper introduced with commit b7d467d76b178217a09dd38089d4b34e201d6526 can be used in the way that night mode was intended to work (picking up new runs that are started automatically).
Idea: A night mode for unattended monitoring. In night mode, the monitoring should switch other to a new run (sister directory of the raw data file). In day mode (current implementation), the monitoring will continue to build the events of the run that it was started on. When all those raw data files are treated, the monitoring terminates.