Difference between revisions of "SoLID Ecal Weekly 20230608"

Revision as of 12:29, 9 June 2023

Mike on tracking:
- looks like back/forward tracking can be added to level0 tree but then it needs to be passed onto level 1

Spencer update on TS3 study, suggestion:
- for data: use individual shower calibrated by MIP, not showersum directly
- for data, run 4680 had SC-A.and.SC-D and SC-A did not work well, should try the newer run
- for sim, separate the 4 particle types and weigh each by the cross-section.

Darren/Zhiwen is working with Kishan on AI/ML
- How does AI/ML PID compare with classical PID for beam test sim?
- How well does the trained ML PID work for beam test data?
High-Level Question to be answered by our study:
- Is AI/ML PID complimentary to classical method (thus assist classical method), or superior?

Update on prescale in data:
- (Jixie, W. Gu): CODA3.0 uses power(2,n-1)+1, so n=6 means 33 and for every 33 events, 1 is recorded.

Presentation by Mike: Tracking_With_Target_Cut
- track back projected to beamline (figure shows in direction perpendicular to 18-deg line, i.e. something like "ytar") shows wide distribution and an offset of target center that is larger than possible in reality (even accounting for pointing of our setup).
- Suspect this is due to GEM chamber position not perfectly known. Note that optimization won't give us the correct alignment, as Xinzhan has shown.
- If we include Jimmy's measurement, things could improve
- Once Xinzhan comes back, focus will be to correct efficiency. Forward-projection to detectors should still be okay, and there is no way we can get the correct y (or z)-targ without survey of GEMs anyways.

with the PS understood, we now have very good agreement in ECal ShowerSum spectrum between different runs (different PS, trigger setup, and threshold). All should be within 15% of the simulation
the end point of electron sim has a sharp drop off but the data show slower drop off. Not sure what is causing the difference, anything missing in the simulation? The comparison used Run 4780. Points to check:
- How much is pileup?
- simulation threshold should account for Shower block normalization (different scaling factor)
- Is the shashlyk length accurate?
- The MIP calibration is accurate to what level?
- Peak-finding for individual shower block may not result in a soft-ware sum the same as the peak-finding of the hardware sum directly.

Spencer studied TS3 from SC-C.and.SC-D.and.ShowerSum runs -- SC-C, SC-D, and ShowerSum spectra need some study
Darren showed AI/ML on ECal and Cherenkov: SULI_Week1_Slides
- For Cherenkov we need to add position cut

anything else (all)

@@ Line 18: / Line 18: @@
 ==Discussion on Cooking with Updated Tracking==
-*Presentation by Mike:
+*Presentation by Mike: [https://solid.jlab.org/wiki/index.php/File:Tracking_6_08_23.pdf Tracking_With_Target_Cut]
-**
+**track back projected to beamline (figure shows in direction perpendicular to 18-deg line, i.e. something like "ytar") shows wide distribution and an offset of target center that is larger than possible in reality (even accounting for pointing of our setup).
+**Suspect this is due to GEM chamber position not perfectly known. Note that optimization won't give us the correct alignment, as Xinzhan has shown.
+**If we include Jimmy's measurement, things could improve
+**Once Xinzhan comes back, focus will be to correct efficiency.  Forward-projection to detectors should still be okay, and there is no way we can get the correct y (or z)-targ without survey of GEMs anyways.
 ==Discussion on Cooking with Edge-Finding==