-
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
Stateless clusterizer for SiStrip #12307
Conversation
A new Pull Request was created by @VinInn (Vincenzo Innocente) for CMSSW_8_0_X. Stateless clusterizer for SiStrip It involves the following packages: RecoLocalTracker/SiStripClusterizer @cmsbuild, @cvuosalo, @slava77 can you please review it and eventually sign? Thanks. |
@cmsbuild please test |
The tests are being triggered in jenkins. |
something went wrong in the merge... |
tested (with debug on) for step2 of 134.91 |
@cmsbuild please test |
1 similar comment
@cmsbuild please test |
The tests are being triggered in jenkins. |
float noise(const uint16_t& strip) const { return SiStripNoises::getNoise( strip, noiseRange ); } | ||
float gain(const uint16_t& strip) const { return SiStripGain::getStripGain( strip, gainRange ); } | ||
bool bad(const uint16_t& strip) const { return qualityHandle->IsStripBad( qualityRange, strip ); } | ||
// uint32_t currentId() const {return detId;} |
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.
this can be removed, unless needed for some imminent developments
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 for noticing.
I will remove it next round (when integrating ThreadSafe DetSetVector)
I disagree. I need this to continue making HLT thread safe. |
float gain(const uint16_t& strip) const { return SiStripGain::getStripGain( strip, gainRange ); } | ||
bool bad(const uint16_t& strip) const { return qualityHandle->IsStripBad( qualityRange, strip ); } | ||
// uint32_t currentId() const {return detId;} | ||
Det setDetId(const uint32_t) const; |
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.
Maybe findDetId
might be a less confusing name? A const
set function usually sets off my warning bells. In this case nothing is actually set.
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.
not anymore at least!
thanks for all other suggestions as well.
Based on my cursory overview, it seems pretty good to me beyond the few comments I had. |
@slava77 - given the state of the strip unpacker PR, I think we can move ahead with this and eventually put the unpacker in 80x once its fully checked out for HI (and for old data) |
There are several comments from Chris which need a follow up (or a notice that they will be fixed in the next PR as happened to my comments). |
I think that @Dr15Jones will be satisfied that his comments get adressed in the next PR that will also |
fine with me |
+1
@boudoul @forthommel please note this PR with changes overlapping with the strip unpacker updates: some extra care may be needed to merge the strip unpacker updates into 80X, it's better to have a separate PR for that, once the issues with the unpacker DQM are sorted out. |
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_0_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar |
+1 |
Stateless clusterizer for SiStrip
make SiStrip clusterizer stateless to support multi-thread on demand.
This is required before making the container itself Thread Safe.
Purely technical changes, tested extensively long ago.
Results should be bit-identical to previous version