Difference between revisions of "BCAL Reconstruction Issues"
From GlueXWiki
| Line 13: | Line 13: | ||
** Determine form of timewalk corrections | ** Determine form of timewalk corrections | ||
** What if we have TDC info only on one end? | ** 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? | ||
* Clustering | * Clustering | ||
** Use only timing information from fADCs? | ** Use only timing information from fADCs? | ||
Revision as of 17:57, 28 March 2013
- Simulation (mcsmear)
- fADC timing
- Uses threshold crossing time rather than FPGA-ish algorithm
- 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
- max ADC amplitude (12 bits?)
- Sampling fluctuations not applied on per-particle basis
- fADC timing
- 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?
- Clustering
- Use only timing information from fADCs?
