Aidan Kelleher
Oct. 1, 2008


Last Week:

1) After discussion with Jon and Seamus, switched to Seamus' method of 
   background subtraction

2) Seamus' method estimates background neutral/charge ratio and uses a shift 
   in TOF to get background counts.

3) Re-analyzed kin 4 (nearly complete -- 79 active jobs and 12 pending as of 
   14:00).  Request from computer center: recheck farm jobs for memory 
   requirements: "It looks like your jobs use less than 250MB of memory 
   although you are requesting 500MB.  This unnecessarily starves out other 
   jobs on the farm nodes to reserve the memory for your request that isn't 
   actually used."

3) Helped my roommate move out

Note: no missing mass cut (might not be correct, also, not correctly inlcuded 
in background selection)

Summary of Asymmetry
Total number of neutral events: 139384
Total neutral events -- background subtracted: 128331
Total number of neutral events, helicity +: 69513
Total number of neutral events, helicity -: 69871
Raw Asymmetry : -0.0506371
Background Subracted Asymmetry: -0.0547101 +/- 0.00344928 (sub) 
	   +/- 0.0027873 (stat) (5.09467% -- stat 8.106% combined)
Number of Runs analyzed: 132
Nitrogen dilution factor: 0.943 <-- Seamus's Thesis
Target polarization: 0.48 
Beam polarization: 0.835 <-- Seamsus's Thesis
Proton leakage factor: 0.834 <-- Seamus's Thesis
A_phys = -0.20182

To Do:

1) Re-check missing mass (used to look good, it looks...not as good) (see m_miss_W_bad.pdf) -- effect of missing mass can be seen in m_miss_effect.pdf
   UPDATE -- missing mass strange behavior is due to how missing mass is 
   calculated. Adding a cut on time of flight procudes: m_miss_W.pdf -- which 
   looks great.
2) Re-run code on newly analyzed runs
3) Nitrogen Dilution
4) Kin 2a target polarization into database
5) Investigate variations Z/A ratio from MC using different resolution for 
   charged and uncharged.