Difference between revisions of "Run Group A"

From clas12-run
Jump to navigation Jump to search
Line 127: Line 127:
 
* At 2 am empty the target and run 150 nA beam until the beam is taken away with rga_v2.trg and the beam blocker in. Change the DAQ alarm limits by going to DAQ /CLAS12 Trigger /Menu /Alarm Settings Expert/ Set All Normalized Rate Limits when the beam and rates are stable. Change the BTA accounting limits in the Beamlin/BTA config (replace the upper limit with 160 nA).  
 
* At 2 am empty the target and run 150 nA beam until the beam is taken away with rga_v2.trg and the beam blocker in. Change the DAQ alarm limits by going to DAQ /CLAS12 Trigger /Menu /Alarm Settings Expert/ Set All Normalized Rate Limits when the beam and rates are stable. Change the BTA accounting limits in the Beamlin/BTA config (replace the upper limit with 160 nA).  
 
-->
 
-->
The beam is supposed to be back around 3-40 pm on Monday, April 8'th. After establishing the physics-quality beam (follow the procedure outlined in https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf) take production data at 50 nA, DAQ config: PROD66; Trigger file: rga_v2.trg.
+
 
 +
The beam is expected to be back around 3-30 pm on Monday, April 8'th. After establishing the physics-quality beam (follow the procedure outlined in https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf) take production data at 50 nA, DAQ config: PROD66; Trigger file: rga_v2.trg.
 
*Note: <font color=red>DO NOT IGNORE</font> unsafe FSD masking alarm! Follow alarm guidance.
 
*Note: <font color=red>DO NOT IGNORE</font> unsafe FSD masking alarm! Follow alarm guidance.
  

Revision as of 13:50, 8 April 2019

[edit]


Clas12design.png