Difference between revisions of "November 30, 2015"
From GlueXWiki
Line 15: | Line 15: | ||
::: - test/debug trigger (2 - 3 hours). | ::: - test/debug trigger (2 - 3 hours). | ||
::: - production (1 - 2 night shifts) | ::: - production (1 - 2 night shifts) | ||
+ | :::: run conditions depend on the accelerator performance (200 nA electron current, 10^-4 radiator, 10^-3 converter | ||
::* Debug trigger for FDC alignment (ST/TOF + FCAL) | ::* Debug trigger for FDC alignment (ST/TOF + FCAL) | ||
::: test/debug trigger (3 - 4 hours) | ::: test/debug trigger (3 - 4 hours) |
Revision as of 17:08, 10 December 2015
- Modifications of config files
- - parameters for CAEN R-C adjustment
- - parameters for fa125 initialization
- - implementation of SYNC events (in progress)
- - configuration of TRD, concurrent running with ST (in progress)
- Other
- - new TS firmware (check in progress)
- - BCAL LED trigger distribution through TS
- - TPOL stand alone self-trigger with CTP
- L1 trigger commissioning plans for the fall run
- PS trigger (TAGM bias voltage calibration, TAGH voltage scans). 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
- Debug trigger for FDC alignment (ST/TOF + FCAL)
- test/debug trigger (3 - 4 hours)
- production at low luminosity (with FDC switched on) - night
- Debug FCAL/BCAL trigger
- - test/debug trigger (3 - 4 hours)
- - take data with the BCAL/FCAL trigger for 1 night shift (thresholds will be tuned)
- - Trigger produced by TAGM/TAGH
- - Requests from sub-detectors