Moved BTOF forward by 2.5 cm. #965
Open
+4
−4
Conversation
This file contains hidden or 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
rahmans1
approved these changes
Oct 16, 2025
rahmans1
force-pushed
the
pr/move_BTOF_forward
branch
from
9373777 to
101de1d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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?
I was approached by Rahman to verify that BTOF and FTOF are located inside the designated envelope: https://indico.bnl.gov/event/29963/contributions/114155/attachments/65038/111684/EPIC%20Envelope%20-%2009-22-2025.pdf
Although FTOF is fine, BTOF protrudes from one side by 2.5 cm outside of the envelope,
The easiest fix is to move the entire BTOF assembly forward by 2.5 cm.
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?
No