-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Displaced tracking validation for Run 3 and Phase 2 #32157
Conversation
A new Pull Request was created by @jalimena (Juliette Alimena) for master. It involves the following packages: Validation/RecoTrack @andrius-k, @kmaeshima, @ErnestaP, @cmsbuild, @jfernan2, @fioriNTU can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@jalimena this PR is adding around 20k new MEs, I wonder if such a huge number of plots and possibilities is actually needed for Validation, I can imagine what a handicap can be to check all of them with releases and samples. On the other hand the configuration is creating the new plots for every MC workflow, could you please reduce it to just Phase2 and Run3 samples? Thanks |
Hi @jfernan2 indeed I don't want to add (or look at) 20k new plots! One thing I see I can do is to remove them for fastsim, but maybe that's not a great idea, given that fastsim is beginning to be used for long-lived particle signals? I also see in the code how I can add the collection just for phase 2 (i.e. with things like |
there is a run3 specific modifier: |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-57113f/12553/summary.html Comparison SummaryThe workflows 140.53 have different files in step1_dasquery.log than the ones found in the baseline. You may want to check and retrigger the tests if necessary. You can check it in the "files" directory in the results of the comparisons Summary:
|
There are a lot of changes in 140.53 unrelated to this PR.... has somebody seen it before? |
Note
in the comparison summary message. |
please test with #32036 |
Thanks @makortel I hadn't noticed it |
There is some more information in #32755 |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-57113f/12568/summary.html Comparison SummarySummary:
|
@jalimena do you plan to include those in this PR or in an independent one? |
@jfernan2 If I get some advice from anyone soon (perhaps @mtosi ?) about how to modify Configuration/PyReleaseValidation, I will happily include it promptly in this PR. However, I guess it is not strictly necessary and I can open a new one for it. If you all are ready to sign and merge it like ~now, then I can for sure open a new PR for the small additions needed. |
Ok, so let's decouple the plots from their actual enabling. Thanks |
+1 |
thanks to you! |
+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:
This PR adds a collection to the tracking validation to validate displaced tracks. In particular, the usual tip and lip cuts on the tracking particles are relaxed. The collection is turned on only by use of a procModifier as shown below.
PR validation:
I've run the RECO, validation, and DQM steps (standard and trackingOnly) for ttbar and DisplacedSUSY samples, with Run 3 and Phase 2 conditions.
For example:
cmsDriver.py step3 --conditions auto:phase1_2021_realistic -s RAW2DIGI,L1Reco,RECO,RECOSIM,EI,PAT,VALIDATION:@standardValidation+@miniAODValidation,DQM:@standardDQM+@ExtraHLT+@miniAODDQM --datatier GEN-SIM-RECO,MINIAODSIM,DQMIO -n 200 --geometry DB:Extended --era Run3 --eventcontent RECOSIM,MINIAODSIM,DQM --procModifiers displacedTrackValidation --no_exec
run over the displaced SUSY sample in Run 3 conditions (0 PU), and then harvesting the DQM, produces these plots as output:
https://jalimena.web.cern.ch/jalimena/plots/track_validation_plots_dispSUSY_2021PU0_11_3_0_pre2_ProcModifier/
and
cmsDriver.py step3_trackingOnly --conditions auto:phase2_realistic_T15 -s RAW2DIGI,RECO:reconstruction_trackingOnly,VALIDATION:@trackingOnlyValidation,DQM:@trackingOnlyDQM --datatier GEN-SIM-RECO,DQMIO -n 200 --geometry Extended2026D49 --era Phase2C9 --eventcontent RECOSIM,DQM --procModifiers displacedTrackValidation --no_exec
run over a ttbar sample in phase 2 conditions with the trackingOnly sequence (0 PU), and then harvesting the DQM, produces these plots as output:
https://jalimena.web.cern.ch/jalimena/plots/track_validation_plots_ttbar_phase2PU0_trackingOnly_11_3_0_pre2_ProcModifier/
if this PR is a backport please specify the original PR and why you need to backport that PR:
not a backport