- stevens4's home page
- Posts
- 2014
- 2013
- 2012
- 2011
- December (1)
- November (2)
- October (1)
- September (1)
- August (2)
- July (3)
- June (7)
- May (2)
- April (2)
- March (5)
- February (2)
- January (2)
- 2010
- November (1)
- October (1)
- September (3)
- August (3)
- July (3)
- June (1)
- May (1)
- April (3)
- March (4)
- February (4)
- January (8)
- 2009
- December (4)
- November (3)
- October (4)
- September (5)
- August (1)
- July (2)
- June (2)
- April (1)
- March (1)
- February (2)
- January (1)
- 2008
- My blog
- Post new blog entry
- All blogs
W-Background Estimation based on Run 9 pp500 data
I'm using Jan's Algo ver 4.1 with a few modifications to look into the idea Scott suggested of sorting events by placing conditions on the away side to get an estimate of the background. Here is a list of the cuts used:
CUTS ver 4.1 algo params: trigID: bht3=230531 L2W=230601 BHT_Dsm>28 isMC=0
TPC: nPileupVert>3, vertex |Z|<100.0cm, globEleTrack: nFit>15, hitFrac>0.51 Rin<90.0cm, Rout>170.0cm, PT>10.0GeV/c
BTOW ADC: kSigPed=3 maxAdc>200 clustET>15.0 GeV ET2x2/ET4x4>0.9 ET2x2/nearJetET>0.8
dist(track-clust)<7.0cm,
W selection highET>30.0 awayTotET<8.0GeV
I relaxed a couple of the cuts from Jan's analysis:
ET2x2/ET4x4>0.9 ET2x2/nearJetET>0.8
We probably get a few more W's and a lot more background, but you can still see a bit of a peak in the lower right of Fig 1 (where no away side requirements are in place)
Figure 1: 2x2 Cluster ET distributions for different away side conditions (conditions shown in title)
I think it is encouraging that when we see something "jet-like" (more than 2 tracks and some reasonable energy) on the away side the Jacobian peak essentially disappears.
Figure 2: Since the upper left and lower left have about the same y-scale I plotted them on top of each other here, no normalization is applied.
- stevens4's blog
- Login or register to post comments