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
DisplacedGeneralStep in tracking #32036
Conversation
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32036/19587
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32036/19589
|
A new Pull Request was created by @doujadarej for master. It involves the following packages: DQM/TrackingMonitorSource @perrotta, @andrius-k, @kmaeshima, @ErnestaP, @cmsbuild, @jfernan2, @fioriNTU, @slava77, @jpata can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins.
|
IIUC, the new iteration is included by default. please provide timing comparisons with a recent 11_2_X release as a baseline and this PR for the full reco workflow. a standard set of tracking MTV plots for a Run3 workflow with PU would be useful as well (I guess out of the box matrix it can be 11834.0 or 11834.99). |
@@ -138,7 +138,8 @@ namespace reco { | |||
hiRegitMuTobTecStep = 43, | |||
hiRegitMuMuonSeededStepInOut = 44, | |||
hiRegitMuMuonSeededStepOutIn = 45, | |||
algoSize = 46 | |||
siStripTripletStep = 46, | |||
algoSize = 47 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about using the value of reservedForUpgrades1
instead? (at the time I meant it exactly for this kind of situation)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
makes sense; I guess the idea is to rename it.
BTW, isn't the siStripTriplet
confusing? pixel-less iteration is also a strip triplet iteration
also, what if down the road we decide to make it use 4 hits?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
makes sense; I guess the idea is to rename it.
Exactly, do
detachedQuadStep = 24,
- reservedForUpgrades1 = 25,
+ siStripTiripletStep = 25,
reservedForUpgrades2 = 26,
That would avoid the class version changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it might be that a new dedicated step (again targeting displaced tracking) would be added for Run3, in that case how should we proceed ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From what I see there is room for another one (reservedForUpgrades2)
Replacing reservedForUpgrades1 by SiStripTripletStep indeed makes it much simpler without changing much the structure (already tried)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if another "regional" displaced iteration is planned, how about we plan to use the reservedForUpgrades1
and reservedForUpgrades2
and name the proposed iteration displacedGeneralStep
while the one from Andrew will be displacedRegionalStep
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, sounds good to me, indeed
-1 Tested at: cf75f2b CMSSW: CMSSW_11_2_X_2020-11-05-1100 I found follow errors while testing this PR Failed tests: Build
I found compilation error when building: >> Building LCG reflex dict from header file src/DataFormats/GsfTrackReco/src/classes.h >> Compiling LCG dictionary: tmp/slc7_amd64_gcc820/src/DataFormats/GsfTrackReco/src/DataFormatsGsfTrackReco/a/DataFormatsGsfTrackReco_xr.cc >> Building shared library tmp/slc7_amd64_gcc820/src/DataFormats/GsfTrackReco/src/DataFormatsGsfTrackReco/libDataFormatsGsfTrackReco.so Copying tmp/slc7_amd64_gcc820/src/DataFormats/GsfTrackReco/src/DataFormatsGsfTrackReco/libDataFormatsGsfTrackReco.so to productstore area: >> Checking EDM Class Version for src/DataFormats/GsfTrackReco/src/classes_def.xml in libDataFormatsGsfTrackReco.so error: class 'reco::GsfTrack' has a different checksum for ClassVersion 20. Increment ClassVersion to 21 and assign it to checksum 866972163 Suggestion: You can run 'scram build updateclassversion' to generate src/DataFormats/GsfTrackReco/src/classes_def.xml.generated with updated ClassVersion gmake: *** [tmp/slc7_amd64_gcc820/src/DataFormats/GsfTrackReco/src/DataFormatsGsfTrackReco/libDataFormatsGsfTrackReco.so] Error 1 Leaving library rule at DataFormats/GsfTrackReco >> Leaving Package DataFormats/GsfTrackReco >> Package DataFormats/GsfTrackReco built |
Comparison job queued. |
@slava77
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32036/20881
|
Pull request #32036 was updated. @perrotta, @andrius-k, @kmaeshima, @ErnestaP, @cmsbuild, @silviodonato, @franzoni, @jfernan2, @fioriNTU, @slava77, @jpata, @qliphy, @fabiocos, @davidlange6 can you please check and sign again. |
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f8f7ff/12517/summary.html Comparison SummarySummary:
|
@doujadarej this PR only modifies Tracking/MessageLog folders in DQM, I understand that plots are being added in From your PR description I would have expected some DQM modifications. Can you confirm? |
@jfernan2 , I'm not sure what you mean, sorry. |
Hi @doujadarej |
+1 |
+1
|
+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 be automatically merged. |
PR description:
Added a tracking iteration after tobTecStep and PixelLess step
for displaced track reconstruction
Parameters for seeding, track building and track selection have been tuned in order to lower the fake rate and the extra timing.
Quality flags used are the same as the ones defined for TobTec Step.
Additional information and global presentation of the step can be found in these presentations in the TRKPOG :
https://indico.cern.ch/event/915033/contributions/3847313/attachments/2040507/3417260/trkpog_180520_DoujaDarej.pdf
https://indico.cern.ch/event/961478/contributions/4046679/attachments/2125576/3578591/trkpog_191020_DoujaDarej.pdf
PR validation:
Tests have been made on different samples :
Run3 MC :
DisplacedSUSY_stopToBottom_M_800_500mm_TuneCP5_14TeV_pythia8/Run3Summer19DR-106X_mcRun3_2021_realistic_v3-v2/GEN-SIM-DIGI-RAW
/TTbar_14TeV_TuneCP5_Pythia8/Run3Summer19DR-106X_mcRun3_2021_realistic_v3-v2/GEN-SIM-DIGI-RAW
WminusH_HToSSTobbbb_WToLNu_MH-125_MS-40_ctauS-500_TuneCUETP8M1_14TeV-powheg-pythia8/
Run2 MC :
/TTbar_13TeV_TuneCP5_Pythia8/RunIISummer19UL17DIGI-106X_mc2017_realistic_v6-v1/GEN-SIM-DIGI-RAW
Data :
/MET/Run2017B-HighMET-17Nov2017-v1/RAW-RECO
and several runTheMatrix workflows (basic test procedure suggested in the CMSSW PR instructions and using reconstruction:trackingOnly, trackingOnlyDQM and trackingOnlyValidation for seed monitoring.
commit 'add DisplacedGeneralStep' :
Change name of iteration SiStripTripletStep -> DisplacedGeneralStep
Add modifier to switch from default tracking to displacedTracking for Phase1 tracking flavour
Remove from ParticleFlow (for now?)
Replace reservedForUpgrades1 (step25) by SiStripTriplet instead of adding it (Step46)