Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Store per-LS deadtime information #39

Open
nothingface0 opened this issue Nov 20, 2024 · 0 comments
Open

Store per-LS deadtime information #39

nothingface0 opened this issue Nov 20, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@nothingface0
Copy link
Contributor

nothingface0 commented Nov 20, 2024

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:

  1. Another query to the /deadtimes OMS API endpoint.
  2. 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

   {"==": [{"var": "lumisection.oms.cms_active"}, true]},
    {"==": [{"var": "lumisection.oms.bpix_ready"}, true]},
    {"==": [{"var": "lumisection.oms.fpix_ready"}, true]},
    {"==": [{"var": "lumisection.oms.tibtid_ready"}, true]},
    {"==": [{"var": "lumisection.oms.tecm_ready"}, true]},
    {"==": [{"var": "lumisection.oms.tecp_ready"}, true]},
    {"==": [{"var": "lumisection.oms.tob_ready"}, true]},
    {"==": [{"var": "lumisection.oms.ebm_ready"}, true]},
    {"==": [{"var": "lumisection.oms.ebp_ready"}, true]},
    {"==": [{"var": "lumisection.oms.eem_ready"}, true]},
    {"==": [{"var": "lumisection.oms.eep_ready"}, true]},
    {"==": [{"var": "lumisection.oms.esm_ready"}, true]},
    {"==": [{"var": "lumisection.oms.esp_ready"}, true]},
    {"==": [{"var": "lumisection.oms.hbhea_ready"}, true]},
    {"==": [{"var": "lumisection.oms.hbheb_ready"}, true]},
    {"==": [{"var": "lumisection.oms.hbhec_ready"}, true]},
    {"==": [{"var": "lumisection.oms.hf_ready"}, true]},
    {"==": [{"var": "lumisection.oms.ho_ready"}, true]},
    {"==": [{"var": "lumisection.oms.dtm_ready"}, true]},
    {"==": [{"var": "lumisection.oms.dtp_ready"}, true]},
    {"==": [{"var": "lumisection.oms.dt0_ready"}, true]},
    {"==": [{"var": "lumisection.oms.cscm_ready"}, true]},
    {"==": [{"var": "lumisection.oms.cscp_ready"}, true]},
    {"==": [{"var": "lumisection.oms.beam1_present"}, true]},
    {"==": [{"var": "lumisection.oms.beam2_present"}, true]},
    {"==": [{"var": "lumisection.oms.beam1_stable"}, true]},
    {"==": [{"var": "lumisection.oms.beam2_stable"}, true]}

we could add another condition for the high deadtime threshold <= 10 %.

@nothingface0 nothingface0 added the enhancement New feature or request label Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant