Repository navigation
Conversation
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
…:eic/epic into Add-dipole-steering-magnets-based-on-CAD
…w-far-backwards-geoemtry
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
Could be. Perhaps we can use another geometry configuration to generate prim files. cc @wdconinc |
Just change it to central only, maybe? But "hideous boolean volume has too many nested layers" can be a problem in its own right... regardless of whether dawn is what barfs on it first. |
|
Agreed with @wdconinc, but I think it's also fair to say, despite how much of a technical marvel dawn is, we are not looking to support it indefinitely. So I would not sink time into debugging geometries for it when you can descope. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Thanks, I've temporarily removed it while I debug other issues. |
|
Looks like the Is there a safer approach would stop this happening again? |
|
(Was resolved in eic/detector_benchmarks#269) We don't run extra nightly to conserve CI resource. |
|
Is onnxruntime not available for python 3.13? Or am I missing something? From looking in the containers repository it appeared the requirements for the job might already be in the container? |
|
Maybe you need to update version constraints in the requirements.txt? |
…s followed by subtractions
for more information, see https://pre-commit.ci
…c into Setup-new-far-backwards-geoemtry
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
Capybara summary for PR 1004
Material map validation
|


Briefly, what does this PR introduce?
Makes the changes required to match the current EIC accelerator beamline setup in the Far Backward region. The vacuum pipe spanning the tagger drift volume has needed some significant revisions, simplifying the implementation but removing some functionality to allow the "antechamber" design.
Incorporates the volumes reviewed in #978, placed correctly.
Introduces a new script which automatically updates the xml description of the magnets, strengths and positions based on a provided twiss and survey file. (The current files have been added to the calibrations but could be removed as don't do anything other than act as an input to the script.)
Some extra tinkering of positions may be required. In particular the luminosity pipe along the z-axis doesn't extend into the B2AeR magnet. There is a small vacuum/air boundary between the tagger exit windows and the beampipe cylinder. These could be fixed in this PR or a future PR as they won't have the most significant impacts.
The Luminosity components will need their positions updated to match the new layout.
Not the cleanest PR.
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?
Hopefully nothing.
Does this PR change default behavior?
There is likely to be significant changes to the acceptance and reconstruction of the taggers.