1
|
Dec 14/23 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
|
Present
|
11
|
-------
|
12
|
Regina - Garth Huber, Muhammad Junaid, Nathan Heinrich, Ali Usman,
|
13
|
Vijay Kumar, Alicia Postuma, Nacer Hamdi
|
14
|
CUA - Richard Trotta, Tanja Horn
|
15
|
JLab - Dave Gaskell
|
16
|
FIU - Pete Markowitz
|
17
|
|
18
|
Nathan
|
19
|
------
|
20
|
Getting ready for full replay of PionLT data
|
21
|
- param files in standard.database are set up
|
22
|
- modifications to param files done by some scripts, took several days to get
|
23
|
everything working
|
24
|
- CoinTime offset needs adjustment due to RefTime cut change
|
25
|
- wrote a sript to plot CoinTIme, want it centered around 0 w/ new offset
|
26
|
- replays to determine new CT offset worked
|
27
|
~30 runs done so far, more planned
|
28
|
- PTRIG6 runs will require different CT offsets than PTRIG5 runs
|
29
|
- full replay going soon
|
30
|
|
31
|
Junaid
|
32
|
------
|
33
|
More on getting ready for full replay of PionLT data
|
34
|
- updated def cuts for efficiency studies, report files
|
35
|
- setting up batch scripts before starting full replay
|
36
|
|
37
|
Richard
|
38
|
-------
|
39
|
Batch job information
|
40
|
- recommends to separate hcana replay from python script job
|
41
|
- makes memory allocation for jobs easier
|
42
|
- need to increase memory efficiency for batch jobs in order to get a good
|
43
|
running priority
|
44
|
- 800MB seems to be a good allocation for hcana replays
|
45
|
- python request needs 10GB, seems large, needed for jobs to run properly
|
46
|
- GH: try creating a python binary for production running, interpreted python
|
47
|
is good for development, but is inefficient for large scale running, this
|
48
|
should reduce memory usage and CPU time
|
49
|
- newest replays at:
|
50
|
/lustre19/expphy/cache/hallc/kaonlt/Pass3_Dec_2023
|
51
|
- rough vresion of script that calculates resource usage:
|
52
|
/u/group/c-kaonlt/USER/trottr/lt-analysis/usage_check.sh
|
53
|
|
54
|
- meeting w/ Ali to discuss efficiecies, uncertainties in effs, Heep yields
|
55
|
|
56
|
- Ali mentions that we also need to implement offsets into SIMC physics input
|
57
|
files
|
58
|
|
59
|
Ali
|
60
|
---
|
61
|
pi+ Delta0 BSA analysis
|
62
|
- starting w/ Q2=2.115, 3.0-2.32, 3.0-3.14 settings
|
63
|
|
64
|
- MM study in Delta region
|
65
|
- need bin-by-bin shape study
|
66
|
- SIDIS scaled to data in MM=1.4-1.55 GeV region
|
67
|
- pi+n MC scaled to neutron peak
|
68
|
- Delta MC is matched to data after n, SIDIS are subtracted
|
69
|
- Delta yields calculated for MM=1.1-1.4 GeV region for each helicity setting
|
70
|
- BSA calc separately for Delta, Bkd, Sum Yields
|
71
|
|
72
|
- maybe we can do 2 t-bins for 2 FF points (higher statistics) after adding
|
73
|
Left, Center, Right SHMS settings
|
74
|
|
75
|
Things to be done:
|
76
|
- check rho contribution to this MM region
|
77
|
- implement kinematic offsets in analysis
|
78
|
- understand pi+n resolution difference
|
79
|
|
80
|
Dave: it's important to confirm you're doing a Dummy target subtraction
|
81
|
- surprised the piDelta BSA is so close to the BSA asymmetry, is there a good
|
82
|
physics reason why they're so similar?
|
83
|
- it would be helpful to calculate also the BSA for the 1.35<MM<1.55 region, to
|
84
|
see if the BSA is different there or not
|
85
|
|
86
|
Discussion on the pi+n resolution difference:
|
87
|
|
88
|
GH: the HMS drift chamber resolution in SIMC is set in:
|
89
|
hms/mc_hms_hut.f
|
90
|
variable: hdc_sigma is set to 0.030 for each plane
|
91
|
- similarly for SHMS in shms/mc_shms_hut.f
|
92
|
DG: first need to look at correlations between FP variables and MM before
|
93
|
making adjustments
|
94
|
- Alicia had done an intial look at this, but wasn't completed. Will look in
|
95
|
more detail after the holidays
|
96
|
|
97
|
Dave: also need to confirm whether NGC is in shms_hut.f or NOT
|
98
|
- want it OUT for KaonLT, IN for PionLT
|
99
|
- it would be great if Dave could add an input flag which would set this,
|
100
|
otherwise, we will need different versions of the code for KaonLT, PionLT
|
101
|
|
102
|
Dave: Maybe the beam energy spread is the issue? PROBABLY!
|
103
|
- in 6 GeV era, the beam energy spread was never an issue
|
104
|
- but it's significantly worse for 10 GeV beam!
|
105
|
|
106
|
- Note that this refers to the width of the beam energy distribution, and is a
|
107
|
different parameter than the uncertainty in the beam energy (which refers to
|
108
|
the uncertainty in the centroid in the distribution), not the width
|
109
|
- For an accurate simulation, SIMC does not use a monochromatic beam energy,
|
110
|
but rather has a Gaussian energy distribution given by this width
|
111
|
|
112
|
- DG finds a 2013 Note: at 11 GeV the spread is 0.02%, at 6 GeV 0.01%. No
|
113
|
mention of what it is at 8.5 GeV
|
114
|
- GH will write Jay Benesch to get more info
|
115
|
|
116
|
Alicia
|
117
|
------
|
118
|
Reprocessing 10.6GeV data with offsets
|
119
|
- will look at memory issue mentioned by Richard for batch jobs
|
120
|
- next step will be MM study, binned in t
|
121
|
|
122
|
Nacer
|
123
|
-----
|
124
|
Calibration checks of 3.835, 4.933 GeV KaonLT data
|
125
|
- SHMS beta distribution was around 1.1, with new Hodo time walk parameter
|
126
|
(determined from 3.8 data) beta is now closer to 1
|
127
|
- good news, this time walk param also works well on 4.9 data
|
128
|
- next step is to check if this makes any effect on DC calib
|
129
|
|
130
|
- Ali: new offsets should be automatically implemented in his analysis, if he's
|
131
|
pointing to the right files
|
132
|
- NH should confirm with AU this is the case
|
133
|
|
134
|
Vijay
|
135
|
-----
|
136
|
Lumi and Heep cross section check for Summer 2019 data
|
137
|
- using Richard's method for Lumi
|
138
|
- results: Carbon -0.243%/100uA LH2 -5.06%/100uA
|
139
|
- consistent with Richard's results, which is good
|
140
|
- Heep MC/Data yields are also consistent with 1, within errors
|
141
|
|
142
|
Dave: the plots look a bit weird in that the error bars for many points are
|
143
|
quite large (+/-5%)
|
144
|
- Pete: judging from the small scatter of the data, it looks like the error
|
145
|
bars are over-estimated
|
146
|
- Ali: we had originally over-estimated the tracking efficiency
|
147
|
uncertainties, maybe that's an issue?
|
148
|
- Garth: or maybe it's simply an error in the plotting script?
|
149
|
- either way, this needs to be rechecked, as the uncertainties on the Lumi
|
150
|
and Heep checks are very important!
|
151
|
|
152
|
- another issue to check: it's very important to confirm that an error-weighted
|
153
|
fit of the results is done
|
154
|
- the results are very encouraging, but some checks are still needed
|
155
|
|
156
|
Next Meeting
|
157
|
------------
|
158
|
- Thur Dec 21 @ 15:00 Eastern/14:00 Regina
|
159
|
- KaonLT will go first
|
160
|
|
161
|
- there will be no meeting on Dec 28
|
162
|
- our first meeting of 2024 will be on Thur Jan 4
|
163
|
- after that, we will have to see what people's schedules are for the new
|
164
|
semester and see if this time still works for everyone, or not
|
165
|
|
166
|
|
167
|
|
168
|
|
169
|
|