E05-115 Collaboration Meeting Mar10-11, 2010

ENGINE replay summary 2019/2/21

Analysis over view 2019/2/21

Revision summary Added new ntuple contents Modified EDC tracking routine, parameter and geometry Modified HDC tracking parameter and geometry KHODO, EHODO parameter tuning WC parameter tuning New default matrix 2019/2/21

Ntuple contents summary Add hsbeta1y … beta between 1y and 2x hmsq … mass square of HKS particle haern*p(n) … AC la-* pos (neg). channel npe hacn*p(n)m … AC la-* pos (neg). channel npe, 2hit hact*p(n) … AC la-* pos (neg). channel time hact*p(n)m … AC la-* pos (neg). channel time, 2hit hwatn*p(n) … WC la-* pos (neg). channel npe hwcn*p(n)m … WC la-* pos (neg). channel npe, 2hit hwct*p(n) … WC la-* pos (neg). channel time hwct*p(n)m … WC la-* pos (neg). channel time, 2hit hwatnkn* … WC la-* kaon normalized npe Modified bpm3c*x(y) … BPM value in ADC hmsq (GeV/c2) bpm3c12, y (cm) : x (cm) 2019/2/21

HTRACKING KHODO Analysis Select proper ADC, TDC hit information KDC Analysis Calculate the number of tracks Calculate FP value Tracking w/ KDC and KHODO Select Good track Check Very close tracks Momentum Reconstruction For beta calculation modified TOF calculation Reject strange beta modified AC, WC, LC calculation Select proper hit, Calc NPE Hit Selection, Physics Select hits on the track 2019/2/21

ETRACKING EHODO Analysis Select proper ADC, TDC hit information EDC Analysis modified Tracking w/ EDC1 and EHODO Define the number of tracks in HES modified Select Good track Check Very close tracks modified Tracking w/ EDC2 Fine tracking w/ EDC2, calc FP variables Momentum Reconstruction For beta calculation Hit Selection, Physics Select hits on the track 2019/2/21

multiplicity -KDC CH2 Run CH2 Run 52Cr Run 52Cr Run 2019/2/21

CH2 Run CH2 Run CH2 Run 52Cr Run 52Cr Run 52Cr Run multiplicity -KHODO 2019/2/21

multiplicity –AC,WC CH2 Run CH2 Run 52Cr Run 52Cr Run 2019/2/21

multiplicity –EDC CH2 Run CH2 Run 52Cr Run 52Cr Run 2019/2/21

multiplicity –EHODO CH2 Run CH2 Run 52Cr Run 52Cr Run 2019/2/21

KTOF resolution parameter tune … Nagao ELOG Message ID 566 2019/2/21

ETOF resolution Before tuning (during experiment) After tuning EH2-EH1 (ns) vs esxfp (cm), All channel EH2-EH1 (ns) vs esxfp (cm), w/o strange channels Strange channels … EH2-17,19,21,23,25,27,19 Maybe one of discriminator for EHODO was wrong 2019/2/21

p suppression -> Listen Gogami’s talk for detail Applied cut -> (haernpe1+haernpe2)<5 || (haernpe2+haernpe3)<5 || haernpe3+haernpe1<5 haernpe1+2+3 vs hmsq [GeV/c2] black : before cut red : after cut -> Listen Gogami’s talk for detail 2019/2/21

p suppression -> Listen Gogami’s talk for detail Applied cut -> (hwatnkn1+hwatnkn2)>6*hmsq-1.5 new ntuple content : hwatnkn1,2 Kaon npe =1, s=0.2 hwatnkn1+2 vs hmsq [GeV/c2] black : before cut red : after cut -> Listen Gogami’s talk for detail 2019/2/21

coin time analysis TEFP TKFP TEt TKt HES Ref. Plane HKS Ref. Plane TF2TE(xf, x’f, yf, y’f) … G4 simulation TF2TK(xf, x’f, yf, y’f) … G4 simulation TEt TKt Target coin time = TKt-TEt About TF2T For the correction of path length Calculated by G4 4th polynomial of xf, x’f, yf, y’f Target : CH2 s~350ps 2019/2/21

FP distribution (HKS) background from certain Z CH2 run76315 G4, brems G4, brems kaonの漏れ込み？永尾解析 2019/2/21

FP distribution (HES) CH2 run76315 CH2 run76315 strange offset effect of strange channel of EH2 G4, brems G4, brems ｙ‘問題, offset 2019/2/21

KD TOSCA model 1 KD TOSCA model (before modification) Picture Pole edge shape was different from real one KD TOSCA model (after modification) 2019/2/21

KD TOSCA model 2 By [T] Black：measured Red＊：before modification Red×：after modification z [mm] 2019/2/21

KD TOSCA model 3 TOSCA-measure [T] Black：Before modification Red：After modification (TOSCA-measure)/measure [%] 2019/2/21

Default matrix calculation Magnification factor of KD, ED TOSCA map in G4 KD : 1.0, ED : 1.0 KD : 0.995, ED : 0.98 Other factors KQ1=1.02 KQ2=1.055 EQ1=1.00 EQ2=1.00 -> Need to be optimised L, S0 peak position is about -15MeV Geometrical modification of magnets in G4 Included survey result in G4 -> not big change 2019/2/21

momentum at target (HKS) ky’t vs kx’t (CH2 run, L selected) kmom (CH2 run, L selected) ky’t vs kx’t (G4, L source (uniform)) kmom (G4, L source (uniform)) 2019/2/21

HKS SS pattern Run 76808 ↓ same histograms (different plot option) ↓ 2019/2/21

momentum at target (HES) ey’t vs ex’t (CH2 run, L selected) emom (CH2 run, L selected) come from bad channel? (->Gogami’s talk) ey’t vs ex’t (G4, L source) emom (G4, L source) 2019/2/21

HES SS pattern Run 76810 ↓ same histograms (different plot option) ↓ FP pattern 2019/2/21

missing mass – CH2 target - Statistics # of lambda ~ 3800, S/N ratio ~ 1.2 # of sigma ~ 780, S/N ratio ~ 0.55 s at L … 2.3 [MeV] 2019/2/21

Analysis Status @ H2O Run Missing Mass spectrum (online, preliminary) Comment The number of L (Kaon) is less than expected value, why? S/N ratio is worse than CH2 because of the window (Havar) of CH2 We took some beam energy scan data in H2O target. count L Mx-ML [MeV] count HKS-HES coin time spectrum Beam momentum in H2O run Nominal value (2344MeV/c) ½とかは言わない方がよい、Havarのスペック +20MeV/c -1MeV/c +1MeV/c ns Hallcp [MeV/c] 12/15/2009 HKS-HES Collaboration Meeting @ Rome

missing mass – 12C target - All Run 20uA Run Make an offset so as to adjust L and S0 peak position. The position of g.s-like peak is slightly different from last experiment’s one. The number of events in the g.s-like peak is 3-5 times smaller than the value calculated from the number of events in QF region. 2019/2/21

missing mass – 7Li target - g.s-like peak and 5/2+, 3/2+-like peak can be seen at reasonable BL region. The number of peak looks smaller than the value counted from QF events. HES y’ cut : etheta>0.065, selecting almost upper half of EQ1. E. Hiyama, Y. Yamamoto, T. Motoba, M. KamimuraPHYSICAL REVIEW C 80, 054321 (2009) 2019/2/21

missing mass – 10B target - T. Motoba, M. Sotona and K. Itonaga, Prog. Thor. Phys. Suppl. No. 117 (1994) 123.　 g.s-like peak can be seen around –BL=8MeV HES y’ cut : -(eyss)>-5 (cm)。 2019/2/21

Issue+To do summary Raster correction SS analysis Matrix tuning Event selection from multiple events in engine First check the number of Kaon. We can say something from the result of Z dependence of the number of Kaon. The reduction of replay time HES tracking code check (y’ offset problem) HKS tracking code check (resolution, multiplicity) Replay time reduction, especially for 52Cr and H2O run How to evaluate the linearity of missing mass? 2019/2/21

HES tracking 2019/2/21

ETRACKING Procedure EHODO Analysis Select proper ADC, TDC hit information EDC Analysis modified Tracking w/ EDC1 and EHODO Define the number of tracks in HES modified Select Good track Check Very close tracks modified Tracking w/ EDC2 Fine tracking w/ EDC2, calc FP variables Momentum Reconstruction For beta calculation Hit Selection, Physics Select hits on the track 2019/2/21

FP resolution FP resolution ~ (DC plane resolution)/sqrt(# of plane) EDC1 plane resolution (x) = 210mm → HES FP(x) resolution = 210/sqrt(6) [mm] ~ 86 [mm] But … EDC plane resolution is bad in the coincidence trigger event! Reason is EDC TDC start time is not determined by EHODO in the coin. trigger event. s=780mm s=250mm EDC1-1 ds (wire center) @ SS Run (75460) EDC1-1 ds (wire center) @ CH2 Run (76312) 2019/2/21

Starttime correction Make tracking only using x-x’ planes of EDC1 Pick a corresponding counter of EH1 and determine a starttime of the track Subtract starttime from drift time of each wires Make full-tracking using xx’, uu’, vv’ Pick some nearest hits on each planes of EDC2 Subtract corresponding starttime from drift time of each EDC2 wires Make tracking including EDC2 EDC1 EDC2 Question How may hits should be required for EDC2? EH1 2019/2/21

Starttime correction result (only EDC1) befotre s=780mm after s=200mm EDC1-1 ds (wire center) @ CH2 Run (76312) EDC1-1 ds (wire center) @ CH2 Run (76312) 2019/2/21

SS pattern run76810 (SS run) ←Only the angular results of EDC2 tracking were used dray(1)=Xfp dray(2)=Yfp dray(3)=X’fp dray(4)=Y’fp 2019/2/21

EDC1-1 EDC1-2 EDC1-3 EDC1-4 EDC1-5 EDC1-6 EDC1-7 EDC1-8 EDC1-9 EDC1-10 EDC1 drift time run76312 (CH2 run) EDC1-1 EDC1-2 100ns EDC1-3 EDC1-4 EDC1-5 EDC1-6 EDC1-7 EDC1-8 EDC1-9 EDC1-10 2019/2/21

EDC2-1 EDC2-2 EDC2-3 EDC2-4 EDC2-5 EDC2-6 EDC2 drift time run76312 (CH2 run) EDC2-1 EDC2-2 100ns EDC2-3 EDC2-4 EDC2-5 EDC2-6 2019/2/21

EDC1-1 EDC1-2 EDC1-3 EDC1-4 EDC1-5 EDC1-6 EDC1-7 EDC1-8 EDC1-9 EDC1-10 EDC1 tracking residual run76312 (CH2 run) include himself, typical residual = 250mm EDC1-1 EDC1-2 EDC1-3 EDC1-4 EDC1-5 EDC1-6 EDC1-7 EDC1-8 EDC1-9 EDC1-10 2019/2/21 2019/2/21

EDC2-1 EDC2-2 EDC2-3 EDC2-4 EDC2-5 EDC2-6 EDC2 tracking residual run76312 (CH2 run) include himself, typical residual = 250mm EDC2-1 EDC2-2 EDC2-3 EDC2-4 EDC2-5 EDC2-6 2019/2/21 2019/2/21