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
BugFix for L3MuonCandidateProducerFromMuons #22774
BugFix for L3MuonCandidateProducerFromMuons #22774
Conversation
…degrading for very high-pt muons, this brings back the possibility of using the innerTrack when available and using the outerTrack otherwise
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-22774/4144 |
A new Pull Request was created by @folguera (Santiago Folgueras) for master. It involves the following packages: RecoMuon/L3MuonProducer @perrotta, @cmsbuild, @silviodonato, @slava77, @Martin-Grunewald, @fwyzard can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
Even if we will definitely move to 10_1_X, I think it is good if you propagate this fix to 10_0_X too. |
Comparison job queued. |
This implies that for high pT muons the parameters of the muonBestTrack() are "worst" than the ones obtained from the innerTrack(), at least for this purpose. Out of curiosity: do you understand why? |
Comparison is ready Comparison Summary:
|
+1 |
+1
|
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
@folguera |
Matching efficiency was degrading for very high-pt muons, this brings back the possibility of using the innerTrack when available and using the outerTrack otherwise. This recovers the missing efficiency.