You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 12, 2019. It is now read-only.
Currently, we get the run number from runinfo DB on starting, but we start publishing to runinfo DB after reaching configured, therefore any run that did not start will be published with a fresh SID and run number 0. These runs will sink to the bottom in the RunInfoServlet and do not appear to be recent runs.
Hannes suggested we get run number on initialize to solve this problem, which is what was being done by LV0.
The text was updated successfully, but these errors were encountered:
Interesting, I did not know this was possible. The design is based on the idea that for a run number to be meaningful, and for anyone to care about run info, a run must have been taken (or at least started). If it is desired to have runInfo published with a run number but there is no run with that run number, that is OK, but I wonder if it will disrupt any analysis workflows (e.g. will the DQM try to analyze these non-runs?)
Currently, we get the run number from runinfo DB on starting, but we start publishing to runinfo DB after reaching configured, therefore any run that did not start will be published with a fresh SID and run number 0. These runs will sink to the bottom in the RunInfoServlet and do not appear to be recent runs.
Hannes suggested we get run number on initialize to solve this problem, which is what was being done by LV0.
The text was updated successfully, but these errors were encountered: