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

Tof new geom #796

Merged
merged 39 commits into from
Oct 20, 2024
Merged

Tof new geom #796

merged 39 commits into from
Oct 20, 2024

Conversation

ssedd1123
Copy link
Contributor

@ssedd1123 ssedd1123 commented Oct 12, 2024

Briefly, what does this PR introduce?

Endcap TOF geometry modified to match the newest technical drawings from https://indico.bnl.gov/event/24949/attachments/57520/98759/ePICTOF_WP2_FTOFLayout_09272024v2.pdf.

The current epic geometry has each ETOF module located separately. But the newest drawing shows that a single power board house multiple modules together. This PR groups modules together according to the aforementioned drawing.

Furthermore, the current epic geometry shows that sensors are placed facing front and backing alternatively across rows. However, the latest drawing shows that ETOF are double sided on every row, but with sensors placed below the service hybrid on the front side, and above the service hybrid on the other side. Each module now contains 4 small sensors instead of one big sensor.

Here's the updated ETOF power board configuration,

image

Here's the design drawing,

image

Barrel TOF is also modified. Staves are broken into two so an engagement ring can fit in the middle. LGAD is also located on both sides alternatively,

image

Cooling tubes are also incorporated into the staves,

image

Latest technical drawing shows that sensor width is half of what was previously proposed. Sensors right next to the central engagement ring are only half sized,

image

What kind of change does this PR introduce?

  • Bug fix (issue #__)
  • New feature (issue #__)
  • Documentation update
  • [ x] Other: BTOF and ETOF geometry modified according to new technical drawing

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

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

No

Does this PR change default behavior?

BTOF ETOF geometries are changed.

ssedd1123 and others added 28 commits August 3, 2024 04:50
…kerWithFrame_geo.cpp, but it is modified to accommodate multile sensors with dead spaces.
Co-authored-by: Dmitry Kalinkin <dmitry.kalinkin@gmail.com>
…ere are only half a sensor around the support ring. Geometries of BTOF is modified to match the technical drawing as close as possible.
… for the two halfs of BTOF. This eliminate the acts error: Layers are overlapping. I have no idea why the error disappears, but if it make the ACTS god happy, so be it.
@github-actions github-actions bot added topic: barrel Mid-rapidity detectors topic: forward Positive-rapidity detectors (hadron-going side) labels Oct 12, 2024
@github-actions github-actions bot added the topic: PID Particle identification label Oct 12, 2024
@veprbl veprbl changed the title Tof new gemo Tof new geom Oct 12, 2024
@veprbl veprbl added this to the 24.11.0 milestone Oct 15, 2024
veprbl
veprbl previously approved these changes Oct 17, 2024
Copy link
Member

@veprbl veprbl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great. Tracking benchmarks still look good.

src/EndcapTOF_geo.cpp Outdated Show resolved Hide resolved
compact/tracking/tof_endcap.xml Outdated Show resolved Hide resolved
Co-authored-by: Dmitry Kalinkin <dmitry.kalinkin@gmail.com>
@ssedd1123
Copy link
Contributor Author

@veprbl bench:backwards_ecal exceeded the 2 hours limit and thus eicweb/eic_container failes. I check the logs and the snake jobs are progressing slowly until the very end so it's not like it's getting stuck in a loop. It seems strange to me that my modifications to TOF would have any significant effects on backward ecal. Do you have any idea what's going on?

@ssedd1123 ssedd1123 added this pull request to the merge queue Oct 19, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Oct 19, 2024
@veprbl veprbl added this pull request to the merge queue Oct 19, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Oct 19, 2024
@ssedd1123
Copy link
Contributor Author

@veprbl Unfortunately I don't think this issue is solved. I looked at other jobs in the merge queue and snakemake is still spawning hundreds of jobs on bench:backwards_ecal.

@veprbl
Copy link
Member

veprbl commented Oct 20, 2024

@veprbl Unfortunately I don't think this issue is solved. I looked at other jobs in the merge queue and snakemake is still spawning hundreds of jobs on bench:backwards_ecal.

Right, back to a drawing board.

@ssedd1123 ssedd1123 added this pull request to the merge queue Oct 20, 2024
Merged via the queue into main with commit 7d595ab Oct 20, 2024
115 checks passed
@ssedd1123 ssedd1123 deleted the tof_new_gemo branch October 20, 2024 19:08
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: forward Positive-rapidity detectors (hadron-going side) topic: PID Particle identification
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants