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

Jet Veto Map #36

Merged
merged 1 commit into from
Mar 26, 2024
Merged

Jet Veto Map #36

merged 1 commit into from
Mar 26, 2024

Conversation

carriganm95
Copy link
Contributor

Adds "loose jet selection" to EventJetProducer and cut jetVetoMap2022 to veto any events with a jet passing loose selection and passing through the jet veto map from the JERC group.

Also updates the JetTightID definition for 2022

Added script StandardAnalysis/test/makeRatioPlots.py to compare different cut selections

…s passing loose selection, also adding script to make ratio plots between cuts
@@ -125,6 +135,9 @@ EventJetVarProducer::AddVariables (const edm::Event &event, const edm::EventSetu
edm::Handle<edm::TriggerResults> triggerBits;
event.getByToken(tokenTriggerBits_, triggerBits);

TFile* f_jetVeto = TFile::Open("/data/users/mcarrigan/condor/run3Inputs/Summer22EE_23Sep2023_RunEFG_v1.root", "read");
Copy link
Contributor

Choose a reason for hiding this comment

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

Will this file live in your condor directory from now on or should be include this file in the repository?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I just don't want it to be a part of every .tar.gz file that we make when running so I planned to save it in /data and have everyone pull from there. Similar to what was done in the past for some files

Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe it can be put inside StandardAnalysis/data?

Copy link
Contributor

Choose a reason for hiding this comment

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

I just don't want it to be a part of every .tar.gz file that we make when running so I planned to save it in /data and have everyone pull from there. Similar to what was done in the past for some files

This is true. Maybe there could be a common folder in /data for those files (with some rules of how to use it, to not become a place where everything can be stored)

@carriganm95 carriganm95 merged commit e883aa3 into master Mar 26, 2024
@carriganm95 carriganm95 deleted the jetVetomap branch March 26, 2024 18:15
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.

3 participants