Difference between revisions of "Run Group C"

From clas12-run
Jump to navigation Jump to search
Line 201: Line 201:
 
* To account for the bleed thru problem, report 0.7 ABU and 0.3 BNA on the BTA interface.
 
* To account for the bleed thru problem, report 0.7 ABU and 0.3 BNA on the BTA interface.
 
* Switch HWP to OUT  during the day shift (inform Halls C and D about an hour beforehand)
 
* Switch HWP to OUT  during the day shift (inform Halls C and D about an hour beforehand)
 +
 +
=== <font color=green>Monday 15th August</font>  ===
 +
* Owl: Take production data on NH3(+) at 4 nA HWP OUT
 +
** Do a bleedthru test between the runs, and write down the amount in the run comment. Also, keep track of Hall C current: if it is off for a significant part of the run, record that as well. The default assumption is that they are running at 80 microAmps.
 +
**To account for the bleed thru problem, report 0.7 ABU and 0.3 BNA on the BTA interface.
 +
* Day: Continue taking data until MCC takes beam away for the bleedthru resolution work. When the beam is down, call target group for the target anneal, notify RadCon of the impending target work. 
 +
* Swing: Continue with production data on NH3 (hopefully)
 +
 +
=== <font color=green>Tuesday 16th August</font>  ===
 +
* Take data on C for the last 3 shifts before the pass change.
 +
  
 
<!--
 
<!--

Revision as of 18:06, 14 August 2022

[edit]


Clas12design.png