Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
DeepDoubleCvL and DeepDoubleCvB tagger integration #24918
DeepDoubleCvL and DeepDoubleCvB tagger integration #24918
Changes from 39 commits
217ee7c
40f8607
9a49df9
f22430b
4c34f16
912c23d
dd24af3
c821036
9017647
147839a
a90008a
0188aba
eb3e3ea
7c16f68
9163e90
d656aa9
0ed5f6f
afc1a59
3c81d7b
79471b3
27bdb12
81b0d65
f6ac641
d3b1b86
e42d295
d17215a
5d8e94f
2e9926b
183aa17
3d8733b
f338373
f804c4e
aef474e
aa32440
92bb0d6
5703a71
5f8c3a4
b456bf9
230e8d3
f3eb756
f74c4c1
40f5b44
2c45ee3
1658fcb
bbadee2
fc232c4
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
which pt are we using at this point?
I printed out a few cases before the last changes and I see the discriminator value going to 0 for jets with pt above 150 GeV (the values below are slimmedJetsAK8 jet pt() [corrected value]).
My guess is that the pt at this point is not corrected. Is this choice OK for your physics needs?
e.g. in wf 136.8311
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct, IIUC this is the uncorrected pt. The 150 cut is OK, because I think we're only saving jets with pT > 170 and for our analysis we need higher pT jets. The concern is for other analyses but I think at the 150 anything 200 is safe.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The cut is not at 170 but 100 GeV. But because of the loose cut, the jet pT can also go below 100 GeV (https://github.com/cms-sw/cmssw/blob/CMSSW_9_4_10/PhysicsTools/PatAlgos/python/slimming/applySubstructure_cff.py#L186-L188). This is for the default Puppi fat jets. The cut at 170 GeV (https://github.com/cms-sw/cmssw/blob/CMSSW_9_4_10/PhysicsTools/PatAlgos/python/slimming/applySubstructure_cff.py#L186-L188) is for CHS fat jets which are later matched to Puppi jets in order to pick up their kinematic properties and other variables (https://github.com/cms-sw/cmssw/blob/CMSSW_9_4_10/PhysicsTools/PatAlgos/python/slimming/applySubstructure_cff.py#L221-L243).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need a lower cut then? @ferencek
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think 150 GeV on uncorrected pT should be fine because, as you said, meaningful analysis level cuts will be quite higher than that. I was just pointing out that the cut on ak8 puppi jets stored in MiniAOD is not a flat 170 GeV cut but is actually lower and a bit more complex because of the extra
cutLoose
andnLoose
requirements. What will be done with jets that do not pass the cut? Some dummy discriminator value (preferably negative) will be stored?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only limited information is stored for lower-pT AK8 jets in miniAOD. @rappoccio can clarify further
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The default value when the output is initialized is 0, we could make it -1 I guess?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kpedro88 I guess you are referring to the 170 GeV on CHS fat jets. Yes, only some of the Puppi fat jets (generally those with high pT) will have a matched CHS fat jets from which kinematic and other variables are picked up and added to the Puppi jet as userFloats.
However, here I am discussing something different since btag discriminators are added in a completely different way from userFloats so the above-mentioned cut on CHS jets plays no role. Here we are not so much after reducing the event size (although, presumably a lot of identical dummy discriminator values stored in the event can lead to better event compression) but reducing the processing time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@andrzejnovak I think a negative value would be better than some other normally allowed value. That way it will be easier to discriminate skipped jets based on their discriminator value.