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

CMS - HI 2013 json files for validated data #145

Closed
katilp opened this issue Sep 12, 2022 · 3 comments
Closed

CMS - HI 2013 json files for validated data #145

katilp opened this issue Sep 12, 2022 · 3 comments

Comments

@katilp
Copy link
Member

katilp commented Sep 12, 2022

from #129

(NB OD release guide: WIP in https://cms-opendata-releaseguide.docs.cern.ch/validated_runs/)

2013 pPb 5.02 TeV data

(datasets see #136)

v2 of the following?

2013 pp 2.76 TeV ref

(datasets see #140)

2015 pp 5.02 TeV ref

(datasets see #139)

two of the files in https://cms-service-dqmdc.web.cern.ch/CAF/certification/Collisions15/5TeV/
assume the ones with the widest range based on the run range in the file name (tbc if that's the correct choice):

@katilp
Copy link
Member Author

katilp commented Apr 24, 2023

@katilp
Copy link
Member Author

katilp commented May 9, 2023

With a risk of overdoing (but maybe useful for later), modifications needed w.r.t cms-YYYY-validated-runs/code/vali_records.py:

Usage assumptions:

  • for normal pp data-taking, the run eras are taken based on the value "released" (yes/no)
  • for pp HI ref or HI data taking, the run era is given in the run variables

@katilp
Copy link
Member Author

katilp commented Jun 6, 2023

From the discussion on June 6, 2023: check the json file selection:

  • always take the files with the widest range
  • take the highest version (typically v2)

Confirming:

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

No branches or pull requests

1 participant