Draft: [DQM] Support Tileboard Display

MR Description

This MR aims to support the tilboard display on the DQM GUI.

• For FNAL cassette tests:
  • Chooses L44 tileboard section of (u,v) = (3,0) as the representative polygon at the layer-level plot
  • Tunes margins and applies ad-hoc translation on the x-coordinate of the tileboard for better visualization
• For TB2025 data visualization:
  • Updates TL-L44 tileboard geometry root file (set the center of the shape at origin)

Figure 1: Cassette-level map of a fixed-ADC run in FNAL setup	Figure 2: Layer-level map of FNAL setup. The polygon is specified from module locator [1]; it is one of the five boards in the sector of iv=0. It would be good to display the full sector.

Observation

Currently, a single SiPM sector [1][2] represents multiple tileboards (e.g., the five polygons in the red box in Figure 1). Since the harvester can only calculate positions using polygons from [3], the sector's center can't be automatically positioned. As a temporary solution, we applied an ad-hoc translation as a workaround.

Technical note

• Layer-level map:
  • Modules in individual polygons based on [3]
  • Scope is determined from the module position with hard-coded margins
• Cassette-level map:
  • Cells are translated according to the module position
  • Scope is determined in the same way, but specific to modules in the same cassette

Relevant files

• [1] Configuration/data/ModuleMaps/modulelocator_FNALv4.txt
• [2] DQM/data/geometry_TL_L44_tileboard.root
• [3] DQM/data/geometry_v16.5.root

Figure 1: HGCAL layer 44 derived from `geometry_v16.5.root` (red box highlights modules 0 and 36).	Figure 2: Overview of TL L44 tileboard, where the blue box corresponds to the part used in TB2025.

To-Do List

• Eliminate translation for SiPM channels.
• A more generic way to determine the scope of the tileboard (e.g., through DQM JSON data)
• Support both TB2025 and FNAL setups through typecode in module locator (related MR: https://gitlab.cern.ch/hgcal-dpg/calibrations/-/merge_requests/6)
• Check the implementation does not affect other geometry
• Consider handling map scope in the cases of rotation

To discuss

• Display tileboards properly in the layer-level maps
  • Use 10-degree sector for display (Pro: simpler with an area subject to one ECON-D; Con: losing fine granularity)
    • Update layer-level geometry root file with each 10-degree sector represented by a single polygon
  • Use five tile modules (Pro: fine granularity; Con: need to handle rows in module locator)