12-Sector-CyMBaL

[ybedfer]

Briefly, what does this PR introduce? Please link to any relevant presentations or discussions.

New version of MPGD plugin and digitization compatible w/ upcoming 12-Sector-CyMBaL (see "https://github.com/eic/epic/tree/12-Sector-CyMBaL").

What is the urgency of this PR?

• [ *] Medium

What kind of change does this PR introduce?

• [* ] New feature (no related issue ever created)

Please check if any of the following apply

None.

[veprbl]

As usual, we will need the PR for epic geometry as well. And as before, I would really appreciate any help with reviewing this.

I assume this is backwards compatible? Or we just rely on the fact that strip geometry is not used in the production?

[ybedfer]

This is the first one of a series of PRs meant to commit a 12-sector version of CyMBaL.

It's brought into play only if the epic_craterlake_tracking_2DStrip configuration is processed. => Default behavior of eicrecon is not affected.

When epic_craterlake_tracking_2DStrip is processed, it's backward compatible. But obviously requires a new version of epic, w/ modified XML and detector builders for CyMBaL (i.e. MPGDBarrelHits) for the new features to be activated.
It then requires a version of DD4hep >= #f7904caf, i.e. :
"DetectorSensitives: assign sensitive detector to reflected object if the logical volume was sensitive".

Then it does two things:

• Update MPGDTrackerDigi, to get it to understand the segmentation scheme of the new CyMBaL.
• Update the MPGD plugin, to include new configuration parameters.

Below a plot illustrating backward compatibility: it's SimHit and RecHit-SimHit residual distributions, obtained w/ an 8-Sector CyMBaL:

Note that I have not been able to run the hit-matching macro: it crashes, first upon encountering TOF RecHits, then elsewhere if TOF is bypassed.

[veprbl]

Note that I have been able to run the hit-matching macro: it crashes, first upon encountering TOF RecHits, then elsewhere if TOF is bypassed.

This reminds me of a known regression from three weeks ago that should be fixed on current main via #2745. Have you tested with most up to date version of your branch?

[github-actions]

⚠️ Clang-Tidy found issue(s) with the introduced code (1/2)

[github-actions]

⚠️ Clang-Tidy found issue(s) with the introduced code (2/2)

[github-actions]

⚠️ Clang-Tidy found issue(s) with the introduced code (1/1)

[github-actions]

Capybara summary for PR 2829

• rec_dis_10x100_minQ2=0_craterlake_10x100_MT (Δ: 420)
• rec_dis_10x100_minQ2=1000_craterlake_tracking_2DStrip (Δ: 0)
• rec_dis_10x100_minQ2=1000_craterlake_tracking_only (Δ: 0)
• rec_dis_10x130_minQ2=1_craterlake_10x130 (Δ: 0)
• rec_dis_10x250_minQ2=1_craterlake_10x250 (Δ: 0)
• rec_dis_18x275_minQ2=0_craterlake_18x275 (Δ: 0)
• rec_dis_18x275_minQ2=0_craterlake_18x275_MT (Δ: 363)
• rec_dis_18x275_minQ2=0_craterlake_18x275_ST_MT (Δ: 355)
• rec_dis_18x275_minQ2=1000_craterlake_18x275 (Δ: 0)
• rec_dis_18x275_minQ2=1000_craterlake_18x275_MT (Δ: 476)
• rec_dis_18x275_minQ2=1000_craterlake_18x275_ST_MT (Δ: 475)
• rec_dis_5x41_minQ2=0_craterlake_5x41 (Δ: 0)
• rec_e_1GeV_20GeV_craterlake (Δ: 0)
• rec_pi_1GeV_20GeV_craterlake (Δ: 2)
• two_stage_raw_e_1GeV_20GeV_craterlake (Δ: 0)
• two_stage_rec_e_1GeV_20GeV_craterlake (Δ: 0)

Last updated 2026-08-05T12:39-04:00 d41b283

[ybedfer]

Hello,

Note that I have been able to run the hit-matching macro: it crashes, first upon encountering TOF RecHits, then elsewhere if TOF is bypassed.

This reminds me of a known regression from three weeks ago that should be fixed on current main via #2745. Have you tested with most up to date version of your branch?

Everything was up-to-date.
I tried again. => Same outcome: No TOF RecHit, and bypassing TOF does not help: something is stored in the "CentralCKFTracks" collection that I cannot identify since macro crashes as soon as I try to access its cellID.

(I managed to find a work around the absence of TOF RecHit, see PR "eic/epic#1146" of epic.)

[ybedfer]

To ease the task of the reviewers, here is a breakdown of the modifications to the source code:

TWO files, mainly, are concerned:

I) "MPGDTrackerDigi": THREE sets of modifications:
i) Method "parseSegmentation":

• Extend the set of valid segmentation schemes to include 12SCyMBaL.
• In order to not duplicate source code lines, I created a lambda function
  for setting "StripParameters", viz.: "getGridPhiZParams".

ii) DeadZone:

• Its handled by new member method "isInActive".
• Conditioning the generation of clusters.
• Conditioned by a new config. parameter: "hasDeadZone".

iii) Fulfilling requests from github actions, like "gsl::at", avoid casting
array into pointer, and, so-called, readability improvements.

II) MPGD plugin: configuration parameters:
i) "stripResolutions": set from an XML <constant>.
ii) "hasDeadZone": false by default, set =true for CyMBaL.