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.
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?
Threshold / gain analysis
Machinery should work, 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
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)