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

RPCMuon bugfix in MuonIdProducer #4902

Merged
merged 8 commits into from Aug 21, 2014
Merged

RPCMuon bugfix in MuonIdProducer #4902

merged 8 commits into from Aug 21, 2014

Conversation

jhgoh
Copy link
Contributor

@jhgoh jhgoh commented Aug 7, 2014

The RPCMuon is mis-implemented as a subset of TrackerMuons.
Originally it is designed to be a complementary ones to the TM's.

@cmsbuild
Copy link
Contributor

cmsbuild commented Aug 7, 2014

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.
@bellan, @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.

@StoyanStoynev
Copy link
Contributor

@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?
What about type setting? What is the purpose of the line 590 (trackerMuon.setType( reco::Muon::TrackerMuon | reco::Muon::RPCMuon );), shouldn't you do that now separately for TrMu and RPCMu after line 623? As it stands now, how do we know if the muon in the collection is TrMu or RPCMu
(given it is not GLB/STA)?

@StoyanStoynev
Copy link
Contributor

Ignore my comment about calo muons it is wrong and not relevant, the rest is relevant.

@jhgoh
Copy link
Contributor Author

jhgoh commented Aug 8, 2014

The original purpose of RPCMuon is to keep muons even if DT/CSC hits are missing.
The current code will skip muons if it does not pass 'goodTrackerMuon' condition even though it passes 'goodRPCMuon'. Thus some muons only with RPC hit will be lost (although it is expected not to be often in ideal situations).

For the typesetting: I missed this part, I think this typesetting have to be moved to line 623, with separate if-statements.

@cmsbuild
Copy link
Contributor

cmsbuild commented Aug 8, 2014

@StoyanStoynev
Copy link
Contributor

Then I expect you to update the PR with the new if-statements.

@jhgoh
Copy link
Contributor Author

jhgoh commented Aug 8, 2014

Applied RPCMuon type set.

@cmsbuild
Copy link
Contributor

cmsbuild commented Aug 8, 2014

Pull request #4902 was updated. @nclopezo, @cmsbuild, @Degano, @StoyanStoynev, @slava77 can you please check and sign again.

@cmsbuild
Copy link
Contributor

@slava77
Copy link
Contributor

slava77 commented Aug 18, 2014

+1

for #4902 4060bf0

tested with extended/higher stat tests in CMSSW_7_2_X_2014-08-11-1400 (test area sign408)

Changes as expected

  • RPC flag is now set correctly (previously every tracker muon had RPC flag set)
  • additional RPC (notTracker) muons appear mainly in jetty events (~10% in QCD dijet; vs single-muon events with <0.1% added)

@ktf
Copy link
Contributor

ktf commented Aug 21, 2014

Bypassing DQM since the change is the same also for RECO and Slava was ok with it. @deguio @danduggan complain if not ok.

ktf added a commit that referenced this pull request Aug 21, 2014
RPCMuon bugfix in MuonIdProducer
@ktf ktf merged commit 977d587 into cms-sw:CMSSW_7_2_X Aug 21, 2014
@jhgoh jhgoh deleted the RPCMuonFix branch October 11, 2014 17:42
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

6 participants