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

Use pixel seed extension for phase1 in initialStep #14621

Merged

Conversation

makortel
Copy link
Contributor

The title says it all. The change was discussed and agreed in May 9 TRK POG meeting
https://indico.cern.ch/event/527844/contributions/2161117/attachments/1269921/1881271/slides_phase1_20160509.pdf

The main point is to exercise regularly the pixel seed extension code from #14356. For 2017 production we may revert this and go back to "quadruplets by triplet propagation" also in initialStep.

Please find below MultiTrackValidator plots with 1000 TTbar+PU35 events showing the effect of this PR on top of 8_1_0_pre5+#14545 (strip alignment as in run2_asymptotic GT)
https://mkortela.web.cern.ch/mkortela/tracking/validation/CMSSW_8_1_0_pre5_pse/

Tested in CMSSW_8_1_X_2016-05-24-1100, non-2017 workflows should have no effect. 2017 workflows should have small effect on the level of generalTracks (mainly decrease of duplicate rate), while initialStep and highPtTripletStep have larger changes (mainly migration from highPtTripletStep to initialStep).

@rovere @VinInn

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @makortel (Matti Kortelainen) for CMSSW_8_1_X.

It involves the following packages:

RecoTracker/IterativeTracking

@cmsbuild, @cvuosalo, @slava77, @davidlange6 can you please review it and eventually sign? Thanks.
@ghellwig, @GiacomoSguazzoni, @rovere, @VinInn, @mschrode, @gpetruc, @dgulhan this is something you requested to watch as well.
@slava77, @Degano, @smuzaffar you are the release manager for this.

cms-bot commands are list here #13028

@VinInn
Copy link
Contributor

VinInn commented May 24, 2016

@cmsbuild , please test

@cmsbuild
Copy link
Contributor

cmsbuild commented May 24, 2016

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/13161/console

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

@slava77
Copy link
Contributor

slava77 commented May 25, 2016

in 10224 on 100 events:
fewer and shorter electron seeds
all_sign710-histatvsorig-histat_ttbar13tevpu2017wf10224p0c_recoelectronseeds_electronmergedseeds__reco_obj_nhits

there are a few more gedGsfElectrons and they are apparently with smaller fbrem
all_sign710-histatvsorig-histat_ttbar13tevpu2017wf10224p0c_recogsfelectrons_gedgsfelectrons__reco_obj_fbrem

Charged hadron yield reduces at higher eta (much smaller effect in generalTracks)
all_sign710-histatvsorig-histat_ttbar13tevpu2017wf10224p0c_recopfcandidates_particleflow__reco_obj_eta12

as expected in the PR description: there is a migration from highPtTripletStep to initialStep in generalTracks
all_sign710-histatvsorig-histat_ttbar13tevpu2017wf10224p0c_recotracks_generaltracks__reco_obj_algo

The effect on electron seeds is even larger in ZEE PU35 sample 10225
all_sign710-histatvsorig-histat_zee13tevpu2017wf10225p0c_recoelectronseeds_electronmergedseeds__reco_obj_nhits
It looks like electrons are more effectively made with these shorter seeds, since the effect on ged electrons is somewhat positive.

There is some decrease in fakes+dups in generalTracks
https://mkortela.web.cern.ch/mkortela/tracking/validation/CMSSW_8_1_0_pre5_pse/ttbar_pu_ootb/effandfake4.pdf
.. these are in line with the presentation in the tracking POG

Before signing, I wanted to check if the large effect on electron seeding is intended.

@makortel
Copy link
Contributor Author

Thanks @slava77 for pointing it out. Electron seeds become shorter because they use initialStepSeeds (among others) and those are changed from quadruplets to triplets in this PR. I produced MTV plots for gsfElectrons (1000 events of ttbar+PU)
https://mkortela.web.cern.ch/mkortela/tracking/validation/CMSSW_8_1_0_pre5_pse_ele/ttbar_pu_electronGsf.html
and I don't see any statistically significant effect. So even though the electron seeds change, the downstream effects seem to be negligible. And anyway the (tracking) tuning is not final, but point taken.

@slava77
Copy link
Contributor

slava77 commented May 26, 2016

@makortel remind me, please, what are the selections for TP in the gsf MTV.
Is it primary electrons or something else/more?

@makortel
Copy link
Contributor Author

@slava77 For efficiencies, first only TrackingParticles with abs(pdgId)==11 are selected
https://github.com/cms-sw/cmssw/blob/CMSSW_8_1_X/Validation/RecoTrack/python/TrackValidation_cff.py#L272
and then the usual plot-specific selections are applied
https://github.com/cms-sw/cmssw/blob/CMSSW_8_1_X/Validation/RecoTrack/python/TrackingParticleSelectionsForEfficiency_cff.py

Fake and duplicate rates are calculated wrt. all (also non-electron) TrackingParticles.

@slava77
Copy link
Contributor

slava77 commented May 26, 2016

+1

for #14621 48c74d0

  • configuration code changes are in line with the description; only phase1 is affected
  • jenkins tests pass and show differences only in phase 1 workflow
  • local tests with higher stats using 10224 and 10225 with PU and 100{24,25,26} without pileup don't show major changes in final (generalTracks) performance: efficiency is about the same and duplicate rates are smaller as expected; electron seeding is using triplets now and the electron efficiency is about the same (MTV GSF plots are good), there is some reduction in fbrem.

@cmsbuild
Copy link
Contributor

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

@davidlange6
Copy link
Contributor

+1

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.

5 participants