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
RPCMuon bugfix in MuonIdProducer #4902
Conversation
A new Pull Request was created by @jhgoh (Junghwan John Goh) for CMSSW_7_2_X. RPCMuon bugfix in MuonIdProducer It involves the following packages: RecoMuon/MuonIdentification @nclopezo, @cmsbuild, @Degano, @StoyanStoynev, @slava77 can you please review it and eventually sign? Thanks. |
@jhgoh could you clarify your description? With the new code you are adding to the muon collection muons that are RPC only (and eventually reducing the calo muons). In the previous code they would not be there at all, thus they were not a "subset" of the tracker muons, if anything they were a subset of the calo muons. Am I reading it wrong? |
Ignore my comment about calo muons it is wrong and not relevant, the rest is relevant. |
The original purpose of RPCMuon is to keep muons even if DT/CSC hits are missing. For the typesetting: I missed this part, I think this typesetting have to be moved to line 623, with separate if-statements. |
Then I expect you to update the PR with the new if-statements. |
Applied RPCMuon type set. |
+1 tested with extended/higher stat tests in CMSSW_7_2_X_2014-08-11-1400 (test area sign408) Changes as expected
|
Bypassing DQM since the change is the same also for RECO and Slava was ok with it. @deguio @danduggan complain if not ok. |
The RPCMuon is mis-implemented as a subset of TrackerMuons.
Originally it is designed to be a complementary ones to the TM's.