1
|
Apr 24/25 PionLT/KaonLT Analysis Meeting Notes
|
2
|
----------------------------------------------
|
3
|
(Notes by GH)
|
4
|
|
5
|
Today: KaonLT will be discussed first
|
6
|
|
7
|
Please remember to post your slides at:
|
8
|
https://redmine.jlab.org/projects/kltexp/wiki/Kaon_LT_Meetings
|
9
|
|
10
|
Present
|
11
|
-------
|
12
|
Regina - Garth Huber, Ivan Zhenchuk, Ali Usman, Alicia Postuma,
|
13
|
Nathan Heinrich, Vijay Kumar, Nacer Hamdi
|
14
|
JLab - Dave Gaskell
|
15
|
FIU - Pete Markowitz
|
16
|
Virginia - Richard Trotta
|
17
|
Ohio - Julie Roche
|
18
|
|
19
|
Richard
|
20
|
-------
|
21
|
KaonLT both Q2=3.0 settings update
|
22
|
- W=2.32 setting
|
23
|
- modified fitting algorithm, had some constraints on the fit range of some
|
24
|
parameters, the ranges for some parameters were widened
|
25
|
- it=10 shown
|
26
|
- Data/MC ratios generaly better, particularly for lower 2 t-bins
|
27
|
- higher 2 t-bins have weird Data/MC ratios near zero for phi~0 at high
|
28
|
epsilon, where there's good data, Richard is investigating
|
29
|
- L/T/LT/TT t-dependences look fairly reasonable
|
30
|
- L>T everywhere
|
31
|
- LT is still large, similar magnitude to L
|
32
|
- TT~15, which is still large, but quite a bit smaller than last week
|
33
|
- believes the differences are due to change in fitting parameters
|
34
|
- *NB* Garth asks to next time please show "money plots", i.e. the plots of
|
35
|
unseparated cross sections vs phi at both epsilon used to determine the
|
36
|
separated cross sections
|
37
|
|
38
|
- *NB* some discussion about the fitting algorithm
|
39
|
- Richard says he checks if the chi-square is stable after some iterations
|
40
|
- Garth stresses the importance of also checking if the output parameters
|
41
|
are close to the edge of a fitting window. If they are, the chi-square
|
42
|
will be stable, but the fit results not optimized
|
43
|
|
44
|
- W=3.14 setting
|
45
|
- Data/MC ratios nicely between 0.75-1.25 for lowest t-bin
|
46
|
|
47
|
- *NB* SIMC might not yet have Ali's resolution correction, needs to confirm this
|
48
|
|
49
|
Next steps:
|
50
|
- finish W=2.32 setting
|
51
|
- reparameterize W=3.14 with new form
|
52
|
- parameterize Q2=2.115 and do first tests, should have this by next week
|
53
|
- planning full replay of Data and SIMC at end of May
|
54
|
- Dave asks if a full replay is really necessary at this time
|
55
|
- Richard points out it would be helpful to do before starting on
|
56
|
systematics, as otherwise they would have to be redone later
|
57
|
- Garth suggests to try replaying the "worst" setting and see if anything
|
58
|
changes before deciding whether to replay everything else
|
59
|
|
60
|
Vijay
|
61
|
-----
|
62
|
PionLT Q2=0.425 MM offset study
|
63
|
- low epsilon, ~7 MeV shift between Data and MC, differences between peak
|
64
|
positions are clearly evident before offset is applied
|
65
|
- mid epsilon, ~2 MeV shift
|
66
|
- high epsilon, ~4 MeV shift but not all SHMS settings done yet. Some SIMC
|
67
|
settings appear to have a normalization error
|
68
|
|
69
|
Next steps:
|
70
|
- will try calculating pion missed triggers correction using Alicia's G4 code
|
71
|
|
72
|
Ali
|
73
|
---
|
74
|
piDelta BSA analysis, new binning of 3 of 5 kinematic settings
|
75
|
- starting with Q2=3.0, W=2.32 "The worst setting"
|
76
|
- hoping for 2 t-bins instead of 1
|
77
|
- low -t (0-0.6) center SHMS setting
|
78
|
- fit of MCs to Data MM distribution generally looks good, except for a systematic
|
79
|
discrepancy on left side of Delta peak
|
80
|
- in comparison to the shown MM Data region (>1.0), the brown pi+n MC looks
|
81
|
too low
|
82
|
- however, the pi+n MC is actually fit to the top of the pi+n peak that is
|
83
|
outside of this MM range, there is not sufficient freedom to raise the MC
|
84
|
normalization to fully reproduce the data in the 1.0-1.1 MM region
|
85
|
- the issue is that the resolution correction doesn't fully describe the
|
86
|
pi+n tail
|
87
|
- fortunately, the MM integration range for piDelta BSA excludes this poor
|
88
|
fit region
|
89
|
- Alicia: how will the systematic uncertainty be calculated, will it take into
|
90
|
account this discrepancy?
|
91
|
- one systematic will be determined from the difference between data and MC
|
92
|
shapes
|
93
|
- another systematic will be determined by varying the background
|
94
|
normalization within a "reasonable range", for the pi+n this should be
|
95
|
based on the statistical variation at the top of the pi+n peak, and so will
|
96
|
still not come all the way up to the data in the 1.0-1.1 MM region
|
97
|
- low -t right SHMS setting
|
98
|
- good statistics and fits in all 8 phi-bins
|
99
|
|
100
|
- high -t left SHMS setting
|
101
|
- 4 of 8 phi bins have good enough statistics and MM shapes to be fit
|
102
|
- high -t right SHMS setting
|
103
|
- the other 4 phi bins have good data, so the sum of left and right gives
|
104
|
good phi coverage
|
105
|
- this setting has more statistical variation than the left
|
106
|
- high -t center SHMS setting still in progress
|
107
|
- the issue is that at high -t, there is no pi+n tail between 1.0-1.1 GeV in
|
108
|
some phi bins and Ali's MC fiting code breaks
|
109
|
- shows plots at end of meeting, where Ali removed the pi+n MC from the fit
|
110
|
- phi bins 4,5 do not have Delta MM shape and will not be included despite
|
111
|
the fact that the code successfully gave a fit (i.e. fit is too uncertain
|
112
|
to extract). bins 1,8 are empty
|
113
|
|
114
|
Alicia
|
115
|
------
|
116
|
BSA paper: No update yet from PLB
|
117
|
|
118
|
KaonLT u-channel study
|
119
|
- replayed all 10.6 GeV data with proton selected and beam helicity enabled
|
120
|
|
121
|
- interesting discovery re. background underneath omega peak
|
122
|
- Henry Klest showed a PYTHIA simulation in the talk for his exclusive phi
|
123
|
production proposal
|
124
|
- gets a MM distribution similar to Alicia's data
|
125
|
- Alicia got Henry's code working and will try passing PYTHIA events
|
126
|
through SIMC
|
127
|
- Ali has a bit of experience with Python for his MSc work with CMS
|
128
|
- if that turns out to not work very well, the other option would be to
|
129
|
modify one of the existing SIDIS generators in SIMC to handle proton
|
130
|
fragmentation instead of pion fragmentation
|
131
|
- Garth spoke to Bill about this. They are planning to make such a
|
132
|
generator, GH told that we would be very interested if they could make
|
133
|
one soon rather than later
|
134
|
|
135
|
- RF PID studies
|
136
|
- Q2=3.0, W=3.14 center SHMS setting
|
137
|
- the RF works well for this setting, but it is not available for the right
|
138
|
SHMS setting
|
139
|
- RF vs Aerogel shows nice delineation between particle types
|
140
|
- Q2=3.0, W=2.32 - RF is not good, a wide distribution
|
141
|
- similarly RF not helpful for Q2=2.1 and 4.4 settings
|
142
|
- Q2=5.5 - RF is helpful and there for all SHMS settings
|
143
|
|
144
|
- MM plots
|
145
|
- Q2=3.0, W=3.14 helicity=+1
|
146
|
- pi+n peak is heavily suppressed (~1000x) with PID cuts
|
147
|
- Q2=3.0, W=2.32 - MM resolution is poorer, omega overlaps with pi+n peak so
|
148
|
it might be difficult to extract u-channel results for this setting
|
149
|
- Q2=2.1, W=2.95 - MM resolution is good, will have to apply pi/K sample
|
150
|
subtraction since no RF info available
|
151
|
- Q2=4.4 - same
|
152
|
- Q2=5.5 - should have nice results despite lower statistics. Can even
|
153
|
separate eta-prime after pi+n suppressed with RF cuts
|
154
|
|
155
|
- Cherenkov plots
|
156
|
- Q2=3.0, W=3.14 - HGC cut <2npe, Aerogel cut <3npe probably will change to
|
157
|
<2npe
|
158
|
- will evaluate a cut efficiency for the Aerogel, even if it is not
|
159
|
strictly needed for BSA, the pi+n PRL referee asked for it so we should
|
160
|
be prepared
|
161
|
- Q2=3.0, W=2.32 - plots shown of aerogel with HGC cut and vice versa
|
162
|
|
163
|
- Planned analysis order of settings
|
164
|
1) Q2=3.0, W=3.14: RF=Good Stats=High
|
165
|
2) Q2=5.5, W=3.02: RF=Good Stats=Low
|
166
|
3) Q2=2.1, W=2.95: RF=No Stats=High
|
167
|
4) Q2=4.4, W=2.74: RF=No Stats=Low
|
168
|
5) Q2=3.0, W=2.32: RF=No Stats=Med
|
169
|
|
170
|
Nacer
|
171
|
-----
|
172
|
KaonLT Q2=0.5 LTsep setup
|
173
|
- now has Data and SIMC Yields per t-phi bin
|
174
|
- wants to cross compare with Richard's results as a check
|
175
|
- working on scripts for Data-MC comparison plots and Ratios
|
176
|
- then will look at Richard's iteration scripts, with aim to simplify where
|
177
|
possible
|
178
|
|
179
|
Junaid
|
180
|
------
|
181
|
PionLT Q2=3.85, W=2.62 LTsep setup
|
182
|
- presents full equations for Normalized Yields and Error Calculations
|
183
|
- very nice! We appreciate the explicit documentation
|
184
|
- shows spreadsheet of Normalized Yield per t-phi bin
|
185
|
- Dave: the errors seem too small
|
186
|
- Note added later: JM found an error in his script, the errors were
|
187
|
normalized twice by mistake
|
188
|
- *NB* it would also be good to add columns of #Counts/bin and %error/bin
|
189
|
- working next on SIMC yields per t-phi bin
|
190
|
|
191
|
Nathan
|
192
|
------
|
193
|
PionLT Coincidence Blocking studies
|
194
|
- met with Dave last Tuesday
|
195
|
- plots made of CTime.CoinTime_RAW_ROC1,2
|
196
|
- ROC2 version has main CT distribution sitting on a very wide pedestal, from
|
197
|
-600 to +600
|
198
|
- ROC1 version has more structure, same pedestal to right of main CT
|
199
|
distribution to +600, but a sloping decline to left of CT distribution
|
200
|
extending to -400 and some sharp peaks at -400
|
201
|
|
202
|
- Dave is mystified, assuming a 50ns coincidence time window, the full CT
|
203
|
distribution should only be about 100ns wide, so what is causing the
|
204
|
distribution to be ~1000 wide?
|
205
|
- Dave: what timing window cuts are being applied?
|
206
|
- Nathan says the timing cuts are 2000 bins winde, but isn't sure offhand
|
207
|
what is the conversion to ns
|
208
|
|
209
|
- NOTE: Nathan is using ROC1 version in the analysis
|
210
|
- Dave suggests that the shoulder on the left of the ROC1 plot indicates we
|
211
|
should use ROC2
|
212
|
- plotting ROC1 vs ROC2 should indicate that it's running against a
|
213
|
trigger window limit
|
214
|
|
215
|
- Dave will look at the Timing Cuts used on the files Nathan sent him, to see
|
216
|
if he can figure out what's going on
|
217
|
|
218
|
- Nathan will try changing the TCOIN.param TDC cuts and see if it makes any
|
219
|
difference
|
220
|
- this would mean switching between offline and online versions
|
221
|
- not expecting the deadtime effect in the Lumi study to go away, but even it
|
222
|
changing would tell us a lot about the origin of the extra deadtime
|
223
|
|
224
|
Ivan
|
225
|
----
|
226
|
- NSERC summer student starting with us next Thursday May 1
|
227
|
- we will have him look at BSA data for low Q2 KaonLT and PionLT settings
|
228
|
- Alicia has kindly offered to replay these data with helicity enabled
|
229
|
|
230
|
Next Meeting
|
231
|
-------------
|
232
|
- Thur May 1 @ 15:30 Eastern/13:30 Regina
|
233
|
- PionLT will go first
|
234
|
** THIS TIME WILL BE USED AT LEAST UNTIL THE END OF AUGUST **
|
235
|
|
236
|
|
237
|
|
238
|
|
239
|
|
240
|
|
241
|
|
242
|
|
243
|
|