-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Consumers of Event and Run numbers are not using the proper type #47288
Comments
cms-bot internal usage |
A new Issue was created by @vlimant. @Dr15Jones, @antoniovilela, @makortel, @mandrenguyen, @rappoccio, @sextonkennedy, @smuzaffar can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign EventFilter/ESDigiToRaw (to start with, please assign further) |
The ECAL packer seems to have this issue as well, although it does not seem to lead to zero digis when unpacking as for the ES. |
+daq |
This issue is fully signed and ready to be closed. |
I don't think we can close this issue just yet though |
-daq |
@smuzaffar @makortel So I did a bit of poking around. The standard says the compiler can do integer conversion (e.g. assign the value of an |
@Dr15Jones , I have opened cms-sw/cmsdist#9678 to see how many and where we get such conversions |
Here is the previous episode in |
The ECAL packer issue is addressed in #47295 . This one is not as critical as the ES one since not the full event number is used for the packing and the packed bits are not affected. |
enabling |
@smuzaffar Is there an easy way to get the list of unique warnings? |
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2cad9b/44269/warnings-unique.txt contains the unique warnings |
In many places, some code is extracting the event and run numbers and using it with "random" C++ type instead of using the types defined in
https://github.com/cms-sw/cmssw/blob/master/DataFormats/Provenance/interface/RunLumiEventNumber.h
It actually causes major trouble when the event number goes beyond the casting type (see preshower issue under https://indico.cern.ch/event/1503577/#2-egm-pog-data-vs-mc-compariso).
The text was updated successfully, but these errors were encountered: