Project

General

Profile

Kaon LT Meetings » mtg_26mar26-27.txt

Garth Huber, 03/27/2026 03:48 PM

 
1
                Mar 26-27/26 PionLT/KaonLT Analysis Meeting Notes
2
                -------------------------------------------------
3
                                (Notes by GH)
4

    
5
                    Today: KaonLT will be discussed first
6

    
7
Thursday: Present
8
-----------------
9
Regina - Garth Huber, Nathan Heinrich, Nermin Sadoun, Nacer Hamdi,
10
   Alicia Postuma, Muhammad Junaid
11
CUA - Sammer Jain, Chi Kin Tam, Tanja Horn
12
Virginia - Richard Trotta
13
Ohio - Julie Roche
14

    
15
Richard
16
-------
17
KaonLT high Q2 LT-sep
18
- investigating small |t| thetaCM behavior
19
  - the problem shown last week was that the #events for thetaCM~0 gets large
20
    in data but not MC
21
  - implemented Gabriel's suggestion, which was to replace thetaCM with
22
    sin(thetaCM) in the analysis, but it made no difference
23
  - followed the crucial clue, which was that the weird behavior is only in
24
    data, not MC.  Maybe it's caused by pion leakthrough background events?
25

    
26
- modified the background subtraction algorithm for variables other than MM
27
  - previously, applied to these variables a background scale factor determined
28
    from the integral of the MM background normalization
29
  - that method ignores the kinematic correlations between MM and other
30
    variables
31
  - new method: on an event-by-event basis, determine a background subtraction
32
    scale factor to apply to pion leakthrough subtraction events determined
33
    from where they are in the MM distribution, rather than an average
34
    normalization factor
35
  - then fill the other variables (e.g. Q2, W) with this MM-weighted background
36
    scale factor   
37
  - the subtraction then takes into account the correlations between MM and
38
    other kinematic variables for background events
39
  - fixes the spike at small thetaCM
40
  - data vs MC comparisons are also now better for variables other than MM,
41
    Q2-dist is better, SHMS/HMS-delta dists have noticeably better comparisons
42
    between data and MC
43
  - *NB* issue yet to be solved: lower end of W-distibution is weirdly cut-off,
44
    looks artificial
45

    
46
Chi Kin
47
-------
48
KaonLT high Q2 syst unc studies
49
- varied acceptance cuts
50
  - changes cut regions in low-epsilon distributions
51
  - of course, the high-epsilon data have a diamond cut, so changing the
52
    acceptance cut has no effect
53
  - SIMC yield, Data yield, average kinematics, will all change
54
  - still need to calculate new cross sections
55
  - Tanja: as long as the MC correctly describes the data, the cross sections
56
    should remain stable
57

    
58
- varying diamond cuts
59
  - looking to decrease polygon size by 2.5%-15%
60
  - Garth: this seems too big of a change, the issue primarily is small
61
    variations on the edges of the diamond where the #events starts dropping
62
    and there is a small ambiguity on where to place the boundary
63
    - large diamond changes will affect first and last t-bins much more than
64
      the others, given where in the diamond these events come from
65
  - *NB* comparing RT and CKT's diamonds is likely to be more instructive
66

    
67
- rad corr
68
  - last week: showed that Rad-On/Off gave a huge variation
69
    - Dave suggested to compare Rad-On/Off for pion case, and use that for the
70
      systematic
71
      - CKT not sure how to properly propage this to K+ t-phi bins, GH suggests
72
        an overall scale factor instead of t-phi dependent
73
    - Tanja: suggests to check how this was handled in Carmignotto, Mohrning,
74
      Niculescu theses
75
    - *NB* Garth: suspect last week's result indicates the MM cut is too
76
      narrow, see if you can widen the MM cut to reduce the sensitivity
77
  - Garth: for pi+ analysis, there is very little background underneath the
78
    neutron peak, so one can unambiguously investigate the rad corr systematic
79
    - for K+ analysis, there is some ambiguity in the Lambda tail, as it
80
      depends on how much pion background is subtracted.  Possibly it makes
81
      more sense to quote a combined background-subtraction/RadCorr systematic,
82
     rather than separately
83

    
84
- K decay correction in SIMC
85
  - changed the K+->mu+nu_mu branching ratio in SIMC, made no difference
86

    
87
Sameer
88
------
89
PionLT Q2=1.6 W=3.08 yield analysis
90
- replayed data for both high and low epsilon
91
- initial PID checks
92
  - CoinTime shows pi+ and K/p bands vs MM
93

    
94
- *NB* Junaid apply cuts in this specific order:
95
  1) acceptance cut
96
  2) then CoinTime
97
  3) then look at other Detectors in various combinations
98
- *NB* Garth: this is briefly described in the notes following Kathleen's
99
  presentation of March 13, suggest to look them up
100
  - Tanja: also look at recent Hall C theses to learn what was done there
101

    
102
- after cuts, will check CoinTime and RF time offsets
103

    
104

    
105
Friday: Present
106
---------------
107
Regina - Garth Huber, Nathan Heinrich, Alicia Postuma, Muhammad Junaid,
108
   Nermin Sadoun, Nacer Hamdi
109
CUA - Chi Kin Tam, Tanja Horn
110
Virginia - Richard Trotta
111
JMU - Gabriel Niculescu
112
Glasgow - Kathleen Ramage, Rachel Montgomery
113
FIU - Pete Markowitz
114

    
115
Nacer
116
-----
117
KaonLT Q2=0.5 LT-sep
118
- implementing t-shift based on MM-shift, followed by 1 iteration
119
  - sigL: low -t peak is gone, t-dependence is much flatter now, the issue is
120
    that the first t-bin is negative by ~1.5sigma
121
    - no longer an exponential, the fit parameter in the exponent prefers zero
122
  - sigT: rises to compensate
123
  - interference terms: basically the same
124
- iterate 2 more times
125
  - Data/MC ratios are better than before, generally more flat vs phi
126
  
127
- Richard: they haven't shown their results yet, but after t-shift the
128
  cross-sections stayed similar to before the shift
129
  - Later note by GH: the reduced sensitivity could likely be due to the higher
130
   -t values of the high Q2 data and the correspondingly wider t-bin
131
- Nacer will change the lower limit of the 1st t-bin a bit, to avoid the
132
  unphysical region near -tmin
133
  - *NB* Richard: suggests to plot W,Q2 for each t-bin (summing
134
    Left,Right,Center SHMS) and compare to the ave-Q2,ave-W values the model is
135
    calculated at
136
    - this is how he found the thetaCM problem, the ave-Q2,ave-W values were
137
      outside the range of the data distribution, now they agree well
138

    
139
- shows plots of -t vs -tmin
140
  - generally good agreement between edge of distribution and -t=-tmin line
141
  - shows small #events -t<-tmin
142
    - Garth: have pion leakthrough been subtracted?  It seems likely these are
143
      due to mis-identified pions
144
    - Nacer: indeed no pion leakthrough is subtracted on these plots
145

    
146
- has CoinTime blocking info from Sameer, preparing to replay data to determine
147
  the correction factors
148

    
149
Alicia
150
------
151
u-channel analysis
152
- met w/ Bill on Tuesday for 2hr on shape study
153
  - he suggested to not worry on exact values of u-bins right now, concentrate
154
    more on the shape study now and fine-tune the u-bins after that is done
155
  - seems good advice, concentrating now on getting the MC fits to data to work
156
    properly
157

    
158
Nathan
159
------
160
PionLT LT-sep framework checks
161
- Junaid and Nathan now have exactly matching data yields, moving on to SIMC
162
  yield comparisons
163
  - SIMC yields agree to better than 1e-6 for one setting
164
  - now running other SHMS settings for checks
165
- after that is done, will compare cross sections
166

    
167
- identified an issue during Data yield comparisons
168
  - Junaid had defined ROC1 as ROC2 by mistake, due to a copy/paste error in
169
    python environment setup
170
  - once this was fixed, ROC2 needs to be defined as ROC2, things agreed
171
  - Junaid has pushed the fixed version to UTIL_PION
172
  - *NB* Kathleen, Nermin, Sameer should double check their python environments
173
    to make sure they did not inherit Junaid's bug
174

    
175
- setting up replay scripts for other settings in x=0.39 scaling scan
176

    
177
Junaid
178
------
179
PionLT Q2=3.85 W=2.62 LT-sep
180
- applying t-shift based on MM-shift
181
  - MM-shifts were in different directions for lo, hi epsilon, t-shifts
182
    similarly will be in opposite directions
183
  - also some of the MM-shifts were fairly large, ~10 MeV
184
  - this is the "worst case" scenario in terms of sensitivity to t-shift
185

    
186
- shows plots of -t vs -tmin after t-shift applied
187
  - before t-shift, had events -t<-tmin
188
  - hi eps: after t-shift, events move away from -t=-tmin line, now events have
189
    -t>-tmin
190
  - lo eps: before t-shift, there was a small gap between data and -t=-tmin
191
    line, after t-shift the gap is gone, events come right to the line
192
  - this confirms the respective t-shifts are applied with correct sign
193

    
194
- LT-sep after t-shift
195
  - very large effect, sigT now has a steep rise in cross section at low -t,
196
    while sigL is fairly flat
197
    - more distressing: sigL is now negative by ~1.5sigma at low -t
198
  - plots of unsep cross sections vs phi also indicate this, the gap between
199
    high and low epsilon is much smaller after t-shift
200
  - Data/MC ratios do not look good, particularly at low -t, where they are 2
201
    and higher, this at least tells us that the data are not consistent with
202
    this new behavior
203
  - for a test, applies t-shifts with same sign for hi,lo epsilon, rather than
204
    opposite sign.  sigL is much better behaved
205

    
206
- *NB* Garth: are we sure the MM offsets are correct?  We should take a closer
207
   look at them given this info, maybe we can reduce some of the MM-shifts
208
- *NB* Nacer: suggests to change the low -t bin lower limit, to exclude events
209
   very close to -tmin
210
   
211
Kathleen
212
--------
213
LD+ yield for Q2=1.6 W=3.08 6.4GeV (2022) data
214
- last week: looked at detector cuts in more detail
215
- Random Subtraction: selecting 3 peaks on either side of prompt, with a gap of
216
  2 away from prompt peak (i.e. peaks 3-5 on either side)
217
  - Garth: some evidence that the 5th peak is a bit smaller than peaks 2,3,4 on
218
    both sides.  Possibly they are getting close to the edge of the coincidence
219
    timing window.  Suggest to use peaks 2-4 rather than 3-5, as their heights
220
    are more uniform
221

    
222
- Dummy Target Subtraction:
223
  - calculated target thickness factor f=4.009 from target group report
224
  - normalized by total beam charge as a quick test
225
  - *NB* Nacer: need to form Qeff from the detector efficiencies and livetimes
226
    - the relevant information should be in the report files
227

    
228
- MM plot after Random and Dummy subtractions
229
  - Nacer: to minimize sensitivity to the MM cut, put the cut in the
230
    plateau between the neutron peak and Delta-rise
231
  - *NB* Alicia: your next step should be to compare the MM peak to SIMC, to
232
    see how well they agree, that will also guide where to place the MM cut
233

    
234
Next steps:
235
- calculate Qeff from detector efficiencies, livetimes
236
- will clean up macros used to make plots
237
- will present a poster at IOP conference, will distribute a draft for comments
238

    
239
Nermin
240
------
241
PionLT 9.117GeV Q2=1.6 W=3.08 SHMS=6deg detector efficiencies
242
- SHMS Aerogel:
243
  - Last week: LD+ aerogel eff was 97%
244
    - added a HGC cut to the aerogel efficiency calculation to reduce K/p
245
      contamination, now the efficiency is 99%
246
  - new LD- detector efficiencies
247
    - using cuts on SHMS calorimeter, acceptance, CoinTime, obtained aerogel
248
      efficiency of 98%
249
    - after adding HGC, aerogel eff improved to 99%
250

    
251
- HMS Cherenkov:
252
  - coin efficiency is lower for LD- than LD+
253
  - this means HMS calorimeter is not removing all pi- from the electron sample
254
    used to calculate the efficiency
255
  - tightened the calorimeter cut, efficiency improved
256

    
257
- HMS Calorimeter:
258
  - applied acceptance, CoinTime, Cherenkov cuts, got eff=0.978 +/- 1e-4
259
  - tightened the Cherenkov cut, nothing improved
260
  - Garth: the issue when calculating the HMS calorimeter efficiency is that it
261
    is very difficult to remove all of the pi- contamination in the electron
262
    sample
263
  - Ali ended up using dedicated Heep runs with minimal pi- contamination in
264
    his HMS calorimeter efficiency study, and then apply this efficiency to the
265
    physics data
266
  - *NB* Junaid: he has done the HMS calorimeter efficiency study for HMS
267
    momenta from 1-4 GeV/c.  Please check the HMS momentum for your setting,
268
    and if it is within this range then you can use his efficiencies (and
269
    uncertainties) directly
270
    - Junaid will send his slides on this
271

    
272
Next steps:
273
- Lumi study for LD2 cryotarget
274
  
275

    
276
   Next Meetings
277
------------------
278
- Thurs: Apr 2 @ 16:00 Eastern/14:00 Regina
279
  - PionLT will go first
280
    
281
- Fri: Apr 3 @ 11:00 Eastern/9:00 Regina
282
  - NO MEETING DUE TO EASTER (GOOD FRIDAY) HOLIDAY
283

    
284

    
285
  
286

    
287

    
288

    
289

    
290
  
291
  
292
  
293
 
(885-885/885)