Skip to content
This repository has been archived by the owner on Mar 12, 2019. It is now read-only.

Get RunNumber on initialize #371

Open
kakwok opened this issue Mar 13, 2018 · 2 comments
Open

Get RunNumber on initialize #371

kakwok opened this issue Mar 13, 2018 · 2 comments

Comments

@kakwok
Copy link
Collaborator

kakwok commented Mar 13, 2018

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.

@kakwok kakwok added the (low) label Mar 13, 2018
@jhakala
Copy link
Member

jhakala commented Mar 13, 2018

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?)

@kakwok
Copy link
Collaborator Author

kakwok commented Mar 13, 2018

If it is desired to have runInfo published with a run number but there is no run with that run number, that is OK

Hannes thinks this is a valid use case.
There'll be no files written to disk, so no files for DQM to be processed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants