The purpose of the luminosity scans is to i) measure the density reduction due to localized beam heating in the target, and ii) verify that the computer and detector efficiencies are correct by using a Carbon target as a control.

To Do:
1st priority: Implement tracking upgrades and replay 3rd luminosity scan. Don't neglect the SOS. Resolve any problems with WC tracking efficiency and computer deadtime.
2nd priority: Reanalyze the 1st luminosity scan.
3rd priority: Analyze the 2nd luminosity scan.
Finally, put the measured luminosity coefficient (%/100 microA) in the analyzer.

1st luminosity scan during FpiII run: Run List
These runs have been analyzed without any tracking code upgrades.
HMS analysis: The Carbon has a small but significant slope, Hydrogen a larger slope, and Deuterium larger still. The slopes are suspiciously well-correlated with the rates. (Plots can be found at the links or at the bottom of this page.)
SOS analysis: Too few electron events for a meaningful analysis (ie, 1%-2% statistical errors). Good statistics for pi-, but results were too weird to log. Need to revisit this later.
Carbon Results (HMS)
Hydrogen and Deuterium Results (HMS)

2nd luminosity scan during FpiII run: Run List
In this luminosity scan the Carbon was run at more than twice the rate of the first luminosity scan. Unfortunately, these runs had less than half the statistics of the 1st scan, so may not be very useful. These runs have been copied to /work/hallc/fpi2-data/ but have not yet been analyzed.

3rd luminosity scan during FpiII run: Run List
Carbon only! High statistics for both HMS and SOS. I believe the Carbon rates were even higher than in the 2nd luminosity scan. A scan of computer deadtime at fixed high beam current was included.