Difference between revisions of "DAQ/Trigger Run Check Lists"
From HallCWiki
Jump to navigationJump to searchLine 24: | Line 24: | ||
** [https://logbooks.jlab.org/entry/3501284 Reference time set-up] | ** [https://logbooks.jlab.org/entry/3501284 Reference time set-up] | ||
* Verify coincidence timing for composite triggers | * Verify coincidence timing for composite triggers | ||
+ | ** [https://logbooks.jlab.org/entry/3504470 HMS scope traces with beam] | ||
+ | ** [https://logbooks.jlab.org/entry/3508587 SHMS scope traces with beam] | ||
** Scope traces of all legs of the trigger | ** Scope traces of all legs of the trigger | ||
* Check relative arrival time of 3/4, EL-REAL, and EL-CLEAN triggers at TM | * Check relative arrival time of 3/4, EL-REAL, and EL-CLEAN triggers at TM |
Revision as of 10:45, 12 January 2018
Overview
- Here we discuss the necessary tasks which need to be completed at the beginning of a run period in order to ensure reliable operation of the single arm DAQ's as well as the coincidence DAQ.
Trigger Leg Definitions
STOF : 2/2 {1/2 {S1X, S1Y}, 1/2 {S2X, S2Y}} EL_LO_LO : 2/3 {STOF, 3/4, PR-LO} EL_LO : 2/2 {EL-LO-LO, CER} EL_HI : 3/3 {3/4, PR-HI, SH-LO} EL_REAL : 1/2 {EL_LO, EL_HI} EL_CLEAN : 2/2 {EL_LO, EL_HI}
General Checks
- Check SHMS & HMS hodoscope discriminator thresholds and widths
- Nominally these are 50 ns and -30 mV
- Check SHMS & HMS PID trigger thresholds
- Check SHMS & HMS PID trigger DC offsets on scope
Single Arm DAQ Checks
- Check reference times are behaving as expected via scope
- Verify coincidence timing for composite triggers
- HMS scope traces with beam
- SHMS scope traces with beam
- Scope traces of all legs of the trigger
- Check relative arrival time of 3/4, EL-REAL, and EL-CLEAN triggers at TM
- Primary trigger should come first, subsequent triggers should arrive 10-20 ns later
- Watch for and correct any trigger related offsets due to different reference time shifts from different triggers
- Software offsets to be determined and implemented
- Verify desired trigger takes the TDC timing
- Ensure the intended reference time is being selected by the analyzer (sanity check self timing peaks)
- Verify readout windows are capturing all the data via. raw histograms
- Use “production_all” replays to do this
- Primary checks: trigger apparatus, hodoscopes, chambers
- Sanity check dead-times utilizing various forms of measurements
Coincidence DAQ Checks
- Verify SHMS & HMS coincidence trigger timing
- Check relative arrival times of trigs at TM
- Ensure T6 is first, other triggers should arrive 10-20 ns later
- Watch for and correct any trigger related offsets due to different reference time shifts from different triggers
- Software offsets to be determined and implemented
- Verify desired trigger takes the TDC timing
- Ensure the intended reference time is being selected by the analyzer (sanity check self timing peaks)
- Verify readout windows are capturing all the data via. raw histograms
- Use “production_all” replays to do this
- Primary checks: trigger apparatus, hodoscopes, chambers