130 likes | 262 Views
HES HKS meeting. 2 1 May 2010 T.Gogami. C ontent. Coincidence Time difference EHODO17 Chi square cut. Coincidence Time (htimetar - etimetar). Run 76956 – 77124 for 52 Cr target. ( 1/3 of all runs ). ?. coincidence time abs(htimetar – etimetar + 55)<1. coincidence time
E N D
HES HKS meeting 21 May 2010 T.Gogami
Content • Coincidence Time difference • EHODO17 • Chi square cut
Coincidence Time(htimetar - etimetar) Run 76956 – 77124 for 52Cr target ( 1/3 of all runs ) ? coincidence time abs(htimetar – etimetar + 55)<1 coincidence time abs(htimetar – etimetar + 55 + 0.6)<1
Coin timeRun num. 77032 - 77091 Something happened
Check “Hall C Log” • RunID < 77065 • htimetar – etimetar +55.0 + 0.6 • RunID >=77065 • htimetar – etimetar +55.0
EHODO 17 hitpattern 77068 77062 • EH hitpat. changed at Run 77063 • Signals which going to 2nddiscri. are small due to high rate. EH 2nddiscri. thereshold changed to -100 [mV] from -200 [mV] • After pushed the cable connected to F1 TDC , EH hitpat. became normal ! 77063
Chi square cut CH2 , HKS track CH2 , HES track • Scan • htrkchi2 / htrkndf < X • etrkchi2 / etrkndf < 3 FIXED 52Cr , HKS track 52Cr , HES track FIXED
S/N with different χ2 cut BETTER than without χ2 cut NReal CH2 NAcc. NAcc. definition not so good
Event num. ratio with different χ2 cut ex.) X=3 • CH2 : 69 % • 52Cr : 25 %
Missing Mass for 52Cr Λ binding region Λ binding region QF QF Acc. Background Acc. Background
Summary and to do • Summary • Cointime cut • RunID < 77065 • htimetar – etimetar +55.0 + 0.6 • RunID>=77065 • htimetar – etimetar +55.0 • EHODO 17 • cable connection before F1 TDC • chi square cut • a lot of bad tracks for 52Cr • chi square cut S/N improve in Λ-binding region • to do • check cointime • golden data to analyzer • matrix with GEANT4
5/17/2010 2次会