-
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
HBHEGPU: added taggedBadByDb by ChannelQuality in GPU [12_0_X] #35355
HBHEGPU: added taggedBadByDb by ChannelQuality in GPU [12_0_X] #35355
Conversation
A new Pull Request was created by @mariadalfonso for CMSSW_12_0_X. It involves the following packages:
@malbouis, @yuanchao, @cmsbuild, @jpata, @slava77, @ggovi, @francescobrivio, @tvami can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
enable gpu |
@mariadalfonso is there a specific relval wf that tests this? |
11634.522 this is TTbar_14TeV , 2021 , HCALOnlyGPU |
test parameters:
|
@cmsbuild , please test |
@mariadalfonso Thank you, Maria. |
|
||
cms::cuda::ESProduct<Product> product_; | ||
#endif // __CUDACC__ | ||
}; |
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.
Sorry for the (maybe) naive question, but should this object be COND_SERIALIZABLE
?
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.
@mariadalfonso @fwyzard please have a look at this comment
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.
CondFormats/HcalObjects/interface/HcalChannelQuality.h is already COND_SERIALIZABLE
HcalChannelQualityGPU.h is not, but usually include the main .h
This is a common pattern for all conditions if need to do this change should be done in synch for all ECAL/HCAL/TRK ... and outside of this PR
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.
Indeed, I don't think these conditions need to be declared COND_SERIALIZABLE
.
They are never persisted or read from the database - they are only transient conditions, derived from the persistent ones and "repackaged" for use on GPUs.
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.
ok thanks for the explanation @mariadalfonso and @fwyzard, makes sense!
-1 Failed Tests: RelVals RelValsGPU Comparison SummarySummary:
|
@mariadalfonso would have been better to start with the master, or at least wait with the second PR until tests and review finishes.
|
Not sure why, I tested locally 11634.522 (GPU ) and compared with 11634.521 (CPU) locally is discoverable like this: runTheMatrix.py -w gpu -l 11634.522 Traceback (most recent call last): |
please ask @fwyzard |
Yes. |
I think you need to enable the |
I thought I did that here: #35355 (comment) |
I think the matrix should be told to use the gpu part of it. |
test parameters:
|
@cmsbuild , please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-4950a8/19215/summary.html GPU Comparison SummarySummary:
Comparison SummarySummary:
|
+alca
|
+db |
+hlt |
+reconstruction
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
This PR add a functionality to the Mahi on GPU that take into account the HcalChannelQuality to resynch with what is done on CPU
On CPU the rechit is dropped, while for the GPU energy is set to 0.
Tested on Run3 MC, and disable the ieta=18, depth1. (Those channel are present only at DIGI, but the fiber is not connected to the scintillator, so energy is not meaningful.)
Help in solving some differences observed between the Run3 HLT menu
backport of #35357
@fwyzard @abdoulline @silviodonato