Closed kunathj closed 2 years ago
Also: Apparently files do not necessarily obey the .dat_XXXX
convention: The first file in that run was not .dat_XXXX
, but .dat
instead. And from file 10000 onwards a fifth digit is needed.
The requested feature was introduced in 6258cdbf58efe643e93879897f045975385f7607.
.dat_0000
will not be changed to .dat
for technical reasons in the DAQ. The monitoring special-cases this first file, and will keep this logic. The same holds true for raw.bin
.
Triggered by trying to run the monitoring on the partially uploaded cosmic muons commissioning run. The monitoring script should have a
--allow_dirty
flag (naming tbc). With that flag,In both cases, almost empty refers to a state were only (part of) the header was written, but no data. This currently lets the monitoring script error out.