Difference between revisions of "BCAL Reconstruction Issues"
From GlueXWiki
| Line 4: | Line 4: | ||
#** TDC timing resolution is too good | #** TDC timing resolution is too good | ||
#** single photo-electron peaks in energy spectrum | #** single photo-electron peaks in energy spectrum | ||
| − | #* spikes in time histogram at low energy | + | #** spikes in time histogram at low energy |
| − | + | ||
| − | + | ||
#* Very low energy ADC hits coming from mcsmear | #* Very low energy ADC hits coming from mcsmear | ||
| − | #* | + | #* Bulk attenuation length vs short and long components (get atten length from ccdb) |
# Timewalk corrections | # Timewalk corrections | ||
#* Establish procedure for doing these corrections based on simulated data (how closely should this match the correction procedure for real data?) | #* Establish procedure for doing these corrections based on simulated data (how closely should this match the correction procedure for real data?) | ||
| Line 20: | Line 18: | ||
#* Use only timing information from fADCs? | #* Use only timing information from fADCs? | ||
#** If we use TDC info also, we need to appropriately make use of the different timing errors of different hits | #** If we use TDC info also, we need to appropriately make use of the different timing errors of different hits | ||
| − | |||
#* Determining cluster properties (E, x, y, z, t) | #* Determining cluster properties (E, x, y, z, t) | ||
#* How to average cell-by-cell position to get cluster position | #* How to average cell-by-cell position to get cluster position | ||
| Line 30: | Line 27: | ||
#** Need extra special treatment of ends of calorimeter? | #** Need extra special treatment of ends of calorimeter? | ||
#* How to determine errors (and correlations) on cluster properties (important for kinematic fitting) | #* How to determine errors (and correlations) on cluster properties (important for kinematic fitting) | ||
| − | # Matching with tracks | + | # Matching with tracks: get update from Simon/Paul |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Revision as of 15:44, 13 January 2015
- Simulation (mcsmear)
- fADC timing: Resolution is too poor
- mcsmear doesn't seem to smear data enough
- TDC timing resolution is too good
- single photo-electron peaks in energy spectrum
- spikes in time histogram at low energy
- Very low energy ADC hits coming from mcsmear
- Bulk attenuation length vs short and long components (get atten length from ccdb)
- Timewalk corrections
- Establish procedure for doing these corrections based on simulated data (how closely should this match the correction procedure for real data?)
- Determine form of timewalk corrections
- What if we have TDC info only on one end?
- DBCALPoint (reconstructing E,z,t from double-ended hit)
- When determining energy, give more weight to higher energy hit? (also in averaging time?)
- Best way to determine sigma_z?
- How to deal with multiple hits in same channel?
- Clustering
- Use only timing information from fADCs?
- If we use TDC info also, we need to appropriately make use of the different timing errors of different hits
- Determining cluster properties (E, x, y, z, t)
- How to average cell-by-cell position to get cluster position
- Weight averages by...? E? E^2? 1/sigma^2?
- Average rectangular coordinates? Cylindrical? Spherical?
- Energy corrections (z-dependent, non-linear)
- Is current scheme good enough?
- If so, write a plugin to automate this process.
- Need extra special treatment of ends of calorimeter?
- How to determine errors (and correlations) on cluster properties (important for kinematic fitting)
- Use only timing information from fADCs?
- Matching with tracks: get update from Simon/Paul
