Difference between revisions of "March 22, 2015"

Latest revision as of 09:32, 23 March 2015

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

- Use config files to initialize electronics modules

@@ Line 1: / Line 1: @@
+* 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 [[https://logbooks.jlab.org/entry/3328066 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
 *Trigger Monitoring
@@ Line 6: / Line 18: @@
 :: - Use config files to initialize electronics modules
-    Trigger algorithm study for the spring run
-    FCAL thresholds tuning
-            - check rates with MC simulation (MC)
-            - MIP response
-    Coincidence of FCAL with other sub-detectors
-            - require tracks in ST
-            - energy correlation with BCAL
-            - combined trigger base on BCAL/ST correlations and FCAL thresholds
-    FCAL trigger tuning
-        decreasing integration window size (time).
-            - propagation time for MIPs (MC simulation)
-            - cable length, PMT transit time spread
-            - check with acquired data
-    Level-1 Monitor
-    Discussion on the calibration trigger types