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
[10_1_X] SiStrip (un)packer: fixes and support for nonstandard ZS(lite) modes #23620
[10_1_X] SiStrip (un)packer: fixes and support for nonstandard ZS(lite) modes #23620
Conversation
- rename the PACKET_CODE definitions for ZS lite to ZS - change the packetCode implementation: default (0) for ZS lite modes, taken from the third byte for ZS Reason: for ZS lite there are no packet codes, the packing scheme is given by the readout mode; for non-lite ZS it is in the channel data
- add "PacketCode" option to SiStripDigiToRawModule - add packetCodeFromString conversion in SiStripFEDBufferComponents - pass the packet code on to FEDBufferPayloadCreator::fillChannelBuffer
workaround for a bug in the pre-2015 packer (eg. 140.53_RunHI2011)
In debug mode all messages are still printed, otherwise a summary (warning type and count) is printed after unpacking the event.
A new Pull Request was created by @pieterdavid (Pieter David) for CMSSW_10_1_X. It involves the following packages: Configuration/StandardSequences @perrotta, @civanch, @mdhildreth, @cmsbuild, @franzoni, @slava77, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1
|
+1 |
Dear @fabiocos - Would it be possible to get this integrated in the next 10_1_X in order to make it available for operation ? Thanks |
@fabiocos |
@fabiocos may I ask if there is at this point any plan to include this PR in the 10_1_X cycle or shall we just have in post-TS2 data in 10_2_X? This is somehow a nuisance for continuing tests on the HW side at P5. |
@fabiocos, indeed the data report is missing (which is a pity) and the report from @boudoul on simulation (https://hypernews.cern.ch/HyperNews/CMS/get/relval/10839.html) is indeed still open (likely because of many changes introduced in the pixel detector) but a quick look at Strip workspace pointed in the "work in progress" report (https://goo.gl/ThZvmN) makes me conclude that the outcome is positive (I do not see catastrophically wrong changes). |
+operations backport from master |
This pull request is fully signed and it will be integrated in one of the next CMSSW_10_1_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_10_2_X is complete. This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 Tracker validation of CMSSW_10_2_0_pre6 is reported ok |
Thanks @fabiocos , do you have an estimate when 10_1_9 will come ? In our case the earlier , the better |
backport of #23417
(as discussed in last Friday's reco meeting (see this contribution))
No changes in the tests are expected, except (as in the 10_2 PR) for warnings:
CC: @alesaggio @OlivierBondu @vidalm @mmusich @echabert @erikbutz