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: add pileup info to the lumi records #3689

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

jmhogan
Copy link
Contributor

@jmhogan jmhogan commented Oct 11, 2024

While adding instructions about pileup reweighting to the CMS open data guide I realized we don't have the necessary input information on the lumi records. This PR adds one extra lumi JSON file to the 2011, 2012, and 2015 records. No changes to the existing files! We can discuss whether it would be better to make a new record, but this feels simpler.

The necessary files are: /eos/opendata/cms/...

  • upload/julie/pileup_2011_JSON_pixelLumi.txt --> luminosity/2011/pileup_2011_JSON_pixelLumi.txt
  • upload/julie/pileup_2012_JSON_pixelLumi.txt --> luminosity/2012/pileup_2012_JSON_pixelLumi.txt
  • upload/julie/pileup_2015_JSON.txt --> luminosity/2015/pileup_2015_JSON.txt

I left dummies for the checksum & file size. I incremented the number of files, but didn't change the overall file size for the record. Each record gets a new sentence in the description: "Condensed information about the instantaneous luminosity by lumi section needed to determine the uncertainty in the pileup prediction is provided in the file."

Corresponding pointer in our pileup guide to the Open Data Guide page where the pileup reweighting will be discussed. The content for that page is here, but I haven't pushed that on yet since the links to the portal are likely to fail right now. It can follow this very quickly so there's no significant time with a link to an "under construction" page.

@tpmccauley
Copy link
Member

Looks good to me. The only suggestion I would make is to perhaps squash your commits into one.

Copy link
Member

@tpmccauley tpmccauley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Perhaps squash commits into one?

@jmhogan
Copy link
Contributor Author

jmhogan commented Nov 20, 2024

@tpmccauley I think the squashing can be done in the merge...
@tiborsimko from our side this is ready to go in -- we'll be pointing to these new files in some Open Data Guide updates that are ready to follow this update.

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

Successfully merging this pull request may close these issues.

2 participants