-
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
Fix the delay of the CPPF DAQ data #38974
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38974/31428
|
A new Pull Request was created by @mileva for master. It involves the following packages:
@jpata, @cmsbuild, @clacaputo can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@@ -217,7 +220,7 @@ void RPCCPPFUnpacker::processRXRecord(RPCAMCLink link, | |||
return; | |||
} | |||
|
|||
if (bx < bx_min || bx > bx_max) { | |||
if ((bx - cppfDaq_Delay) < bx_min || (bx - cppfDaq_Delay) > bx_max) { |
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.
wouldn't it make sense to define e.g.
auto bx_corrected = bx - cppfDaq_Delay;
and use it everywhere where the shifted value must be used? does the meaning of bx==0 change or stay the same (e.g. a few lines below here)?
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.
Thanks @jpata
does the meaning of bx==0 change or stay the same
Good question! It looks that is needed for the DPG analysis, but could be deeper. Let me have some time to debug and investigate.
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.
auto bx_corrected implemented as suggested.
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.
Hi @jpata !
I have updated #38979, as well.
On the question "does the meaning of bx==0 change or stay the same".
I checked and it does change nothing both in the CPPF DAQ data (attached cppf_rpc_daq_bx_check.png) or in the input to EMTF (l1_L1Stage2EMTF_rpcHitBX.png).
So, we would prefer to not touch it for the moment.
In order to test I used 136.897_RunCosmics2021CRUZET workflow, but I changed the input data. The default run for this workflow is 344518, however in this run the CPPF key were not enabled to EMTF. (I.e. - no RPC input to EMTF, just DAQ data.) Because of this I changed with another cosmics run 356088.
runTheMatrix test ran without problems.
However, I decided to run with more events - the default are 100 events.
And on the 102th event the Module: L1TStage2CPPF:l1tStage2Cppf crashed with segmentation violation.
But I don't think the crash is caused of our update,
as the same module already was reported to crash with release validation after it was already merged, further to latest comments in #38564 .
ping @ram1123 and @zhangcg123
I can give more details during the meeting.
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-3adec0/26653/summary.html Comparison SummarySummary:
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38974/31464
|
Pull request #38974 was updated. @jpata, @cmsbuild, @clacaputo can you please check and sign again. |
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-3adec0/26720/summary.html Comparison SummarySummary:
|
Hi @dilsonjd , @jpata , @zhangcg123 |
Sorry I missed the point here - what is the segfault you are talking about? We can see some differences in RPC distributions https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_12_5_X_2022-08-09-1100+3adec0/52044/validateJR/all_OldVSNew_RunMinimumBias2021wf139p001/all_OldVSNew_RunMinimumBias2021wf139p001c_RPCDetIdRPCRecHitsOwnedRangeMap_rpcRecHits__reRECO_objAT_size.png https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_12_5_X_2022-08-09-1100+3adec0/52044/validateJR/all_OldVSNew_RunMinimumBias2021wf139p001/all_OldVSNew_RunMinimumBias2021wf139p001c_RPCDetIdRPCRecHitsOwnedRangeMap_rpcRecHits__reRECO_obj_collection__data__localPosition_x.png which I understand are expected. Surprisingly nothing in muons downstream (too rare?). I think enabling this change with the Run3_RPC modifier seems reasonable, if it's not planned for Run2 or Phase2. Are there any studies left you want to do here or is this PR ready? |
Hi @jpata About the MinBias - validation plots: Yes, the changes are expected. As a consequence of the "delayed" daq data some of the offline rpc clusters in the endcap were not reconstructed and thus not stored in the data. About the muons: in general there are not too much muons in the MinBias data. From the other hand the RPC rechits are not widely used in the reconstruction, but rather for the the timing studies. Modification is for Run3. We do not need this for Run2 and we don't have plan to explore it in phase 2. I don't think we can make some more studies at this moment and I would like to ask to approve this pull request. Thank you! |
+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, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
@mileva can you please edit the title to be the same as you used for the 12_4_X version of this PR? That one is a lot more descriptive. |
just to clarify, you can remove 12_4_X from the title :) |
+1 |
PR description:
To fix the CPPF DAQ delay and RPC offline clusters BX association.
PR validation:
Tested with:
runTheMatrix and three different workflows:
136.897_RunCosmics2021CRUZET+RunCosmics2021CRUZET+RECOCOSDRUN3+ALCACOSDRUN3+HARVESTDCR3
140.103_RunSingleMuon2022B+RunSingleMuon2022B+HLTRUN3+RECONANORUN3+SKIMSINGLEMUONRUN3
140.117_RunCosmics2022B+RunCosmics2022B+HLTRUN3+RECOCOSMRUN3+SKIMCOSMICSRUN3
And also with private validation and offline analysis.
More details and validation plots might be found here.
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
None, to be backported in 12_4_X
Mention @dilsonjd @jhgoh @andresib