-
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
GEM - fed data size bugfix [EventFilter/GEMRawToDigi] #31776
GEM - fed data size bugfix [EventFilter/GEMRawToDigi] #31776
Conversation
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31776/19026
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31776/19027
|
A new Pull Request was created by @jshlee (Jason Lee) for master. It involves the following packages: EventFilter/GEMRawToDigi @perrotta, @jpata, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@@ -266,9 +268,12 @@ void GEMDigiToRawModule::produce(edm::StreamID iID, edm::Event& iEvent, edm::Eve | |||
fedRawData.resize(dataSize); | |||
|
|||
uint64_t* w = reinterpret_cast<uint64_t*>(fedRawData.data()); | |||
for (const auto& word : words) | |||
for (const auto& word : words) { | |||
#ifdef EDM_ML_DEBUG |
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.
It is curious that you use both LogDebug
and #ifdef EDM_ML_DEBUG
in the same class: was any of them a remnant of your validation of the fix, or are they supposed to remain both?
In any case, a
#include "FWCore/MessageLogger/interface/MessageLogger.h"
statement is missing from both plugins
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.
@perrotta Only LogDebug was used originally. I added a few more LogDebug and used EDM_ML_DEBUG for the output to be easier to see. I can change them all to either one if that is preferred.
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 think that having one single method to report debug logs can be less confusing, and the one stated in the MessageLogger are typically recommendedin CMSSW instead of cout's (which aren't thread safe, in case you want to use them in a multithread environment). I won't be strict on it, though, and I just wanted to point it out to you.
In any case, if you stick on LogDebug,
please add the missing header includes
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.
done
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31776/19038
|
please test |
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, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
hi Silvio, I'm not against a backport, but to make use of these changes we would need to generate new MC RAW data... |
Right, the fix is in DigiToRaw, not RawToDigi ! |
I don't see the need for this to be backported as this variable (FED trailer fragmentLength) isn't used in RawToDigi process. |
PR description:
PR validation:
if this PR is a backport please specify the original PR and why you need to backport that PR: