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
Fix QuickTrackAssociatorByHits for composite hits #20364
Fix QuickTrackAssociatorByHits for composite hits #20364
Conversation
…instead of hits Otherwise composite hits will always be treated as "duplicates".
The code-checks are being triggered in jenkins. |
A new Pull Request was created by @makortel (Matti Kortelainen) for master. It involves the following packages: SimTracker/TrackAssociatorProducers @cmsbuild, @civanch, @mdhildreth can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/PR-20364/478 Code check has found code style and quality issues which could be resolved by applying a patch in https://cmssdt.cern.ch/SDT/code-checks/PR-20364/478/git-diff.patch You can run |
The code-checks are being triggered in jenkins. |
Pull request #20364 was updated. @cmsbuild, @civanch, @mdhildreth can you please check and sign again. |
+code-checks |
@cmsbuild, please test |
The tests are being triggered in jenkins. |
-1 Tested at: d3e1f4a The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: You can see the results of the tests here: I found follow errors while testing this PR Failed tests: RelVals AddOn
When I ran the RelVals I found an error in the following worklfows: runTheMatrix-results/5.1_TTbar+TTbarFS+HARVESTFS/step1_TTbar+TTbarFS+HARVESTFS.log135.4 step1 runTheMatrix-results/135.4_ZEE_13+ZEEFS_13+HARVESTUP15FS+MINIAODMCUP15FS/step1_ZEE_13+ZEEFS_13+HARVESTUP15FS+MINIAODMCUP15FS.log
I found errors in the following addon tests: cmsDriver.py TTbar_13TeV_TuneCUETP8M1_cfi --conditions auto:run2_mc --fast -n 100 --eventcontent AODSIM,DQM --relval 100000,1000 -s GEN,SIM,RECOBEFMIX,DIGI:pdigi_valid,L1,DIGI2RAW,L1Reco,RECO,EI,VALIDATION --customise=HLTrigger/Configuration/CustomConfigs.L1THLT --datatier GEN-SIM-DIGI-RECO,DQMIO --beamspot NominalCollision2015 --era Run2_25ns : FAILED - time: date Mon Sep 4 12:32:50 2017-date Mon Sep 4 12:29:10 2017 s - exit: 35584 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison not run due to runTheMatrix errors (RelVals and Igprof tests were also skipped) |
The code-checks are being triggered in jenkins. |
Pull request #20364 was updated. @cmsbuild, @civanch, @mdhildreth can you please check and sign again. |
+code-checks |
@cmsbuild, please test Fixed FastSim by keeping |
The tests are being triggered in jenkins. |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+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 (and backports should be raised in the release meeting by the corresponding L2) |
I wonder why there are changes in |
+1 |
This PR fixes a long-standing bug in QuickTrackAssociatorByHits regarding composite hits (=hits having >= 2 clusters). Currently the "matched hit fraction" is in fact calculated as
so hits with 2 cluster are ounted as 2 in the numerator and 1 in denominator. The bug does not affect the offline track monitoring as in offline the strip matched hits are split in the final fit. The affected cases are
The fix is to change the denominator to
N(clusters of track)
so one could say that the association is now actually done "by clusters". Note that this is done only forClusterTPAssociation
mode, theTrackerHitAssociator
mode is kept in counting hits.Here are MTV plots for phase1
https://cms-tracking-validation.web.cern.ch/cms-tracking-validation/PR/CMSSW_9_3_0_pre3_PR20364/
showing no effect for tracks
https://cms-tracking-validation.web.cern.ch/cms-tracking-validation/PR/CMSSW_9_3_0_pre3_PR20364/phase1_ttbar_pu35_summary/summary.pdf
and decrease in efficiency of seeds with strip hits
https://cms-tracking-validation.web.cern.ch/cms-tracking-validation/PR/CMSSW_9_3_0_pre3_PR20364/phase1_ttbar_pu35_seeding_summary_seeds/summary.pdf
Plots for HLT (thanks to @JanFSchulte) can be found from
https://cms-tracking-validation.web.cern.ch/cms-tracking-validation/PR/CMSSW_9_3_0_pre3_PR20364_HLT/
showing decrease in efficiency (especially in |eta| > 1) and increase in fake rates.
Tested in 9_3_0_pre3, expecting no changes in offline track plots, and decrease in efficiency and increase in fake rates for HLT track plots.
@rovere @VinInn @ebrondol @JanFSchulte @mtosi @slava77 @perrotta