Difference between revisions of "March 22, 2015"
From GlueXWiki
(2 intermediate revisions by the same user not shown) | |||
Line 3: | Line 3: | ||
:# Tune trigger parameters (trigger threshold scans, tune timing offsets) and study performance for | :# Tune trigger parameters (trigger threshold scans, tune timing offsets) and study performance for | ||
::: - FCAL (2 days) | ::: - FCAL (2 days) | ||
− | :::: Performed threshold scans for noise/cosmic runs [[https://logbooks.jlab.org/entry/3328066 | + | :::: Performed threshold scans for noise/cosmic runs [[https://logbooks.jlab.org/entry/3328066 Log entry]] |
::: - BCAL (1 day) | ::: - BCAL (1 day) | ||
::: - FCAL & BCAL (1 day) | ::: - FCAL & BCAL (1 day) | ||
::: - ST and TOF (1 day) | ::: - ST and TOF (1 day) | ||
− | ::: - Coincidence of FCAL/BCAL and ST/TOF ( | + | ::: - Coincidence of FCAL/BCAL and ST/TOF (2 days) |
::: - Multiple triggers in the system (2-3 days) | ::: - Multiple triggers in the system (2-3 days) | ||
+ | :::: Trigger hit-pattern is written to the trigger record | ||
*Trigger Monitoring | *Trigger Monitoring |
Latest revision as of 09:32, 23 March 2015
- Trigger Commissioning Plan
- Integrate PS trigger to the global DAQ (1 - 2 days)
- Tune trigger parameters (trigger threshold scans, tune timing offsets) and study performance for
- - FCAL (2 days)
- Performed threshold scans for noise/cosmic runs [Log entry]
- - BCAL (1 day)
- - FCAL & BCAL (1 day)
- - ST and TOF (1 day)
- - Coincidence of FCAL/BCAL and ST/TOF (2 days)
- - Multiple triggers in the system (2-3 days)
- Trigger hit-pattern is written to the trigger record
- - FCAL (2 days)
- Trigger Monitoring
- - Use config files to initialize electronics modules