-
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
HGCal Reco Geometry #12170
HGCal Reco Geometry #12170
Conversation
ianna
commented
Oct 29, 2015
- Allocate vectors at geometry constructor initialisation
- Avoid resizing big vectors
- Implement sorting of valid DetIds. Apply it if needed?
There was no point to have it static anyway.
Make them members in Vx3DHLTAnalyzer. Please test before accepting.
* HGCal geometry writer * Configuration files to write and read HGCal geometry * Test HGCal geometry from DB * HGCal DB geometry builder * Allow to drop Ecal subdetectors from Calo geometry DB builder
…sizing big vectors.
A new Pull Request was created by @ianna (Ianna Osborne) for CMSSW_8_0_X. HGCal Reco Geometry It involves the following packages: Geometry/HGCalGeometry @cmsbuild, @civanch, @Dr15Jones, @ianna, @mdhildreth can you please review it and eventually sign? Thanks. |
@lgray and @bsunanda - before I commit DB payloads code for HGCal, it seems some tiding up is needed. I'm not sure if you rely on sorted DetIds. I've provided a simple sort by rawId, more complex one can be implemented if needed. Also, FlatTrd breaks CaloCellGeometry polymorphism. The test asserts when Debug mode is enabled. I'm not going to fix it since @bsunanda is planning to move to another shape. Please comment. |
@cmsbuild please test |
@@ -114,6 +114,8 @@ HGCalGeometry* HGCalGeometryLoader::build (const HGCalTopology& topology) { | |||
} | |||
} | |||
} | |||
// FIXME: Sort valid DetIds if neded | |||
// geom->sortDetIds(); |
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.
@lgray - here is a logical place to sort valid DetIds if needed.
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.
@ianna better to just go ahead and sort them. It shouldn't have any adverse effect and can only help in the future.
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.
@lgray - I'm a bit concerned about sorting 5 million element vector for "just in case" - as it's n*log2(n). What is current/future access pattern? Do you check every hit DetId on its validity? Mind the search is linear.
The tests are being triggered in jenkins. |
…h incorrect 16 samples flag reporting
…nHcalCalibAlgos Replace LinkDef file witl XML selection file in Calibration/HcalCalibAlgos
Static beam 80x
The tests are being triggered in jenkins. |
Pull request #12170 was updated. @cmsbuild, @civanch, @Dr15Jones, @ianna, @mdhildreth can you please check and sign again. |
+1 |
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 |
Conflicts: Geometry/HGCalGeometry/interface/HGCalGeometry.h Geometry/HGCalGeometry/src/HGCalGeometry.cc
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 |
if (counter != numberOfCells) { | ||
std::cerr << "inconsistent # of cells: expected " << numberOfCells << " , inited " << counter << std::endl; | ||
assert( counter == numberOfCells ) ; | ||
} | ||
std::cout << "HGCalGeometryBuilder-> " << counter << " cells are produced" << std::endl; | ||
std::cout << "HGCalGeometryBuilder-> " << counter << " cells are produced\n"; |
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.
@ianna - could you remove this printout. Thanks
@davidlange6 - could you, please, revert this merge? I've merged this branch with another and wrongly pushed the result into this one. Sorry. (I wonder why the labels were not reset...) |