Detector Parameters Update: Hadron Endcap HCal

[Chao1009]

A series of smaller issues from #552
det: new value from 2023/09/27 parameter table
sim: current simulation value as of 2023/10/11
template_var: from which we extract the sim value in compact files. Empty means we do not know.
stat: Correct, Missing, or Mismatched

Please implement the new detector parameters, and try to fill in the template_var for the Missing ones if you think it's important for future simulation/design comparison.

Here is the detailed report for this detector subsystem:

HADRON DIRECTION END CAP, Hadron Calorimeter, : 
                           det    sim       template_var        stat
Length (cm)              140.0  140.0  {{LFHCAL_length}}     Correct
Inner Radius (cm)         17.5    0.0                  0  Mismatched
Outer Radius (cm)        267.0  270.0    {{LFHCAL_rmax}}  Mismatched
Offset from Center (cm)  359.6    NaN              Empty     Missing
Physical Start (cm)      359.6  363.2    {{LFHCAL_zmin}}  Mismatched
Physical End (cm)        499.6  503.2    {{LFHCAL_zmax}}  Mismatched

[rymilton]

Hi, the hadron endcap HCal is not my detector. I am the liaison for the insert (which is not in the detector parameters spreadsheet for some reason). The ORNL folks are leading the HCal/LFHCAL.

[Chao1009]

Hi @FriederikeBock, would you plan to verify and update the related detector parameters in the simulation? Please let us know if you have any questions or need help.

[FriederikeBock]

@Chao1009 I'm not so sure how to help here.

    <constant name="LFHCAL_zmin"          value="EcalEndcapP_zmin + EcalEndcapP_length"/>
    <comment> LFHCAL is 140 cm total, but current implementation leaves the final 10 cm empty </comment>
    <constant name="LFHCAL_length"        value="140.0*cm"/>
    <constant name="LFHCAL_zmax"          value="LFHCAL_zmin + LFHCAL_length"/>

z min and max are defined via other detector parameters. So it seems someone is going beyond their allotted volume ahead of the LFHCal.
A similar thing applies for the outer radius.

 <constant name="LFHCAL_rmax"          value="HcalBarrel_rmax"/>

Even if it should not affect us entirely, as our detector is not defined as a disc but rather as single placement of 8M modules. That's why I also didn't define an inner radius, as I can't.

Not sure whether this is really helpful.
Regards,
Fredi

[kkauder]

@Chao1009 @FriederikeBock , I chased it down to ForwardServiceGap_length which is 13.6 cm in definitions.xml but 9.6 cm in the table. I'll make a PR, this should affect all forward detectors so maybe best to run the report again after merging.