Difference between revisions of "TD Ddoverd 2010"
(Created page with '= 2/10/2010= {| border="1" |cellpadding="20" cellspacing="0 |- | root file || reaction || <math>Q^2</math> || W vs <math>Q^2</math> || <math>F_{cup}</math> || <math>X_b</mat…') |
|||
Line 549: | Line 549: | ||
[[File:ND3npaddlenumberwithnphecuts.gif|400px]]<br> | [[File:ND3npaddlenumberwithnphecuts.gif|400px]]<br> | ||
+ | |||
+ | [[DeltaDoverD_Progress]] |
Latest revision as of 18:20, 6 February 2011
2/10/2010
root file | reaction | W vs | # events for <1.232 | ||||
1 | B<0, pi^-=27 && e^-=11 | 9868 | |||||
2 | B>0, pi^+=27 && e^-=11 | 412 | |||||
3 | B>0, pi^+=27 && e^-=7 | 793 | |||||
4 | B>0, pi^-=7 && e^-=11 | 400 | |||||
5 | B<0, pi^+=7 && e-=11 | 9406 |
Rate differences
Which paddle do we expect the Pion to hit if we flip the direction of the B-Field?
Only using Certain Paddles
or
Looking at Ratio_3 and Ratio_4 one can make a conclusion that we are detecting ~ % more type hadrons.
Choosing events Below 1.232 GeV && Certain paddle numbers
22-02-2010
- NH3 Target, two file lists: NH3Bn.list (B<0, 26994-26983) && NH3Bp.list (B>0, 27074-27079)
no paddle cuts
- A.) B>0
1.) B>0,
&& , NH3Bp1_1.root2.) B>0,
&& , NH3Bp2_1.root- B.) B<0
1.) B<0,
&& , NH3Bn1_1.root2.) B<0,
&& , NH3Bn2_1.root
Paddle Cuts
Again, choosing events below 1.232 GeV, applying cuts, and plotting Histograms for certain electron and pion paddles.
_vs_ , , Fcup && .
- A.) B>0
1.) B>0,
&& , NH3Bp1.root2.) B>0,
&& , NH3Bp2.root- B.) B<0
1.) B<0,
&& , NH3Bn1.root2.) B<0,
&& , NH3Bn2.rootFile | W vs | |||
NH3Bp1.root | 200px | |||
NH3Bp2.root | 200px | |||
NH3Bn1.root | 200px | |||
NH3Bn2.root | 200px |
Now you need to cut on. The above suggests that looking at 1 < < 2 GeV/c^2 may be a good starting point.
The idea is to compare the outbending (B<0)
rate in paddle 27 to the inbending(B>0) rate in paddle 7 when 1 < < 2. For the same kinematics the rates should be the same because the reaction is the same. Do the same for to see if it is consistent. This will show much flipping the magnet polarity impacts the rate measurement. Are the differences due to the B-field change or the scintillator efficiency, or to the track reconstruction? Our goal is to argue that the detector has the same efficiency for detecting and in the same scintillator when the Torus B-field direction is flipped.1 < < 2
File | W vs | ||
NH3Bp1.root | 200px | ||
NH3Bp2.root | 200px | ||
NH3Bn1.root | 200px | ||
NH3Bn2.root | 200px |
bin | Bp1/Bn1 | Bp2/Bn2 |
0.1 | 2.38 | 0.2991.09 | 0.405
0.2 | 1.29 | 0.1883.59 | 0.215
0.3 | 1.38 | 0.2424.6 | 0.284
0.4 | 1.62 | 1.023.76 | 1.28
Angle vs Paddle Number Distribution
# | angle vs paddle number | angle vs paddle number |
B>0, | &&||
B>0, | &&||
B<0, | &&||
B<0, | &&
26/04/2010
NH3Bn positive pion runs
7.root - 27.root
pion paddle number | x_bj=0.1 | x_bj=0.2 | x_bj=0.3 | x_bj=0.4 |
1 | 10 | 3.1638 | 6.1620 | 4.472 | 1.4
2 | 14 | 3.760 | 7.728 | 5.30 |
3 | 20 | 4.593 | 9.648 | 6.93 | 1.7
4 | 26 | 5.187 | 9.353 | 7.35 | 2.2
5 | 24 | 4.994 | 9.742 | 6.56 | 2.4
6 | 30 | 5.5125 | 1.179 | 8.97 | 2.6
8 | 16 | 4102 | 1065 | 8.14 | 2
9 | 19 | 4.396 | 9.848 | 6.93 | 1.7
10 | 23 | 4.898 | 9.957 | 7.52 | 1.4
11 | 16 | 471 | 8.438 | 6.22 | 1.4
12 | 20 | 4.585 | 9.253 | 7.36 | 2.5
13 | 13 | 3.673 | 8.542 | 6.55 | 2.2
14 | 19 | 4.375 | 8.738 | 6.23 | 1.7
15 | 15 | 3.962 | 7.925 | 52 | 1.4
16 | 22 | 4.758 | 7.642 | 6.50 |
17 | 5 | 2.240 | 6.323 | 4.84 | 2
18 | 10 | 3.233 | 5.718 | 4.22 | 1.4
19 | 7 | 2.627 | 5.221 | 4.51 | 1
20 | 3 | 1.734 | 5.813 | 3.60 |
21 | 3 | 1.716 | 49 | 30 |
22 | 2 | 1.410 | 3.22 | 1.40 |
23 | 0 | 2 | 1.43 | 1.71 | 1
24 | 0 | 1 | 11 | 10 |
NH3Bp positive pion runs
#p.root
pion paddle number | x_bj=0.1 | x_bj=0.2 | x_bj=0.3 | x_bj=0.4 |
4 | 21 | 4.615 | 3.92 | |
5 | 39 | 58 | 18 | |
6 | 56 | 91 | 49 | |
7 | 90 | 110 | 82 | 5 |
8 | 81 | 155 | 78 | 3 |
9 | 68 | 8.1139 | 1285 | 9.24 | 2
10 | 83 | 9.1181 | 1388 | 9.48 | 2.8
11 | 102 | 10164 | 1396 | 9.88 | 2.8
12 | 103 | 10.1188 | 13.7122 | 118 | 2.8
13 | 85 | 9.2203 | 14.2132 | 11.516 | 4
14 | 105 | 10.2219 | 14.8120 | 10.911 | 3.3
15 | 116 | 10.8192 | 13.8113 | 10.68 | 2.8
16 | 91 | 9.5208 | 14.4134 | 11.69 | 3
17 | 98 | 9.9187 | 13.7112 | 10.69 | 3
18 | 106 | 10.3159 | 12.6121 | 117 | 2.6
19 | 91 | 9.5166 | 12.9107 | 10.39 | 3
20 | 83 | 9.1138 | 11.790 | 9.57 | 2.6
21 | 81 | 9167 | 12.9110 | 10.511 | 3.3
22 | 87 | 9.3164 | 12.884 | 9.25 | 2.2
23 | 77 | 8.898 | 9.973 | 8.56 | 2.4
24 | 86 | 9.3131 | 11.481 | 96 | 2.4
25 | 96 | 9.8185 | 13.692 | 9.614 | 3.7
26 | 87 | 9.3147 | 12.197 | 9.88 | 2.8
27 | 72 | 8.5132 | 11.582 | 9.16 | 2.4
28 | 64 | 8131 | 11.473 | 8.510 | 3.2
29 | 46 | 6.9101 | 1053 | 7.52 | 1
30 | 13 | 3.514 | 3.818 | 4.81 | 1
06-02-2010
Electron Efficiency
Chosen electron paddles are following for the positive and negative paddles respectively: 7 and 11.
electroneffbp.root && electroneffbn.root
B>0
TH1.Print Name = Qsqrd, Entries= 323638, Total sum= 323634 fSumw[0]=0, x=-0.2 fSumw[1]=0, x=-0.1 fSumw[2]=0, x=9.71039e-18 fSumw[3]=0, x=0.1 fSumw[4]=3, x=0.2 fSumw[5]=21, x=0.3 fSumw[6]=93, x=0.4 fSumw[7]=285, x=0.5 fSumw[8]=575, x=0.6 fSumw[9]=1148, x=0.7 fSumw[10]=2478, x=0.8 fSumw[11]=9402, x=0.9 fSumw[12]=24380, x=1 fSumw[13]=31648, x=1.1 fSumw[14]=29967, x=1.2 fSumw[15]=27864, x=1.3 fSumw[16]=27157, x=1.4 fSumw[17]=26820, x=1.5 fSumw[18]=25603, x=1.6 fSumw[19]=25027, x=1.7 fSumw[20]=24470, x=1.8 fSumw[21]=23512, x=1.9 fSumw[22]=20320, x=2 fSumw[23]=13453, x=2.1 fSumw[24]=6738, x=2.2 fSumw[25]=2043, x=2.3 fSumw[26]=449, x=2.4 fSumw[27]=119, x=2.5 fSumw[28]=41, x=2.6 fSumw[29]=13, x=2.7 fSumw[30]=5, x=2.8 fSumw[31]=4, x=2.9
B<0
TH1.Print Name = Qsqrd, Entries= 716018, Total sum= 716011
fSumw[0]=0, x=-0.2 fSumw[1]=0, x=-0.1 fSumw[2]=180, x=9.71039e-18 fSumw[3]=112762, x=0.1 fSumw[4]=160348, x=0.2 fSumw[5]=91665, x=0.3 fSumw[6]=62692, x=0.4 fSumw[7]=46135, x=0.5 fSumw[8]=35169, x=0.6 fSumw[9]=28473, x=0.7 fSumw[10]=23810, x=0.8 fSumw[11]=20763, x=0.9 fSumw[12]=18452, x=1 fSumw[13]=16021, x=1.1 fSumw[14]=14494, x=1.2 fSumw[15]=12731, x=1.3 fSumw[16]=11610, x=1.4 fSumw[17]=10422, x=1.5 fSumw[18]=9437, x=1.6 fSumw[19]=8929, x=1.7 fSumw[20]=8149, x=1.8 fSumw[21]=7504, x=1.9 fSumw[22]=6209, x=2 fSumw[23]=4557, x=2.1 fSumw[24]=2948, x=2.2 fSumw[25]=1625, x=2.3 fSumw[26]=659, x=2.4 fSumw[27]=195, x=2.5 fSumw[28]=50, x=2.6 fSumw[29]=18, x=2.7 fSumw[30]=4, x=2.8 fSumw[31]=7, x=2.9
Electron Eff Result
Inclusive detected electrons -vs- Q-squared | Inclusive Missing Mass (W) for 1.0 Q^2 <1.2 |
Media:electronefficiencyratioBp7Bn11.txt
Now plot efficiency as function of X_{BJ} and W < 1232 and require pion.
Positive Pion Efficiency dependence on
Pion and electron both required.
W<1232 and
Now cut on Q^2 where the inclusive electron rates are the same with both torus settings and then require at least one positive pion.
X_bj | B_n/B_p Rates |
---|---|
0.14 | 0.25 | 0.55
0.15 | 0.74 | 0.27
0.17 | 1.07 | 0.18
0.19 | 1.3 | 0.13
0.2 | 1.4 | 0.14
There appears to be a region around X_{Bj}= 0.2 which has the same number of pions detected for both torus settings.
Negative Pion Efficiency dependence on
Pion and electron both required(e_sector=7 for B>0 && e_sector=11 for B<11).
Now cut on Q^2 where the inclusive electron rates are the same with both torus settings and then require at least one positive pion.
B_p/B_n Rates | |
---|---|
0.2 | 0.004 | 0.55
0.3 | 0.017 | 0.5
0.4 | 0.069 | 0.6
0.5 | 0.0262 | 0.6
0.6 | 0.039 | 0.5
0.7 | 0.1 | 0.64
0.8 | 0.055 | 0.52
0.9 | 0.259 | 0.52
1 | 1.232 | 0.52
1.1 | 3.96 | 0.8
There DOES NOT appears to be a region which has the same number of negative pions detected for both torus settings.
What is wrong?
8/13/10
1.) Change Osipenko cuts to maximize electrons when B <0 but still minimize impact of negative pion contamination. Look at effects on Npe distribution.
Insert current number of electron events that are removed by the Osipenko cut for B<0. Compare it to event removed by other cuts.
2.) Schedule Prelim exam.
Shropshire has replaced cole.
Members are: Forest, Fisher, Shropshire, Dale, Tatar(?)
Ask Dustin McNulty
1.) [1]
"Original cut parameters generated by Osipenko et.al. were not very efficient for especially outbending data of eg1b experiment. The loss of electrons was substantial. For inbending data, loss of electrons were at acceptable level. To gain some electrons back we generated new cut parametes that will specifically work better for outbending data. Also we slightly adjusted the cut parameters for inbending data for some sectors and segments."
2.) Upgraded Proposal defense presentation(includes event display) File:TamarProposalP 1.pdf
11/10/10
DTS files used for analysis.
Media:ND3Bn.txt
Media:ND3Bp.txt
Media:NH3Bn.txt
Media:NH3Bp.txt
positive
negative
What are the cuts for the above histogram?
pion, OSI, EC
11/30/10
DST ntuple suggestions
- Event number and run number should be recorded. Run number is in RUNINFO. Event number should be in the event packet.
- Create variable called helicity and fill it with absolute helicity.
GEM detector
- order mylar and copper tape., 1" wide, $20 worth of each
- check DPO 4104 see if working properly
- find 10 frames for Qweak GEM foils (or order more)
- check gas supply
12/6/10
DST ntuple
Run number looks good.
PbPt values are all non-zero now.
1) Some of the TORUS values are zero when they should be positive?
Doesnt matter. There are totally four files: ND3_target+Torus_positive, ND3_target+Torus_negative, NH3_target+Torus_positive and NH3_target+Torus_negative. So not an issue.
2.) Electrons have less than 0.25 GeV energy?
Still dont know.
3.) ASYM=HWP*LINAC*P_T is in the root file.
4.) Where are the FC normalization histograms
12/20/10
DST
1.) Looks like a particle ID problem for outbending (B<0) negative pions.
Calculate the missing mass for the and stor it in M_X. (included and corrected in NTUPLE)
Redo all the ntuples.
All ntuples are done.
2.) is run 27048 OK (no target run(empty)), corrected for both target runs
3.) Current quarks(the core of the constituent quark without the gluons and sea quarks(covering). The mass of the current quarks(up and down) is 5-10 MeV), light cone?
pion momentum for different torus settings and targets
pion paddle number for different torus settings
Need a before and after cuts histogram with stats to see number of events dropped