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

74X backport assign muon PDG id using PFMuon charge #11840

Closed
wants to merge 1 commit into from

Conversation

jhgoh
Copy link
Contributor

@jhgoh jhgoh commented Oct 16, 2015

Backport of #11838 to fix wrong pdg id assignment of muons

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @jhgoh (Junghwan John Goh) for CMSSW_7_4_X.

74X backport assign muon PDG id using PFMuon charge

It involves the following packages:

RecoMuon/MuonIdentification

@cmsbuild, @cvuosalo, @slava77 can you please review it and eventually sign? Thanks.
@battibass, @abbiendi, @bellan, @trocino, @bachtis, @rociovilar this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
If you are a L2 or a release manager you can ask for tests by saying 'please test' in the first line of a comment.
@Degano you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

@slava77
Copy link
Contributor

slava77 commented Oct 16, 2015

Considering that the bug has a 4-year history of being validated, I don't think fix is needed in 74X (open only to fixes in data processing operational issues)

@jhgoh
Copy link
Contributor Author

jhgoh commented Oct 19, 2015

I'm closing this PR.

@jhgoh jhgoh closed this Oct 19, 2015
@jhgoh jhgoh deleted the SetMuonPdgIdFromPFCharge74 branch October 19, 2015 11:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants