Difference: FadcStatusSept08 (7 vs. 8)

Revision 82011-04-21 - PeterWinter

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

Physics / analysis topics:

Overall checks / improvements

  • 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 DONE
    • 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? (see eLog:113)

Threshold / gain analysis

  • 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. 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)?

Capture energy spectrum

  • Cuts on capture events might need to be changed? (Side note: Can we actually centralize this cut for all analysis modules that do this (CaptureAnalysis, FADC, ...)? Maybe a general function that determines if a muon has a capture: IsCaptureEvent(TMuStop *muon)?)

Charged particle emission after capture

  • Principle candidates are easy to be found: PDF document
  • Characterization (length, energy loss etc.) needs work, Steve's latest ./mu development code would be usefule here. Not possible in current FADC shrub since no inclusion of these events (only muon2->IsSpot() at this time)

PK comments

 \ No newline at end of file
Added:
>
>
Please go to https://muon.npl.washington.edu/twiki/bin/view/Main/FadcStatusSept08
 \ No newline at end of file
 
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