I encountered a problem where the previous run likely crashed after the "run_records" folder was created, but the run had not yet been written to the database. Since we are getting the run numbers from a database, the next run has the same run number, but a run_records folder already exists. This essentially locks the system without manual intervention.
I think we might want to disable the check in:
Or keep the test, but if a folder is already there, rename the old folder or alike?
I encountered a problem where the previous run likely crashed after the "run_records" folder was created, but the run had not yet been written to the database. Since we are getting the run numbers from a database, the next run has the same run number, but a run_records folder already exists. This essentially locks the system without manual intervention.
I think we might want to disable the check in:
artdaq-daqinterface/rc/control/daqinterface.py
Line 3736 in 82b9ff7
Or keep the test, but if a folder is already there, rename the old folder or alike?