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
It has been requested that the % deadtimes per lumisection information (e.g. here) is also requested from OMS and stored in Run Registry.
This feature would probably include:
Another query to the /deadtimes OMS API endpoint.
Augmenting the data stored in the database of Run Registry.
From the requestor:
When data taking is in process Heavy Ion people need to perform various checks with the new fresh data. And for that I used to produce JSON (Non-certified) quickly. Using that JSON we can mostly throw the minimum bad lumis mainly identified by the OMS bits. DQM (run-registry) is also included in the JSON but mostly all lumis are marked GOOD, because by that time those runs and lumis are not certified.
As we know the high-deadtime lumi is certified by the L1 certification team. So, as we are producing our JSON so quickly without any certification done, the high deadtime lumi is also marked as the GOOD lumi in our JSON.
So right now what I am doing is, first I am identifying those high deadtime (>10%) lumis for each run, and then I am removing those Lumis from the existing quick JSON by hand. But it is time consuming to repeat the same process for each run by run.
So now what I was thinking is, we are already extracting some information from OMS, like
It has been requested that the % deadtimes per lumisection information (e.g. here) is also requested from OMS and stored in Run Registry.
This feature would probably include:
/deadtimes
OMS API endpoint.From the requestor:
The text was updated successfully, but these errors were encountered: