Skip to content
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

fix: update tracker support and services cones per project CAD info #661

Merged
merged 21 commits into from
Apr 29, 2024

Conversation

wdconinc
Copy link
Contributor

@wdconinc wdconinc commented Mar 11, 2024

Briefly, what does this PR introduce?

This PR adds the outer support/services cone and places the cones and barrels in their actual intended positions. I'm marking this as a bugfix since the placement was completely wrong (with tracks in some regions going through two support cylinders...).

TODO:

What kind of change does this PR introduce?

  • Bug fix (issue #__)
  • New feature (issue #__)
  • Documentation update
  • Other: __

Please check if this PR fulfills the following:

  • Tests for the changes have been added
  • Documentation has been added / updated
  • Changes have been communicated to collaborators @sly2j

Does this PR introduce breaking changes? What changes might users need to make to their code?

No.

Does this PR change default behavior?

Yes, it adds the project's estimate of the equivalent aluminum thickness of the services.

@wdconinc
Copy link
Contributor Author

@wdconinc
Copy link
Contributor Author

Overlaps:
image

=== Overlaps for Default ===
 = Overlap ov00000: world_volume/InnerTrackerSupport_assembly_13/TrackerSupportCylEndcapN2C_14 overlapping world_volume/EcalEndcapN_21/EcalEndcapN_envelope_0 ovlp=1.2488
 = Overlap ov00001: world_volume/InnerTrackerSupport_assembly_13/TrackerSupportCylEndcapN2C_14 overlapping world_volume/EcalEndcapN_21/ring12_1 ovlp=1.2488
 = Overlap ov00002: world_volume/InnerTrackerSupport_assembly_13/TrackerSupportDiskEndcapP_20 overlapping world_volume/DIRC_14/DIRCModule_2/Envelope_box_vol_0 ovlp=0.960703
 = Overlap ov00003: world_volume/InnerTrackerSupport_assembly_13/TrackerSupportDiskEndcapP_20 overlapping world_volume/DIRC_14/DIRCModule_10/Envelope_box_vol_0 ovlp=0.960703
 = Overlap ov00004: world_volume/InnerTrackerSupport_assembly_13/TrackerSupportDiskEndcapP_20 overlapping world_volume/DIRC_14/DIRCModule_6/Envelope_box_vol_0 ovlp=0.960703
 = Overlap ov00005: world_volume/InnerMPGDBarrelSubAssembly_8/InnerMPGDBarrel_0/InnerMPGDBarrel_layer1_0 overlapping world_volume/InnerTrackerSupport_assembly_13/OuterSupportConeEndcapN_10 ovlp=0.883848
 = Overlap ov00006: world_volume/MiddleSiTrackerSubAssembly_5/SagittaSiBarrel_0/SagittaSiBarrel_layer1_0 overlapping world_volume/InnerTrackerSupport_assembly_13/InnerSupportConeEndcapN_2 ovlp=0.671716
 = Overlap ov00007: world_volume/OuterSiTrackerSubAssembly_6/OuterSiBarrel_0/OuterSiBarrel_layer1_0 overlapping world_volume/InnerTrackerSupport_assembly_13/InnerSupportConeEndcapN_2 ovlp=0.636361
 = Overlap ov00008: world_volume/InnerTrackerSupport_assembly_13/TrackerSupportDiskEndcapP_20 overlapping world_volume/DIRC_14/DIRCModule_5/Envelope_box_vol_0 ovlp=0.487628
 = Overlap ov00009: world_volume/InnerTrackerSupport_assembly_13/TrackerSupportDiskEndcapP_20 overlapping world_volume/DIRC_14/DIRCModule_3/Envelope_box_vol_0 ovlp=0.487628
 = Overlap ov00010: world_volume/InnerTrackerSupport_assembly_13/TrackerSupportDiskEndcapP_20 overlapping world_volume/DIRC_14/DIRCModule_9/Envelope_box_vol_0 ovlp=0.487628
 = Overlap ov00011: world_volume/InnerTrackerSupport_assembly_13/TrackerSupportDiskEndcapP_20 overlapping world_volume/DIRC_14/DIRCModule_1/Envelope_box_vol_0 ovlp=0.487628
 = Overlap ov00012: world_volume/InnerTrackerSupport_assembly_13/TrackerSupportDiskEndcapP_20 overlapping world_volume/DIRC_14/DIRCModule_11/Envelope_box_vol_0 ovlp=0.487628
 = Overlap ov00013: world_volume/MiddleSiTrackerSubAssembly_5/SagittaSiBarrel_0/SagittaSiBarrel_layer1_0 overlapping world_volume/InnerTrackerSupport_assembly_13/InnerSupportConeEndcapP_3 ovlp=0.414088
 = Overlap ov00014: world_volume/InnerTrackerSupport_assembly_13/TrackerSupportDiskEndcapP_20 overlapping world_volume/DIRC_14/DIRCModule_0/Envelope_box_vol_0 ovlp=0.27
 = Overlap ov00015: world_volume/InnerTrackerSupport_assembly_13/TrackerSupportDiskEndcapP_20 overlapping world_volume/DIRC_14/DIRCModule_4/Envelope_box_vol_0 ovlp=0.27

@wdconinc
Copy link
Contributor Author

wdconinc commented Mar 12, 2024

Analysis and todo of overlaps:

  • = Overlap ov00000: world_volume/InnerTrackerSupport_assembly_13/TrackerSupportCylEndcapN2C_14 overlapping world_volume/EcalEndcapN_21/EcalEndcapN_envelope_0 ovlp=1.2488
    = Overlap ov00001: world_volume/InnerTrackerSupport_assembly_13/TrackerSupportCylEndcapN2C_14 overlapping world_volume/EcalEndcapN_21/ring12_1 ovlp=1.2488
    EcalEndcapN is 12-sided (inscribed circle with radius 65 cm), and only smallest radius fits in cylindrical support cylinder.
    • check whether EcalEndcapN is indeed up to 65 cm, since detector parameter table says 63 cm
    • check with Roland whether this is intended as cylindrical or at that point is 12-sided around EcalEndcapN
  • = Overlap ov00004: world_volume/InnerTrackerSupport_assembly_13/TrackerSupportDiskEndcapP_20 overlapping world_volume/DIRC_14/DIRCModule_6/Envelope_box_vol_0 ovlp=0.960703
    EndcapP services/support disk (180.8 to 183.4 cm) overlaps with DIRC (which can go up to 185 cm)
    • check with Roland on assumptions for services/support disk placement
  • = Overlap ov00005: world_volume/InnerMPGDBarrelSubAssembly_8/InnerMPGDBarrel_0/InnerMPGDBarrel_layer1_0 overlapping world_volume/InnerTrackerSupport_assembly_13/OuterSupportConeEndcapN_10 ovlp=0.883848
    Inner MPGD Barrel overlaps with services at the equivalent thickness specified
    • check with Roland on how this fits without interference: Inner MPGD Barrel has moved outwards in radius
  • = Overlap ov00006: world_volume/MiddleSiTrackerSubAssembly_5/SagittaSiBarrel_0/SagittaSiBarrel_layer1_0 overlapping world_volume/InnerTrackerSupport_assembly_13/InnerSupportConeEndcapN_2 ovlp=0.671716
    = Overlap ov00013: world_volume/MiddleSiTrackerSubAssembly_5/SagittaSiBarrel_0/SagittaSiBarrel_layer1_0 overlapping world_volume/InnerTrackerSupport_assembly_13/InnerSupportConeEndcapP_3 ovlp=0.414088
    Sagitta Si Barrel overlaps with services at the equivalent thickness specified
    • check with Roland on how this fits without interference
  • = Overlap ov00007: world_volume/OuterSiTrackerSubAssembly_6/OuterSiBarrel_0/OuterSiBarrel_layer1_0 overlapping world_volume/InnerTrackerSupport_assembly_13/InnerSupportConeEndcapN_2 ovlp=0.636361
    Outer Si Barrel overlaps with services at the equivalent thickness specified
    • check with Roland on how this fits without interference

@wdconinc wdconinc force-pushed the services_effective_aluminum_thickness branch from b6f993a to 1bcb9d7 Compare March 12, 2024 17:49
@wdconinc
Copy link
Contributor Author

Overlap between services/support cylinder (rmin = 65 cm, rmax = rmin + 26 mm) and EcalEndcapN (rmax = 65 cm but because of 12-sided nature this only avoids interference at the center of each side, not at the corners).
image

@veprbl
Copy link
Member

veprbl commented Mar 12, 2024

Overlap between services/support cylinder (rmin = 65 cm, rmax = rmin + 26 mm) and EcalEndcapN (rmax = 65 cm but because of 12-sided nature this only avoids interference at the center of each side, not at the corners).

This part of services is important for us. I suppose, it should somehow change the shape from round to dodecadon. Should we request additional details from the project on that?

@wdconinc
Copy link
Contributor Author

Should we request additional details from the project on that?

We should get some more details later this week.

@wdconinc wdconinc force-pushed the services_effective_aluminum_thickness branch from 0fadd72 to 356c7ad Compare March 14, 2024 14:50
@wdconinc
Copy link
Contributor Author

Updated CAD at https://cad.onshape.com/documents/c0ed227baac48c145c49cf1e/w/d0907e24cd4dc810e5d737d3/e/7bbf426811fe41884a26ab05

Drawing:
image

@veprbl
Copy link
Member

veprbl commented Mar 16, 2024

One question about the last drawing: the 8.2 mm thickness is just the mechanical support itself, so we would still need the density estimates and routing in CAD for cabling?

@wdconinc
Copy link
Contributor Author

The thickness is equivalent aluminum thickness based on total number and diameter of cables. So it doesn't need a lower density. In reality it will be thicker and a stacked bundle with a lower average density.

@veprbl
Copy link
Member

veprbl commented Mar 16, 2024

The thickness is equivalent aluminum thickness based on total number and diameter of cables. So it doesn't need a lower density. In reality it will be thicker and a stacked bundle with a lower average density.

Should be copper? Also, we don't need to prepare special, "effective" geometry. It would be fine to have a conductor volume from the regular CAD design to which we then assign a proportion of conductor/isolator/air to the material?

@wdconinc
Copy link
Contributor Author

The effective model is all there is. There is no routing that we can import. The CAD figures above are all there is that has somewhat correct effective material volume. A previous version was outlines/max extents only.

@wdconinc
Copy link
Contributor Author

Looks like this now:
image

@wdconinc wdconinc force-pushed the services_effective_aluminum_thickness branch from e04e4e9 to 83b3034 Compare March 18, 2024 21:10
@ShujieL
Copy link
Contributor

ShujieL commented Mar 21, 2024

Please email me once this and other relevant geometry updates are merged, I will then update the material map. Thanks!

@wdconinc wdconinc mentioned this pull request Mar 21, 2024
7 tasks
@wdconinc wdconinc force-pushed the services_effective_aluminum_thickness branch 3 times, most recently from 6d10958 to 936a028 Compare March 27, 2024 21:12
@wdconinc wdconinc added this to the 24.04.0 milestone Mar 27, 2024
@veprbl
Copy link
Member

veprbl commented Apr 1, 2024

I did some studies on effect at the negative rapidity for this PR https://indico.bnl.gov/event/22883/contributions/89707/attachments/53617/91737/eeemcal_update.pdf
It's not too bad.

@wdconinc wdconinc force-pushed the services_effective_aluminum_thickness branch 2 times, most recently from 47b3fbd to ec64f62 Compare April 5, 2024 12:40
@veprbl veprbl modified the milestones: 24.04.0, 24.05.0 Apr 8, 2024
@wdconinc
Copy link
Contributor Author

wdconinc commented Apr 8, 2024

The current routing of the services long the DRICH looks something like this, in section view:

image

  • the slope in the DRICH vessel is not as steep as the service routing seems to imply,
  • the "snout" slope in the DRICH vessel is also mismatched with the service routing.

@github-actions github-actions bot added the topic: forward Positive-rapidity detectors (hadron-going side) label Apr 8, 2024
@wdconinc wdconinc force-pushed the services_effective_aluminum_thickness branch from 65f19f8 to d382b24 Compare April 9, 2024 02:51
@wdconinc wdconinc marked this pull request as ready for review April 16, 2024 18:52
@wdconinc wdconinc requested a review from veprbl April 16, 2024 18:54
@github-actions github-actions bot added topic: barrel Mid-rapidity detectors topic: calorimetry labels Apr 26, 2024
@wdconinc wdconinc added this pull request to the merge queue Apr 29, 2024
Merged via the queue into main with commit 81162e0 Apr 29, 2024
109 checks passed
@wdconinc wdconinc deleted the services_effective_aluminum_thickness branch April 29, 2024 03:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: barrel Mid-rapidity detectors topic: calorimetry topic: forward Positive-rapidity detectors (hadron-going side) topic: PID Particle identification topic: tracking
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants