You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 64
Next »
General Info
- Tuesdays at 11:00 (JLab time)
- Room B101 at JLab
- Bluejeans
- Confluence
ECAL Calibration Tasks
- Alignment
- based on survey
- based on tracking
- Energy
- FEE
- absolute
- dedicated FEE runs and singles triggers
- Møllers and WABs
- absolute
- 4.4 GeV and positron trigger should greatly reduce their statistics/usefulness
- singles and old-pair triggers may help
- Cosmics
- relative, before and after the run
- LED
- relative, before and during the run
- Edge corrections
- based on tracks' y-intercept at ECAL relative to ECAL y-edge
- Time
- channel offsets
- time-walk
- RF
- signal shape is different relative to 2016
- potentially more important for positron/singles triggers than for pairs
HODO Calibration Tasks
- Gains
- Gains were calculated during the run, several time throughout the run
- We have observed gain variation as a function of the Luminosity, and a tiny dependence as a function of time
- For production runs, a single run from every day (few days) can be used to calculate gains
- For low Lumin runs, a single run can be used for each Luminosity
- About 15-20 file will be needed
- Format? Either hpstr/DST with hodo information should be available, or I have a simple ntuple that gives necessary information
- TIme
- I am not sure how hodo timing can be improved, signal shapes need to be investigated (Is there a significant need to improve it?)
- At this moment the hit time is defined as a threshold crossing time
- Alignment
- Hodo acceptance is covering all the ECal/SVT acceptance, Efficiency studies during the run didn't show any efficiency loss close to edges of the calorimeter.
Meeting Agendas/Minutes
October 1, 2019