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

RU CSC segment builder update #17543

Merged
merged 3 commits into from Feb 21, 2017
Merged

Conversation

nvoytish
Copy link
Contributor

Some bugs omitted and optimization done.
The RU algo switched as the default CSC segment building algorithm.

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @nvoytish for CMSSW_9_0_X.

It involves the following packages:

RecoLocalMuon/CSCSegment

@cmsbuild, @cvuosalo, @slava77, @davidlange6 can you please review it and eventually sign? Thanks.
@ptcox, @bellan, @abbiendi, @jhgoh this is something you requested to watch as well.
@davidlange6, @smuzaffar you are the release manager for this.

cms-bot commands are listed here #13028

@nvoytish
Copy link
Contributor Author

@slava77
Copy link
Contributor

slava77 commented Feb 17, 2017

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 17, 2017

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/17838/console Started: 2017/02/17 13:59

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

@slava77
Copy link
Contributor

slava77 commented Feb 20, 2017

+1

for #17543 66a843a

  • implementation in line with the description; the main feature is RU algo switched as the default CSC segment building algorithm
  • jenkins tests pass and comparisons with the baseline show differences that start from cscSegments (reduction in number of segments per event mainly in short segments) and propagate downstream to muons, tracks (via muon iterations) and higher level objects.
  • local tests with higher statistics and more targeted samples confirm behavior expected as presented in slides in the RECO and CSC meting(s) RU CSC segment builder update #17543 (comment). Some summary and details follow below.

In PU35 ttbar events (wf 10224)

  • about 16% fewer cscSegments , mostly the shorter ones are gone
    all_sign862vsorig_ttbar13tevpu2017wf10224p0c_cscdetidcscsegmentsownedrangemap_cscsegments__reco_obj_collection__data__degreesoffreedom
  • about 16% less pf muons, a reduction mainly in the endcaps as expected (this reduction is balanced out by a matching increase in pf charged hadrons)
    all_sign862vsorig_ttbar13tevpu2017wf10224p0c_recopfcandidates_particleflow__reco_obj_eta57

Muon 1TeV gun:

  • a factor of 1.5 fewer CSC segments, with reduction mainly in worse quality and shorter segments

wf10009_cscseg_chi2

Multi-track validation plots show roughly unchanged performance for signal muons and some reduction in the muon fake rate.

  • efficiency in 10 GeV muon gun sample (using 2K muons) is apparently down by o(0.1%)
  • efficiency in 1 TeV muon gun sample is roughly unchanged (to within o(0.1%) )
  • track parameter pulls look roughly the same in the core with some reduction in the tails (as expected from presented slides)

On the technical side, based on PU35 ttbar (10224)

  • cscSegments time is up from 1 ms to 3ms per event, still rather negligible
  • downstream muon-related module times are down (e.g. cosmics or displaced muons CPU is down by ~10%) for a total of about 0.5% reduction in total reco time

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_9_0_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar

@ptcox
Copy link
Contributor

ptcox commented Feb 20, 2017 via email

@slava77
Copy link
Contributor

slava77 commented Feb 20, 2017 via email

@davidlange6
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit 09b61b9 into cms-sw:CMSSW_9_0_X Feb 21, 2017
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

5 participants