[Near] [Far]

[Home] [Linearity] [Drift] [Gains] [S2S]

Near Detector Strip to Strip Calibration page


List of Bad Strips (History)
Summary of Constants (History)
Previous Plots of calibration constants (History)



Relevant Data Set Information Strips That Give me issues
It should be noted that only the strips which do not pass a minimum hit cut are not included in my calculation of the detector response.
Bad Strips are classified in 5 ways(and may be classified "bad" more than once because it fails more than one classification.)
ConvergeFailure These Strips failed to converge to a particular light level
LowStripHits These Strips have a really low hit Count (<50 hits/strip)
HighStripHits These Strips have a really High hit Count (>2 sigma more hits)
ColdStrip Strips have a response significantly lower than the average (<5%)
HotStrip Strips have a response significantly higher than the average(>2.5x)
The Table below is organized in the following manner
plane | strip | mean for strip | Average for Detector | Crate/Master/Minder


Problematic Strip Plot
Here we plot the rate at which we identify bad strips. An indication that something has gone terribly wrong would be that one of these error rates would spike.


Strip Response Information
Since our calibration is now normalized such that the mean calibration constant is constant, it does not make sense to plot this value to look for issues. However, the plots below could pick up potential problems
Row 1: plots 1 and 2; Picks out the strip with the largest response.
This may be an indication of LI or some other high E problem
Row 2: plots 1 and 2: Picks out the strip with the highest # of hits
Noisy channels may get picked up alot and cause reco errors
Row 3: plots 1 and 2:
Plots Average response and average calibration constants
Probably less sensitive to channel-by-channel problems
Row 4: plots 1 Plotting the average width of the detector response
Again, not really sensitive to single channel problems.