-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Strip hybrid zero suppression: do less work if the APV is already zero-suppressed #29759
Strip hybrid zero suppression: do less work if the APV is already zero-suppressed #29759
Conversation
…ero-suppressed APVs
…sable by the regional unpacker
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29759/15206
|
A new Pull Request was created by @pieterdavid (Pieter David) for master. It involves the following packages: RecoLocalTracker/SiStripClusterizer @perrotta, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
Thanks! |
please abort |
Jenkins tests are aborted. |
please test workflow 140.55 |
The tests are being triggered in jenkins.
|
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29759/15271
|
please test workflow 140.55 |
The tests are being triggered in jenkins.
|
+1 |
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. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Changed the implementation of the zero-suppression for hybrid strip tracker data, where most of the APVs are zero-suppressed in the FED, and some detected as having a non-flat or shifted baseline, and fully read out. When the software zero-suppression processes these data, the digis for APVs that were already zero-suppressed can simply be copied, but the current implementation would still recalculate the common mode (and ignore the result from that).
The time gain for a 2021 HI scenario is difficult to estimate (it depends on occupancy and the number of APVs that is not zero-suppressed by the FEDs), but should be significant, about an order of magnitude less time spent in the ZS (on the 2015 VR file I used for validation a factor 14).
With the changes above it didn't really make sense anymore to have different "convert hybrid to raw digis" and two suppressHybridData methods, so I made it one that can handle the calls from both the ZS module and the regional unpacker; I also removed the option to write the raw digis out again from the ZS for hybrid inputs (it was not used anywhere, and keeping this would have made the rest more complicated and inefficient).
PR validation:
No changes are expected. I did a digi-to-digi comparison by adding a flag to switch between the old and new implementation (removed only in the last commit), on 2018 repacked data (as in the HI benchmarks), config, and 2015 VR data with hybrid emulation, config; I also checked that the digis are the same between the full sequence and the regional unpacker (which calls the zero-suppression in a slightly different way, I think it may have been wrong before, but was not used).
Could this be tested with workflow 140.55? I think that's the only one that uses this code.
CC: @icali @CesarBernardes