|
META TOPICPARENT |
name="PeterWinterAnalysis" |
-- PeterWinter - 22 Sep 2008 |
|
- Overshoot at ./mu level not recorded! Needs a flag added to the TFadcPulse class
- Overall mapping quite okay. But
- known misidentification for too close pulses due to large coincidence window. Example picture is in my logbook 1, p.142. Got fixed
|
|
< < |
-
- some pulses are also simply not recognized at the pulse finding level.
|
> > |
-
- some pulses are also simply not recognized at the pulse finding level. Is only fixable at ./mu level.
- close by pulses are not separated by the pulse finder (see eLog:112
). Needs fix at ./mu level.
|
|
- Fractional pixel space information is available but not used right now. Could maybe allow to reduce the time coincidence window for the mapping between FADC and TDC400 information?
|
|
< < |
- How to handle the induced undershoots? How do they influence signal on neighbouring wires?
|
> > |
- How to handle the induced undershoots? How do they influence signal on neighbouring wires? (see eLog:113
)
|
|
Threshold / gain analysis |
|
< < |
- Machinery should work, FADC shrub should allow to systematically look at the
|
> > |
- Machinery should work (eLog:99
), FADC shrub should allow to systematically look at the
|
|
-
- gain - optimal energy / stop anode energy
- threshold - energy spectra for all green, blue or red pixels
|
|
< < |
- Runs need to be combined to compromise between enough statistics and studying the time evolution of these parameters
|
> > |
- Runs need to be combined to compromise between enough statistics and studying the time evolution of these parameters. Unfortunately, the current analyzed run 11 mu- runs have VERY low FADC statistics (a handful of events per run instead of ~5000 expected triggers), because the data is simply corrupt.
|
|
- Align gain for each run (subset of combined runs).
- Do we have to select a certain angle range only (i.e. mainly horizontal muons)?
|