-
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
PFRecHitTopologyESProducer may access and invalid SoA index #44789
Comments
type pf |
assign heterogeneous |
cms-bot internal usage |
A new Issue was created by @fwyzard. @Dr15Jones, @rappoccio, @sextonkennedy, @antoniovilela, @smuzaffar, @makortel can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
@jsamudio @fllor @hatakeyamak while looking into this, I noticed a realised there is a minor inconsistency in the code:
Is it intended ? In either case, could you introduce a named constant to identify invalid dense ids, instead of using Thank you ! |
You are right. A denseId should always be a @jsamudio @hatakeyamak Since I do not have access to the CMS infrastructure anymore, could one of you do the commit?
cmssw/RecoParticleFlow/PFRecHitProducer/plugins/alpaka/PFRecHitProducerKernel.dev.cc Line 158 in 3fb8b0e
For the named constant, just do cmssw/RecoParticleFlow/PFRecHitProducer/plugins/alpaka/PFRecHitProducerKernel.dev.cc Line 33 in 3fb8b0e
This should probably be left unchanged. Also introduce the constant here:
This will then also solve #44608 |
I am currently traveling, but will tackle this once I reach my destination. |
Enabling range checks shows that
PFRecHitTopologyESProducer
may access and invalid SoA index:The text was updated successfully, but these errors were encountered: