-
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
PPS Pixel data unpacking #35067
PPS Pixel data unpacking #35067
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35067/24949
|
A new Pull Request was created by @fabferro (Fabrizio Ferro) for master. It involves the following packages:
@jpata, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2bbeda/18131/summary.html Comparison SummarySummary:
|
Could a unit test / test config be useful here? |
Kind ping @fabferro. Just to clarify, I think this looks fine from the reco point of view, but typically we try to ask for the possibility (if it's not unreasonably complicated or useless) to have a test for new functionality, to be able to (at least in principle) run the code we sign. I think in this case a small test config on some testbeam data file could be helpful. Let me know what you think! |
It sounds reasonable. I'll ask PPS online people to provide me a(nother) data file and a temporary DAQ map. |
Could something be done in analogy to PR#34759, https://github.com/ChrisMisan/cmssw/blob/465b1657fb94e540dd43becf6ccb9073654b2e42/RecoPPS/Local/test/totemTiming_digiConverter_reco_cfg.py? The test file could then perhaps be located in |
from Configuration.Eras.Modifier_ctpps_2016_cff import ctpps_2016 | ||
from Configuration.Eras.Modifier_ctpps_2017_cff import ctpps_2017 | ||
from Configuration.Eras.Modifier_ctpps_2018_cff import ctpps_2018 | ||
(ctpps_2016 | ctpps_2017 | ctpps_2018).toModify(ctppsPixelDigis, isRun3 = cms.bool(False) ) |
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.
Slava pointed to me that the type does not need (should not) be specified here, sorry for missing it earlier.
(ctpps_2016 | ctpps_2017 | ctpps_2018).toModify(ctppsPixelDigis, isRun3 = cms.bool(False) ) | |
(ctpps_2016 | ctpps_2017 | ctpps_2018).toModify(ctppsPixelDigis, isRun3 = False ) |
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.
I missed it too when I re-read the code before submission. Slava never misses! ;-)
Thanks.
BTW, it works fine as well...
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35067/25032
|
The test config just added reads lab data from /eos/cms/store/group/dpg_ctpps/comm_ctpps/PixelAlive_562_RAW.root and produces a root file with DIGIs applying a dummy DAQ map (/eos/cms/store/group/dpg_ctpps/comm_ctpps/CTPPSPixel_DAQMapping_AnalysisMask.db). The output, if limited to a few events only, can be manually compared with a binary-to-txt-dump file /eos/cms/store/group/dpg_ctpps/comm_ctpps/Run562_dumpBinary.txt. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35067/25052
|
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2bbeda/18281/summary.html Comparison SummarySummary:
|
+reconstruction
|
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. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR modifies the PPS pixel unpacking code in view of the changes for Run3.
The changes concern 13 out of 64 bits of the data word that encode the pixel coordinates: the "double column-pixel id" convention is changed into a "column-row" one, due to the use of a slightly different readout chip (PROC600 instead of PsiDIG46).
The back compatibility with Run2 data is ensured by means of era modifiers: Run3 convention becomes the default one and Run2 one is triggered by means of ctpps_201* era modifiers.
The part of the code packing the simulated data is also changed accordingly.
PR validation:
The detectors are not yet installed. They will be installed beginning of November 21. Private validation on lab data, Run2 data and full simulation was done.
if this PR is a backport please specify the original PR and why you need to backport that PR:
No backport expected.