Difference between revisions of "February 8, 2016"
From GlueXWiki
Line 11: | Line 11: | ||
* Trigger info in the Config DB | * Trigger info in the Config DB | ||
− | * [https://logbooks.jlab.org/entry/3376980 Analysis of the fall data] | + | * [https://logbooks.jlab.org/entry/3376980 Analysis of the fall data] Elton |
* '''L1 trigger commissioning plans for the fall 2015 spring 2016 run''' | * '''L1 trigger commissioning plans for the fall 2015 spring 2016 run''' |
Latest revision as of 10:49, 8 February 2016
- Check Configuration at Run Start
- Check fadc250 baselines
- Check Registers
- Initial implementation of SYNC events
- TS scalers
- fadc250 pedestals
- PS scalers
- Check electronics initialization during data taking
- Trigger info in the Config DB
- L1 trigger commissioning plans for the fall 2015 spring 2016 run
- PS trigger (TAGM bias voltage calibration, TAGH, PS voltage scans, efficiency studies). Run TRD in parallel, if no problems.
- - test/debug trigger (2 - 3 hours).
- - production (1 - 2 night shifts)
- run conditions depend on the accelerator performance (200 nA electron current, 10^-4 radiator, 10^-3 converter + Be converter, TBD)
- Trigger for FDC alignment (ST/TOF + FCAL)
- Trigger for FCAL MIPs calibration (ST & TOF)
- - test/debug trigger (3 - 4 hours, CDC/FDC switched off)
- - production at low luminosity with the FDC switched on (1 - 2 night shifts for both the FDC alignmnent and FCAL MIP triggers)
- Debug FCAL/BCAL trigger
- - trigger studies (3 - 4 hours)
- - take data with the BCAL/FCAL trigger, FCAL/BCAL thresholds will be tuned, chambers can be switched on depending on run conditions (1 - 2 night shifts).
- - test trigger performance at high rate. Take data with 'nominal' trigger thresholds.
- Trigger generated by TAGM/TAGH
- - trigger studies (3 - 4 hours)
- - combine TAGH/TAGM with other trigger types.
- - take data with the total absorption counter, 2x10-5 radiator, a few nA current (TBD) (2 - 3 hours)
- Special trigger requests from sub-detectors