-
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
Adding ZDC packer #44019
Adding ZDC packer #44019
Conversation
cms-bot internal usage |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44019/38948
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
@matt2275 , please fix the code-format issues using Just for my own understanding: does this PR as is take care of introducing all we need to re-emulate ZDC in the FYI: @cms-sw/l1-l2 @cms-sw/hlt-l2 |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44019/38965 |
A new Pull Request was created by @matt2275 for master. It involves the following packages:
@cmsbuild, @aloeliger, @epalencia can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@missirol, I don't believe there is a L1 ZDC simulation yet so I don't think those files should be changed at the moment but I'm not an expert and could be mistaken. |
@missirol I don't think we should need to change anything much else in the configurations? This just adds the ZDC packer to the GT packing step, so anywhere that is used should get this by default. Most of the configurations you linked are defining L1 emulator unpack steps that otherwise, except for L1's emulation of L1, go un-used, or at least that is my interpretation. In any case, I don't see a GT step in any of those that could be modified to account for ZDC I think. |
@matt2275 Did you have any plots or outputs from the RAW->DIGI->RAW test you performed to test the packer? |
@eyigitba FYI |
please test |
I think the pull request is ready for review. In addition to making sure the repacked zdc sums match the original zdc sums. I made sure the new zdc packer wouldn't cause a crash if the collection name were incorrect or unused by the cms job. In that case, it gives a warning that the collection could not be found but doesn't throw any fatal errors. Is there any other things I should check before marking the pull request ready for review? |
@matt2275 I think that's good for now. Please mark this as good for review and maybe we can ping experts for any extra testing if needed. |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-541f95/37742/summary.html Comparison SummarySummary:
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44019/39399
|
Pull request has been put on hold by @antoniovilela |
Pull request #44019 was updated. @aloeliger, @epalencia, @cmsbuild can you please check and sign again. |
unhold |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-541f95/38050/summary.html Comparison SummarySummary:
|
+l1 re-sign |
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. @antoniovilela, @rappoccio, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Adding a ZDC packer to EventFilter/L1TRawtoDigi
Only output change should be L1TDigitoRaw now can include EtSumZDC info.
PR has no dependencies
PR validation:
PR tested with EventFilter/L1TRawtoDigi/test/test_RawToDigiToRawToDigi_GT_cfi.py where the output produces 2 sets of data:
These 2 data sets were compared and were identical for EtSumZDC data.
I attached the summary of the RunTheMatrix test where there were some failures
RunTheMatrixSummary.txt