Project

General

Profile

Kaon LT Meetings » mtg_25nov20-21.txt

Garth Huber, 11/21/2025 02:50 PM

 
1
                Nov 20-21/25 PionLT/KaonLT Analysis Meeting Notes
2
                -------------------------------------------------
3
                                (Notes by GH)
4

    
5
                    Today: PionLT 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
Thursday: Present
11
-----------------
12
Regina - Garth Huber, Nathan Heinrich, Muhammad Junaid, Alicia Postuma,
13
   Nermin Sadoun
14
Virginia - Richard Trotta
15
CUA - Chi Kin Tam, Tanja Horn
16
JLab - Dave Gaskell
17
Ohio - Julie Roche
18

    
19

    
20
Junaid
21
------
22
PionLT pion absorption correction via Geant4
23
- NGC on, Aerogel n=1.011 simulation for P_shms=5.127 GeV/c
24
- added an uncertainty calculation
25
- correction is 0.9654 +/- 0.00005
26

    
27
RF cut PID efficiency
28
- added HGC to PID selection cuts to both numerator (Did) and denominator
29
  (Should)
30
- get 0.99802 +/- 0.00007
31

    
32
- will apply both corrections to the normalized physics yields
33
  - *NB* Garth: it would be great if you could put together a table of
34
    systematic uncertainties similar to what is in the Blok paper
35
    - please include Nathan's new systematic errors there as well
36

    
37
Next steps
38
- setting up for next Q2 LT-sep, checking RF cut offsets for these data
39

    
40

    
41
Nathan
42
------
43
PionLT CoinLumi analysis
44
- sent everyone a copy of his Lumi report for comment
45
  - no comments received yet from Sameer
46

    
47
- question for Dave on where to find the documentation for the hodoscope gate
48
  width
49
  - after some hunting, Dave finds:
50
    Found an elog from 2019 that says discriminator widths were 50 ns
51
    https://logbooks.jlab.org/entry/3747761
52
  - Dave also asks Bill Henry to recheck the gate widths manually, and gets
53
    back an answer surprisingly quickly
54
    https://logbooks.jlab.org/files/2025/07/4423016/IMG_6761.jpeg
55
    which confirms that the widths are still 50ns
56
  - Nathan confirms that 50ns is the value he used in his ELLT calculation, so
57
    everything should be good now
58

    
59

    
60
Alicia
61
------
62
pi+n BSA paper has been resubmitted to PLB
63
- awaiting on final communication from journal, hopefully about page proofs
64
- working on arXiv submission, filling in author list metadata
65

    
66
u-channel replay of Q2=3.0, W=2.32 data
67
- the intent was to see if new HMS matrix elements for P_hms=6.59 GeV/c made
68
  any improvement to the MM reconstruction resolution
69
  - differences in MM are quite small, we will have to live with the worse
70
    resolutionfor this setting
71

    
72
- pi+n contamination in omega region is worse than for Q2=3.0, W=3.14 setting
73
  - the two MM peaks are not fully resolved, comparison to clean pion data
74
    indicates omega is 1-1.5sigma to left of pi+n, so very close to the nominal
75
    1.5sigma optical criterion for resolving two close peaks
76
  - unfortunately, no RF cut for this setting
77
  - also, Python generator behaves poorly for this setting, as reported earlier
78
    (extraneous MM shape)
79
    - Garth: suggests to consult with Henry Klest on Pythia settings
80

    
81
- retained EM^2 PM^2 so MM^2 can be calculated
82
  - SIMC predicts DVCS and pi- to be offset from each other by ~1 sigma, but
83
    MM^2 data is shifted by ~1 sigma to right of both peaks
84
    - doesn't trust data peak positioning so far away from omega, pi+n region
85
    - applying a shift of 4 MeV^2 to data, to overlap data with pi0 simulation
86
      shows reasonable agreement in peak shape, lends credence that this region
87
      is mostly pi0, as expected
88
    - low epsilon data doesn't need any MM offset, as peaks already in correct
89
      position, and also RF cut available
90

    
91
Next steps:
92
- will look in more detail at low epsilon MM^2 data
93
- will contact Henry Klest re. Pythia
94

    
95

    
96
Richard
97
-------
98
KaonLT Q2=3.0, W=2.32 LT-sep
99
- looking at t-phi bins with anomalously low cross sections
100
  - the issue is that these are bins with no pi+n leakthrough to anchor the
101
    background fit underneath Lambda peak
102
  - Chebyshev polynomial fits for background are poorly constrained, and
103
    clearly oversubtracting, giving outlier yields near zero
104
  - now looking at 2 different types of background fits
105
    - quadratic w/far edge fixed to MM=1.15 GeV data
106
    - Chebyshev poly fitting the rest
107
    - still adjusting fit parameters, but things looking better
108
  - *NB* Garth: the error bars due to this background fitting uncertainty are
109
    significantly underestimated, the way you'r calculating these errors is
110
    fine only for those settings where pi+n leakthrough gives a constraint, but
111
    you need to take into account the uncertainty in the background estimation
112
    where it is poorly constrained
113

    
114
- using Q2=4.4 parameterization
115
  - Goal: all ratios within 3sigma of mean, and mean within 1.5sigma of unity
116
  - then will apply these fit functions also to Q2=5.5 data
117
  
118

    
119
Chi Kin
120
-------
121
KaonLT Q2=3.0, W=3.14 LT-sep
122
- last week, theta_pq (CM frame) was not calculated correctly
123
  - wrong reference frame used, giving negative weights in re-weighting script
124
  - this is fixed now, things looking more consistent
125

    
126
- iterations looking a bit better now
127
  - did 8 iterations, fits stabilized but still not good enough
128
  - looked at t-binning, with goal to improve the yields in poorly-populated
129
    bins
130
    - narrowed the t-bin ranges:
131
      new bin limits: 0.19,0.26,0.31,0.38,0.49
132
      - previously had 0.17 to 0.6
133
      - Richard was using only data up to 0.4
134

    
135

    
136
Friday: Present
137
---------------
138
Regina - Garth Huber, Nathan Heinrich, Muhammad Junaid, Nacer Hamdi,
139
   Vijay Kumar, Nermin Sadoun
140
York - Stephen Kay
141
CUA - Sameer Jain, Tanja Horn, Chi Kin Tam
142
JMU - Ioana Niculescu, Gabriel Niculescu
143
Ohio - Julie Roche
144
JLab - Dave Gaskell
145
CSULA - Konrad Aniol
146

    
147

    
148
Nacer
149
-----
150
KaonLT Q2=0.5 LT-sep
151
- still looking for right parameterization
152
  - fitting only sigT=p1/Q2+|t|^p2/(Q^2+p3)^2, L=LT=TT=0
153
  - switched to simpler Wfac=1/(W^2-mp^2)^2
154
  
155
  - did 4 iterations
156
    - Data/MC ratios looking quite a bit better, R near 1 and flatter than
157
      before
158
      - high epsilon has a bit bigger oscillations than low epsilon
159
    - sigT has non-monotonic t-dependence
160

    
161
- would like to try adding back sigL now
162
  - *NB* Garth: suggests a polynomial for sigT, the fit |t|^p2 form is
163
    monotonic and cannot reproduce the observed t-dependence
164
    - TT could be a simple straight line fit TT=a+b*t, no Q2-dependence
165
    - L could be some simple monotonic, like L=p1+|t|^p2
166
    - keep LT=0
167

    
168
- kinematic and focal plane plots for Data and MC
169
  - overall the plots look good, but there are some mismatches between Data and
170
    MC that generated some discussion
171
    - SHMS_xpfp is a bit narrower than data
172
    - HMS xptar has a shift between data and MC for high epsilon, right SHMS
173
  - *NB* Gabriel: puzzled that the HMS_xptar shift is as large as it is
174
    - Dave: this is a known issue with HMS xptar reconstruction
175
      - the data should be corrected by a couple of mr, could have an impact on
176
        phi-distribution, i.e. at edges of acceptance Data and MC will
177
        mismatch, giving rise to oscillations in the Data/MC ratio
178
      - Junaid did not see this effect
179
      - *NB* Nacer and Junaid will compare 0th order matrix offsets used in
180
        replays
181

    
182

    
183
Vijay
184
-----
185
PionLT Low Q2 LT-sep
186
- systematic checks for Coin Blocking correction
187
  - varied timing cuts +/-4ns
188
    - resulting uncertainties are correlated with epsilon for both Q^2:
189
      - low epsilon: +/-0.5%, mid and high epsilon: +/-0.3%
190
      
191
  - how should we apply these uncertainties to data?
192
    - Nathan: what about calculating it run-by-run and adding it in quadrature
193
      with the statistical errors?
194
    - Garth: these are not random errors, should not be added in quadrature
195
      with statistical errors.  The issue is that random errors are magnified
196
      by 1/Delta-epsilon in the L/T-separation, non-random errors are not
197
      magnified
198
      - Nacer: wouldn't it be more conservative to take the biggest error and
199
        apply it with the statistical?
200
	- Dave: the issue is that it's too conservative, under-reports the
201
  	  quality of the data, and results in lower quality L/T-separation
202
	  
203
    - *NB* Dave: need to break this uncertainty into parts (see systematics
204
      table in Blok paper).  Part of the uncertainty is global, and part of it
205
      epsilon-correlated)
206
      - Garth: take the smallest (high epsilon) value ~0.3% as a scale
207
        systematic uncertainty, and the difference between the low and mid
208
        epsilon values and this smallest value as the epsilon-correlated part
209
	- Dave: agrees with this suggestion
210
    - *NB* Garth needs to have a discussion with students on how systematic
211
      uncertainties were treated in Fpi-2 analysis (Blok paper)
212

    
213
- shows Data MC overlay for kinematic and focal plane plots for 2 Q2=0.425
214
  settings:
215
  - high epsilon, Right-2
216
  - low epsilon, Center
217
  - agreement looks fairly good, HMS yptar shift seems smaller than Nacer's
218
    
219
  
220
Sameer
221
------
222
KaonLT Coin Blocking correction
223
- error bars are statistical and systematic added in quadrature, following our
224
  discussion he will quote them separately next time
225
  - Nathan also needs to separate them in his analysis
226

    
227
- systematic uncertainty is bigger than statistical, which indicates a problem
228
  in the analysis
229
  - *NB* Nathan: the right cut is too tight into the distribution, it needs to
230
    shift by ~20ns
231

    
232
- Nacer: what boiling factor should we use for KaonLT data?
233
  - *NB* Nathan: Richard's boiling factor is ~2x Nathan's
234
    - would like someone to redo this study using the same methodology as in
235
      Nathan's report
236
      - perhaps Richard used what we now understand to be the wrong LiveTime,
237
        given the newer studies?
238
      - hopefully get a boiling number similar to Nathan, in which case use his
239
        number as it's higher statistics
240
	- if it's significantly different, then need to investigate in more
241
	  detail
242
  - Garth: agrees with this suggestion, it would be good for Nacer to add
243
    this to his list.  Nathan thinks reproducing his study should not take long
244
    to do
245

    
246

    
247
Gabriel
248
-------
249
Looking in more detail at KaonLT offsets
250
- ideally want a common set of offsets for all settings
251
- using physics data to investigate the variation in the offsets with setting,
252
  which will also be helpful in understanding the uncertainties in the offsets
253
  -  uses Lambda, Sigma, pi+n MM peaks as constraint
254
    - Lambda, Sigma: compare data to SIMC MM values
255
    - pi+n: recalculate MM using pion mass and compare to SIMC
256

    
257
- follows a method similar to Richard:
258
  - generates many offsets, evaluates MM for each
259
    - finds best set of offsets, then creates a new generation of offsets near
260
      these values
261
    - process is time consuming, only 1 generation done so far, expect 2-3
262
      generations necessary to converge
263
    - gets a nice set of histos of offsets satisfying some criteria for each
264
      generation
265

    
266
- not using hcana MM values, calculating everything on own from spectrometer
267
  vectors
268
  - using HallC:p value of the beam energy, not the value from
269
    standard.kinematics
270
  - *NB* Garth: we had a discussion about this at a meeting that Gabriel
271
    missed.  The issue is that HallC:p is not corrected for the Arc Energy
272
    Measurement.  Need to find the value of HallC:p at the time of the Arc
273
    Energy Measurement (AEM), and then correct all other values by the ratio
274
    Beam=(HallC:p_now)/(HallC:p_AEM)*(AEM-GeV)
275
    - also note that for 10.6 GeV beam energy the bremsstrahlung of the beam in
276
      the Hall C Arc is too large to ignore.  The Arc Energy Measurements are
277
      corrected for this loss (via a calculation), while HallC:p is not
278
      corrected for it.
279

    
280

    
281
  Next Week Meetings
282
------------------
283
- Thurs: Nov 27: no meeting due to USA Thanksgiving
284
    
285
- Fri: Nov 28 @ 11:00 Eastern/10:00 Regina
286
  - Canadians and UK collaborators are invited
287
  - Richard thought he would be available to attend
288

    
289
  
290
  
291
	
292
    
(788-788/789)