Difference between revisions of "BCAL Reconstruction Issues"
From GlueXWiki
(8 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | * | + | # '''BDT Work''' |
− | * | + | #* Implement truth information; improve rejection of and understand origin of 'bad clusters' |
− | + | # '''Simulation (mcsmear)''' | |
− | + | #* fADC timing: Resolution is too poor | |
− | ** | + | #* mcsmear doesn't seem to smear data enough |
− | + | #** TDC timing resolution is too good | |
− | ** spikes in time histogram at low energy | + | #** 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) | |
− | * | + | # '''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? | |
− | * Determining cluster properties (E, x, y, z, t) | + | #** 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) | |
− | + | # '''Matching with tracks:''' get update from Simon/Paul | |
− | + | # '''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? | |
− | + | ||
− | + | ||
− | + | ||
− | * | + | |
− | + | ||
− | ** | + |
Latest revision as of 15:47, 13 January 2015
- BDT Work
- Implement truth information; improve rejection of and understand origin of 'bad clusters'
- 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)
- 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
- 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?