Conversation
for more information, see https://pre-commit.ci
|
Auto check uses craterlake for overlap checks. Do I change craterlake (and all other craterlake_*)? |
Yes, please update all configurations to use your new xml. |
veprbl
left a comment
There was a problem hiding this comment.
I have some preliminary comments.
This comment was marked as resolved.
This comment was marked as resolved.
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
|
I think the overlap is now gone. 2 pending checks after 1/2 day. Anything else? |
|
I have no idea what those 2 failed check are : nvidia-smi & sim:zdc_lyso |
for more information, see https://pre-commit.ci
veprbl
left a comment
There was a problem hiding this comment.
Have a question about segmentation. I think, we should make it into a consistent bit field for both implementations.
|
Confimed that removing fake segmantation runs ok. Not sure what I saw 1/2 year ago. I tested it repeatedly. Anyway thanks for all those changes. |
### Briefly, what does this PR introduce? Following Forward EM calorimeter geometry update: eic/epic#855 this provides switch between Homogeneous and ScFi geometry implementations based on xml file loaded - For Homogenous, we keep energy smearing as is. SF=1.0 - For ScFi, hits from fibers are summed to a tower and no enrgy smearing applied. SF=0.03. - Remove active insert which won't be built Added an option to put SiPM saturation to CalorimeterHitDigi - Specify 2 new parameters : totalPixel and nPhotonPerGeV - default for totalPixel is 0, which case no attenuation is applied - For FEMC for both geometry models, SiPM saturation is ON by default - Use "-PFEMC:SiPMSaturation=OFF" to turn it off See following links for some more details: https://www.star.bnl.gov/~akio/epic/geometry/index.html https://www.star.bnl.gov/~akio/epic/reco/index.html https://www.star.bnl.gov/~akio/epic/hadron/index.html ### What kind of change does this PR introduce? - [ ] Bug fix (issue #__) - [x] New feature (issue #__) - [ ] Documentation update - [ ] Other: __ ### Please check if this PR fulfills the following: - [ ] Tests for the changes have been added - [ ] Documentation has been added / updated - [ ] Changes have been communicated to collaborators ### Does this PR introduce breaking changes? What changes might users need to make to their code? I don't think so, unless one provides wrong config xml file (until sum check in place) ### Does this PR change default behavior? It does apply SiPM attenuation by default for FEMC (but not other calorimeters). --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Dmitry Kalinkin <dmitry.kalinkin@gmail.com> Co-authored-by: Wouter Deconinck <wdconinc@gmail.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
Some benchmark plots from https://eicweb.phy.anl.gov/EIC/benchmarks/detector_benchmarks/-/pipelines/132524
|
| pv = trow_vol.placeVolume( | ||
| tower_vol, | ||
| Transform3D(RotationZYX(0, 0, 0), Position((tc - 1.5) * blocksize / 4, 0, 0))); | ||
| pv.addPhysVolID("tower_x", tc); |
There was a problem hiding this comment.
I thought you changed this to "x". Same for "y" above? @veprbl
### Briefly, what does this PR introduce? This is a hotfix for #855 (comment) (we should probably run a benchmark on scfi version) ### What kind of change does this PR introduce? - [ ] Bug fix (issue #__) - [ ] New feature (issue #__) - [ ] Documentation update - [ ] Other: __ ### Please check if this PR fulfills the following: - [ ] Tests for the changes have been added - [ ] Documentation has been added / updated - [ ] Changes have been communicated to collaborators ### Does this PR introduce breaking changes? What changes might users need to make to their code? No ### Does this PR change default behavior? Yes





Briefly, what does this PR introduce?
New Forward EM calorimeter geometry with current design. There are 2 models, homogeneous and Wpowder+ScFi.
Also removes active insert, which won't be built.
See following links for some more details:
https://www.star.bnl.gov/~akio/epic/geometry/index.html
https://www.star.bnl.gov/~akio/epic/reco/index.html
https://www.star.bnl.gov/~akio/epic/hadron/index.html
What kind of change does this PR introduce?
Please check if this PR fulfills the following:
Does this PR introduce breaking changes? What changes might users need to make to their code?
See also PR for EICrecon for digitization change
eic/EICrecon#1848
Does this PR change default behavior?
Not until default configuration files start to use new geometry