Difference between revisions of "Spring 2018 Commissioning"

From HallCWiki
Jump to: navigation, search
(Run Plans)
(SHMS & HMS Mode 10 Runs)
Line 60: Line 60:
  
 
* SHMS Runs
 
* SHMS Runs
# Any kinematics, 100k events, EDTM off
+
# Any kinematics, ~1M events, EDTM off
# Any kinematics, 100k events, EDTM on at 100 Hz
+
# Any kinematics, ~1M events, EDTM on at 100 Hz
 
* HMS Runs
 
* HMS Runs
# Any kinematics, 100k events
+
# Any kinematics, ~1M events
# Any kinematics, 100k events, EDTM on at 100 Hz
+
# Any kinematics, ~1M events, EDTM on at 100 Hz
  
 
== Single Arm and Coincidence EDTM Studies ==
 
== Single Arm and Coincidence EDTM Studies ==

Revision as of 11:14, 9 January 2018

Overview

Topics which are relevant to the DAQ/Trigger for the Spring 2018 commissioning run are discussed here.

To-Do

  • High Priority
    • Configure Dave G. Dead time measurement scheme (Arrington’s and/or Morhings thesis)
    • Check HMS & SHMS hodoscope discriminator widths (40 ns, -30 mV)
    • Configure NGC into SHMS PID trigger leg in place of HGC
    • Sanity check SHMS hodoscope CAMAC power supply (noticed unstable behavior during end of fall run)
    • Add SHMS PRSHWRSUM in trigger apparatus (FADC leaf)
    • Remove layer B from HMS pre-shower sum
  • Medium Priority
    • Figure out DAC to mV conversion factor, find old talk regarding setting the DAC values to obtain pedestals a pre-determined value
    • Include multi-hit capability in the trigger apparatus for reference times
    • Integrate TI scalers into report files
    • Configure OR of hodoscope trigger logic into TDC’s and scalers
    • Change trigger leaf names to PRLO from PRSHWRLO etc. (needs to match xscaler)
  • Low Priority
    • Add number of FADC error flags to the report files (front and center)
    • Add number of pulses identified in the window to data tree

DAQ/Trigger Run Plans

Single Arm & Coincidence Dead Time Studies

Run Conditions

  • Kinematics that provide ~1.5 kHz at 1-5 uA in each spectrometer arm and coincidence mode
  • EDTM on at 100 Hz
  • These runs can be performed parasitically

Run Plans

  • Single arm runs
  1. 5 uA, ~1.5 kHz, ps1 = 0, ~10 min (900k events)
  2. 10 uA, ~3.0 kHz, ps1 = 0, ~10 min (1.8 M events)
  3. 20 uA, ~6.0 kHz, ps1 = 0, ~10 min (3.6 M events)
  4. 40 uA, ~12.0 kHz, ps1 = 0, ~10 min (7.2 M events)
  5. 60 uA, ~18.0 kHz, ps1 = 0, ~10 min (10.8 M events)
  • Coincidence runs
  1. 5 uA, ~1.5 kHz, ps6 = 0, ~10 min (900k events)
  2. 10 uA, ~3.0 kHz, ps6 = 0, ~10 min (1.8 M events)
  3. 20 uA, ~6.0 kHz, ps6 = 0, ~10 min (3.6 M events)
  4. 40 uA, ~12.0 kHz, ps6 = 0, ~10 min (7.2 M events)
  5. 60 uA, ~18.0 kHz, ps6 = 0, ~10 min (10.8 M events)

SHMS & HMS Mode 10 Runs

Run Conditions

  • At 1.5 kHz these runs should take ~5--10 min
  • These runs can be performed parasitically

Run Plans

  • SHMS Runs
  1. Any kinematics, ~1M events, EDTM off
  2. Any kinematics, ~1M events, EDTM on at 100 Hz
  • HMS Runs
  1. Any kinematics, ~1M events
  2. Any kinematics, ~1M events, EDTM on at 100 Hz

Single Arm and Coincidence EDTM Studies

Run Conditions

  • EDTM 10 Hz runs should be taken when the run lengths are > 30 minutes
  • EDTM 100 Hz runs should be taken when the run lengths are < 30 minutes
  • If short runs are being performed then the EDTM can be run at 1 kHz
  • These runs can be performed parasitically although folks will need to know how to cut the EDTM events out of the data

Run Plans

  • SHMS Single arm EDTM runs at various rates
  1. SHMS Run: Any kinematics, EDTM at 10 Hz
  2. SHMS Run: Any kinematics, EDTM at 100 Hz
  • HMS Single arm EDTM runs at various rates
  1. HMS Run: Any kinematics, EDTM at 10 Hz
  2. HMS Run: Any kinematics, EDTM at 100 Hz
  • Coincidence EDTM runs at various rates
  1. Coincidence Run: Any kinematics, EDTM at 10 Hz
  2. Coincidence Run: Any kinematics, EDTM at 100 Hz

Trigger PID Threshold Scans

Run Conditions

  • Runs should contain ~500k events which at 1.5 kHz trigger rate will take 5 minutes per run
  • These runs can be performed parasitically

Run Plans

  • SHMS PID threshold scan with NGC in trigger (HGC was previously utilized)
  1. NGCER 40, PRSH-LO 40, PRSH-HI 60
  2. NGCER 30, PRSH-LO 30, PRSH-HI 50
  3. NGCER 25, PRSH-LO 25, PRSH-HI 40
  4. NGCER 20, PRSH-LO 20, PRSH-HI 30
  5. NGCER 15, PRSH-LO 15, PRSH-HI 20
  6. NGCER 10, PRSH-LO 10, PRSH-HI 10
  • HMS PID threshold scan
  1. CER 40, PRSH-LO 40, PRSH-HI 60, SH-LO 40
  2. CER 30, PRSH-LO 30, PRSH-HI 50, SH-LO 30
  3. CER 25, PRSH-LO 25, PRSH-HI 40, SH-LO 25
  4. CER 20, PRSH-LO 20, PRSH-HI 30, SH-LO 20
  5. CER 15, PRSH-LO 15, PRSH-HI 20, SH-LO 15
  6. CER 10, PRSH-LO 10, PRSH-HI 10, SH-LO 10

Single arm SHMS & HMS runs with EL-REAL and EL-CLEAN being readout (need to time these in at the TI front panel)

Run Conditions

  • Runs should contain ~500k events which at 1.5 kHz trigger rate will take 5 minutes per run
  • These runs can be performed parasitically

Run Plans

  • SHMS single arm multi-trigger type studies
  1. Any kinematics, 500k events, EDTM off
  2. Any kinematics, 500k events, EDTM on at 10 Hz
  • HMS single arm multi-trigger type studies
  1. Any kinematics, 500k events, EDTM off
  2. Any kinematics, 500k events, EDTM on at 10 Hz

Talks

Log Book Entries