120 likes | 225 Vues
This report by Peter Speckmayer details the recent findings and corrections related to the HCAL stack in the LCD framework. It discusses historical issues with layer numbering that affected simulations and how these were resolved. Additionally, it highlights a currently detected problem with the tracking region that exhibits similar symptoms but is unrelated to past bugs. Solutions implemented include reducing the tracking region depth and re-running simulations to ensure accuracy. The next steps involve reconstruction and neural network training to refine the HCAL performance.
E N D
Late shower start in HCAL stack Peter Speckmayer Peter Speckmayer, LCD weekly
Late shower start • History: • once upon a time... • we had a layer numbering problem. • HCAL stack layer number were reversed (first layerhighest number) • sometimes incorrect reversing of layer numbers • shortenes artificially the HCAL (some layers not taken into account) • has been fixed then • change in geometryconverter layers start with No. 0 Peter Speckmayer, LCD weekly
Late shower start 2 • Detected similar problem again • not related to old (and fixed) bug • but same symptoms Peter Speckmayer, LCD weekly
late start/ example Peter Speckmayer, LCD weekly
late start/ example Peter Speckmayer, LCD weekly
late start/ example Peter Speckmayer, LCD weekly
Tracking region • compact.xml: <!-- tracking region --> <constant name="tracking_region_radius" value="126.5*cm"/> <constant name="tracking_region_zmax" value="100.*cm"/> • Define layers of HCAL (material, thickness), define number of layers, define center of HCAL • HCAL center differs for different set ups • lcdd: <constant name="tracking_region_zmax" value="1000.0" /> <constant name="world_x" value="50000.0" /> <position name="HCAL_position" x="0.0" y="0.0" z="4000.0" unit="mm" /> <position name="HCAL_layerType0_slice0_position" x="0.0" y="0.0" z="-3.75" unit="mm" /> <position name="HCAL_layerType0_slice1_position" x="0.0" y="0.0" z="3.75" unit="mm" /> <position name="HCAL_layerType0_slice2_position" x="0.0" y="0.0" z="7.5" unit="mm" /> <position name="HCAL_layer0_position" x="0.0" y="0.0" z="-3491.25" unit="mm" /> • Tracking region reaches into Calorimeter • no calorimeter hits from impinging particle while in tracking region • but calorimeter hits from back-scattered particles Peter Speckmayer, LCD weekly
Tracking region • solution so far: • reduce tracking region to 1 cm in z • re-submitted all simulations with corrected tracking region • next step: reconstruction, creating ROOT-trees • then: training of neural net • this time: want to go down to 3 lambda (up to now: 6 lambda) • wait for detailed explanation about tracking region Peter Speckmayer, LCD weekly
After shortening of tracking region Peter Speckmayer, LCD weekly
Wrong/correct samples wrong (material, thickness) correct (material, thickness) W-steel 15, 10 Steel-W 15, 10 steel 30, 25, 15 W 05, 10, 15 • W-steel 20 • Steel-W 20 • Steel 20, 10 • W 20 Peter Speckmayer, LCD weekly
Summary • some HCAL stacks wrong • problem found • re-simulate ALL stacks (on the grid) • reconstruct down to 3 lambda Peter Speckmayer, LCD weekly