This repository has been archived by the owner on Sep 4, 2024. It is now read-only.
38 incident hadron beamline #39
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…974/contributions/51260/ . Still need to locate where the sizes are described and probably more up to date locations
wdconinc
reviewed
Oct 12, 2022
wdconinc
reviewed
Oct 12, 2022
wdconinc
approved these changes
Oct 12, 2022
7 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Briefly, what does this PR introduce?
An optional extension to the incoming hadron beamline to check for overlaps with other far backwards region detectors. Generally this might be commented out for running the simulation as it should have no effect.
The beamline and magnet sizes will need to be updated as currently they are small place holders with positions based off the files linked here:
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?
Does this PR change default behavior?
There is no change to the behaviour