SHMS Run 10614: DIS, Longitudinal Trigger: ¾ (TRIG1...2020/04/28 · Ref. Time Name: pDCREFX...
Transcript of SHMS Run 10614: DIS, Longitudinal Trigger: ¾ (TRIG1...2020/04/28 · Ref. Time Name: pDCREFX...
-
SHMS Run 10614: DIS, LongitudinalTrigger: ¾ (TRIG1)
Report File: 0.368 kHz, Fit: 0.378 kHz
-
Detector: SHMS DC (tdc)Ref. Time Name: pDCREFXhcana Leaf Name: T.shms.pDCREFX_tdcMultiplicity
SHMS Run 10614: DIS, LongitudinalTrigger: ¾ (TRIG1)
• DCREF 1, and 3 through 10 all have multiplicities of 1 and 2• DCREF2 has multiplicity 2, 3, and 4
-
Detector: SHMS DC (tdc)Ref. Time Name: pDCREFXhcana Leaf Name: T.shms.pDCREFX_tdcTimeRaw
SHMS Run 10614: DIS, LongitudinalTrigger: ¾ (TRIG1)
Ø Why the much higher counts in pDCREFs 2, 3, and 10?
-
Detectors: SHMS CAL, HGCER, NGCER, HODO, TRIG (all adc)Ref. Time Name: pFADC_TREF_ROC2hcana Leaf Name: T.shms.pFADC_TREF_ROC2_adcPulseTimeRaw
SHMS Run 10614: DIS, LongitudinalTrigger: ¾ (TRIG1)
-
Detectors: SHMS HODO (tdc), TRIG (tdc)Ref. Time Name: pTref1hcana Leaf Name: T.shms.pT1.tdcTimeRaw
SHMS Run 10614: DIS, LongitudinalTrigger: ¾ (TRIG1)
-
Detectors: SHMS HODO (tdc), TRIG (tdc)Ref. Time Name: pTref2hcana Leaf Name: T.shms.pT2.tdcTimeRaw
SHMS Run 10614: DIS, LongitudinalTrigger: ¾ (TRIG1)
-
SHMS Run 10602: DIS, TransverseTrigger: ¾ (TRIG1)
Report File: 0.376 kHz, Fit: 0.387 kHz
-
Detector: SHMS DC (tdc)Ref. Time Name: pDCREFXhcana Leaf Name: T.shms.pDCREFX_tdcMultiplicity
SHMS Run 10602: DIS, TransverseTrigger: ¾ (TRIG1)
• DCREF 1, and 3 through 10 all have multiplicities of 1 and 2• DCREF2 has multiplicity 2, 3, and 4
-
Detector: SHMS DC (tdc)Ref. Time Name: pDCREFXhcana Leaf Name: T.shms.pDCREFX_tdcTimeRaw
SHMS Run 10602: DIS, TransverseTrigger: ¾ (TRIG1)
-
Detectors: SHMS CAL, HGCER, NGCER, HODO, TRIG (all adc)Ref. Time Name: pFADC_TREF_ROC2hcana Leaf Name: T.shms.pFADC_TREF_ROC2_adcPulseTimeRaw
SHMS Run 10602: DIS, TransverseTrigger: ¾ (TRIG1)
-
Detectors: SHMS HODO (tdc), TRIG (tdc)Ref. Time Name: pTref1hcana Leaf Name: T.shms.pT1.tdcTimeRaw
SHMS Run 10602: DIS, TransverseTrigger: ¾ (TRIG1)
-
Detectors: SHMS HODO (tdc), TRIG (tdc)Ref. Time Name: pTref2hcana Leaf Name: T.shms.pT2.tdcTimeRaw
SHMS Run 10602: DIS, TransverseTrigger: ¾ (TRIG1)
-
SHMS Run 9779: 3He Elastic, LongitudinalTrigger: EL-CLEAN (TRIG3)
Report File: 47.105 kHz, Fit: 47.17 kHz
-
Detector: SHMS DC (tdc)Ref. Time Name: pDCREFXhcana Leaf Name: T.shms.pDCREFX_tdcMultiplicity
SHMS Run 9779: 3He Elastic, LongitudinalTrigger: EL-CLEAN (TRIG3)
Ø pDCREFs 1, 3, 5, 7, 9 have multiplicities of 1,2,3,4,5Ø pDCREFs 2, 4, 6, 8, 10 have multiplicities of 0, 1,2,3,4,5. Why 0?
-
Detector: SHMS DC (tdc)Ref. Time Name: pDCREFXhcana Leaf Name: T.shms.pDCREFX_tdcTimeRaw
SHMS Run 9779: 3He Elastic, LongitudinalTrigger: EL-CLEAN (TRIG3)
Ø Why the pedestal in all DCREFX_tdcTimeRaw plots in this run?
-
Detectors: SHMS CAL, HGCER, NGCER, HODO, TRIG (all adc)Ref. Time Name: pFADC_TREF_ROC2hcana Leaf Name: T.shms.pFADC_TREF_ROC2_adcPulseTimeRaw
SHMS Run 9779: 3He Elastic, LongitudinalTrigger: EL-CLEAN (TRIG3)
Are the double peaks in the pFADC_TREF_ROC2_adcPulseTimeRaw
meaningful?
-
Detectors: SHMS HODO (tdc), TRIG (tdc)Ref. Time Name: pTref1hcana Leaf Name: T.shms.pT1.tdcTimeRaw
SHMS Run 9779: 3He Elastic, LongitudinalTrigger: EL-CLEAN (TRIG3)
Why the double peaks in the pT1_tdcTimeRaw plots for the elastic runs?
-
Detectors: SHMS HODO (tdc), TRIG (tdc)Ref. Time Name: pTref2hcana Leaf Name: T.shms.pT2.tdcTimeRaw
SHMS Run 9779: 3He Elastic, LongitudinalTrigger: EL-CLEAN (TRIG3)
Why the double peaks in the pT2_tdcTimeRaw plots for the elastic runs?
-
SHMS Run 9780: 3He Elastic, LongitudinalTrigger: EL-CLEAN (TRIG3)
Report File: 38.686 kHz, Fit: 47.66 kHz
-
Detector: SHMS DC (tdc)Ref. Time Name: pDCREFXhcana Leaf Name: T.shms.pDCREFX_tdcMultiplicity
SHMS Run 9780: 3He Elastic, LongitudinalTrigger: EL-CLEAN (TRIG3)
Ø pDCREFs 1, 3, 5, 7, 9 have multiplicities of 1,2,3,4,5Ø pDCREFs 2, 4, 6, 8, 10 have multiplicities of 0, 1,2,3,4,5. Why 0?
-
Detector: SHMS DC (tdc)Ref. Time Name: pDCREFXhcana Leaf Name: T.shms.pDCREFX_tdcTimeRaw
SHMS Run 9780: 3He Elastic, LongitudinalTrigger: EL-CLEAN (TRIG3)
Ø Why the pedestal in all DCREFX_tdcTimeRaw plots in this run?
-
Detectors: SHMS CAL, HGCER, NGCER, HODO, TRIG (all adc)Ref. Time Name: pFADC_TREF_ROC2hcana Leaf Name: T.shms.pFADC_TREF_ROC2_adcPulseTimeRaw
SHMS Run 9780: 3He Elastic, LongitudinalTrigger: EL-CLEAN (TRIG3)
Are the double peaks in the pFADC_TREF_ROC2_adcPulseTimeRaw
meaningful? (only present in the elastic (high rate) runs)
-
Detectors: SHMS HODO (tdc), TRIG (tdc)Ref. Time Name: pTref1hcana Leaf Name: T.shms.pT1.tdcTimeRaw
SHMS Run 9780: 3He Elastic, LongitudinalTrigger: EL-CLEAN (TRIG3)
-
Detectors: SHMS HODO (tdc), TRIG (tdc)Ref. Time Name: pTref2hcana Leaf Name: T.shms.pT2.tdcTimeRaw
SHMS Run 9780: 3He Elastic, LongitudinalTrigger: EL-CLEAN (TRIG3)