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

Implementation of kVetoHybridNoFit btagging option #11

Closed
TomasDado opened this issue Apr 20, 2018 · 1 comment
Closed

Implementation of kVetoHybridNoFit btagging option #11

TomasDado opened this issue Apr 20, 2018 · 1 comment
Labels
enhancement New feature or request

Comments

@TomasDado
Copy link
Contributor

TomasDado commented Apr 20, 2018

Description

When running btagging options with NoFit the code exists when no permutation is allowed in an event. This requires users to modify their selection for these b-tagging options. Possible workaround for this problem could be to provide a new option that works like kVetoNoFit and when an event with no allowed permutations occurs, the btagging option switches to kVetoLightNoFit which ensures that there are some allowed permutations in the event.

Note: Option with NoFit are desirable because they significantly reduce CPU time

Expected Behavior

New btagging option that saves CPU time by excluding some permutations that work with arbitrary number of btagged jets should be added

@TomasDado
Copy link
Contributor Author

Closed by #32

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

No branches or pull requests

2 participants