-
Notifications
You must be signed in to change notification settings - Fork 53
Femcal update #855
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
base: main
Are you sure you want to change the base?
Femcal update #855
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
…om compact xml file
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have a question about segmentation. I think, we should make it into a consistent bit field for both implementations.
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