Detector Parameters Update: Hadron Endcap HCal about epic HOT 4 CLOSED

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.

from epic.

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.

from epic.

@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

from epic.

@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.

from epic.