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

Make BadGlobalMuonTagger METFilter compliant. #10

Closed
wants to merge 1 commit into from
Closed

Make BadGlobalMuonTagger METFilter compliant. #10

wants to merge 1 commit into from

Conversation

riga
Copy link

@riga riga commented Feb 1, 2017

This PR changes the pass/fail logic of the BadGlobalMuonTagger in order be compliant with existing MET filters.

Instead of returning a found decision that denoted the existance of a found bad/duplicate muon, the filter now returns the pass decision. As a result, the module can be added to a sequence or path without sequence negation (~module/module.__invert__).

The module also produces a bool for the pass decision now, that can be evaluated in following analyzers when using the tagging mode with the same recipes as already described here.

Edit: Ok, I just found a HN with an identical proposal -.- ... but at least you might add this with a single click ;)

@riga
Copy link
Author

riga commented Feb 4, 2017

Closed this PR due to corruption caused by a base fork change. Cloned to #13.

@riga riga closed this Feb 4, 2017
gpetruc pushed a commit that referenced this pull request May 9, 2017
gpetruc pushed a commit that referenced this pull request Aug 16, 2017
gpetruc pushed a commit that referenced this pull request Aug 16, 2017
solved the problem with InputTag
gpetruc added a commit that referenced this pull request Jul 1, 2019
gpetruc pushed a commit that referenced this pull request Dec 6, 2023
make startup allocations safe on platforms where dlsym allocates memory
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.

1 participant