Difference: FadcStatusSept08 (4 vs. 5)

Revision 52008-09-23 - PeterWinter

Line: 1 to 1
 
META TOPICPARENT name="PeterWinterAnalysis"
-- PeterWinter - 22 Sep 2008
Line: 6 to 6
 

Overall checks / improvements

  • Overshoot at ./mu level not recorded! Needs a flag added to the TFadcPulse class
Changed:
<
<
  • 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 DONE
    • 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?
Added:
>
>
  • 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
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback