update of TRK and FT3 services, to better match with Corrado's scheme#15392
Merged
Conversation
njacazio
approved these changes
May 12, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Update on TRK services for the peacock layout, to better correspond to the engineering drawings:
FT3 disks with staves:
cutStavesOnNominalRadius_outerset totrue: this reduces the sensitive area of ML disks, but allows to avoid overlaps with surrounding services:Was:
We will need to see how to increase the sensitive area of the ML disks (namely, to which extend we can violate the 35 cm constraint on disk rMax, without colliding with ML services).
Geometry was checked with the following command:
Remaining overlaps: