| |
| META TOPICPARENT |
name="PeterWinterAnalysis" |
-- PeterWinter - 22 Sep 2008 |
| |
Overall checks / improvements
- Overshoot at ./mu level not recorded! Needs a flag added to the TFadcPulse class
|
|
<
< |
- Overall mapping quite okay, but know misidentification for too close pulses due to large coincidence window. Example picture is in this eLog. Some pulses are also simply not recognized.
|
>
> |
- 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.
|
| |
- 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?
|
| |
Threshold / gain analysis
- Machinery should work, FADC shrub should allow to systematically look at the
|
Copyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.