-
Notifications
You must be signed in to change notification settings - Fork 45
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
Insert granularity #771
Insert granularity #771
Conversation
multisegmentation for the insert
for more information, see https://pre-commit.ci
syntax error corrected
add gap between left and right sides of the detector. This also allows separate segmentations on the left and right sides of the detector
for more information, see https://pre-commit.ci
updated documentation, also use 60 layers instead of 65
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
include "side" as an id field
for more information, see https://pre-commit.ci
Force Ecal insert to use "side" as a readout field, so that things don't crash.
fixed issue for subtraction volume.
refactoring the segmentation
…row and column numbers may need to be adjusted by integer offsets, and the margin between the LR edges of the detector and the corners of the hexagons have not been included yet
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.
Edited some documentation and requested clarification in some parts. Overall it looks good, assuming that the segmentation you introduced behaves as expected like the plots you've shown before.
Co-authored-by: Ryan Milton <87345122+rymilton@users.noreply.github.com>
Thanks for catching this Co-authored-by: Ryan Milton <87345122+rymilton@users.noreply.github.com>
Co-authored-by: Ryan Milton <87345122+rymilton@users.noreply.github.com>
Co-authored-by: Ryan Milton <87345122+rymilton@users.noreply.github.com>
included left_right_gap in the forward_insert.xml
use same left right gap for the forward ecal insert as for the hcal insert (for now).
updated the gap to match the value in the xml
thank! |
@rymilton Thanks for the feedback. If you are satisfied with my changes and responses, please approve. If you request futher changes, please let me know. Thanks |
Thanks these changes look good. One more thing is that with your branch, I'm seeing this error when using EICrecon: |
I was getting the same errors, and I found that the fix for it is adding "side" to the fields in the CalorimeterHitsMerger_factory in FHCAL.cc . I am fixing this in eic/EICrecon#1595
|
Alright, sounds good. I'll approve these changes then. |
…hold (#1595) ### Briefly, what does this PR introduce? Uses a larger threshold for the distance between the neighboring hits in the insert, due to the new cell size. Also include "side" field (ie, left vs right) in the hit merger algorithm ### What kind of change does this PR introduce? - [ ] Bug fix (issue #__) - [ ] New feature (issue #__) - [ ] Documentation update - [X] Other: change of parameters ### Please check if this PR fulfills the following: - [X] Tests for the changes have been added - [X] Documentation has been added / updated - [X] Changes have been communicated to collaborators ### Does this PR introduce breaking changes? What changes might users need to make to their code? Probably. Including the detector "side" as a field in the hit merger algorithm probably breaks the code if using a version of the epic repository from before pull request eic/epic#771 is merged. Therefore this pull request and eic/epic#771 should be merged at the same time as one another ### Does this PR change default behavior? yes. Changes the parameters of the topo clustering and also uses the "side" field in the hit merger. --------- 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>
multisegmentation for the insert
Briefly, what does this PR introduce?
Updates the segmentation for the insert so that it has 3 different segmentations:
~12cm2 in layers 1-16
~21 cm2 in layers 17-60 for the left side
~25 cm2 in layers 17-60 for the right side
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?
no
Does this PR change default behavior?
yes. different cell sizes in the calorimeter insert. Also a few minor changes: removed thinner front layer from the insert. Added gap between left and right sides. Adjusted the width and heights of the insert slightly.