added cut to skimmer based on XHY->bbWW semi-resolved channel veto #39
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…/HHbbVV into Wqq_semi_resolved_veto
…/HHbbVV into Wqq_semi_resolved_veto Adding slight fix
for more information, see https://pre-commit.ci
|
Looking good, I had to update the discriminant to match the one used in the semi-resolved analysis. @andresnava1000 Could you check the efficiency of a selection on |
|
Variables are looking OK, will need to iterate on the exact veto with Amitav. See https://indico.cern.ch/event/1375175. For now, saving the SD and regressed masses of the two W-tagged jets. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The cut should remove any events that have 2 or more non-Hbb fatjets with Wqq scores above 0.8
Logic for cut:
Compute number of fatjets per event with Wqq score > 0.8. Define cut as true for event if there are less than 3 such fatjets, and in the case that there are exactly two, define cut as true iff Hbb is one of them
To study this would I want to run over a large number of signal files (C2V = 0)? it seems like this cut is pretty rare from the several files that I tested. For background, would I use TTToSemiLeptonic as well?