Difference between revisions of "The HPS Run Wiki"

From hps run
Jump to navigation Jump to search
Line 126: Line 126:
 
| valign=top width=50% |
 
| valign=top width=50% |
  
== Run Plan October 15 - 18, 2021 ==
+
== Run Plan October 19 - 22, 2021 ==
  
<!--* Hall-A will come up on swing shift, Wednesday, Oct.13day.
+
 
* Restore physics quality beam for the production running after Hall-A setup is done. Consult with MCC -  
+
* Restore physics quality beam for the production running at 1-pass, start from the tagger dump (see instructions on the right)  
** if changes to the beam are substantial, start from the tagger dump (see instructions on the right)
+
<!--
** if the setup of the beam delivery to Hall-A will not affect our beam, perform 2H02 harp scan when the beam is back to verify beam quality (see instructions) and proceed with the production data taking.
 
 
* Special runs: ''' After October 15 morning run ends'''
 
* Special runs: ''' After October 15 morning run ends'''
 
** Low Luminosity run: trigger '''file hps2021_v2_3.trg''', beam current ''' 60 nA''', target '''20 um''', '''4 hours'''.  
 
** Low Luminosity run: trigger '''file hps2021_v2_3.trg''', beam current ''' 60 nA''', target '''20 um''', '''4 hours'''.  
 
** Random Trigger Run. Trigger file '''hps2021_v2_2_30kHz_random.trg''' Target '''20 um''', Beam current '''120 nA''', Duration about '''1 hour with a good beam''' (Good means beam off should be less than 20% of the  
 
** Random Trigger Run. Trigger file '''hps2021_v2_2_30kHz_random.trg''' Target '''20 um''', Beam current '''120 nA''', Duration about '''1 hour with a good beam''' (Good means beam off should be less than 20% of the  
** Moeller run: Trigger file '''hps2021_v2_2_moller_LowLumi.trg''', Beam current '''50 nA''', Target '''8 um''', 200 M events.-->
+
** Moeller run: Trigger file '''hps2021_v2_2_moller_LowLumi.trg''', Beam current '''50 nA''', Target '''8 um''', 200 M events.
  
* '''Take production data taking''':  120 nA beam on the 20 um W target, PROD77 configuration, production trigger '''hps2021_v2_3.trg'''. Each run should last about 4 hours.
+
* '''Take production data taking''':  120 nA beam on the 20 um W target, PROD77 configuration, production trigger '''hps2021_v2_3.trg'''. Each run should last about 4 hours.-->
 +
* '''Setup production data taking''':  Start 50 nA beam on the 8 um W target, PROD77 configuration, production trigger '''hps_1.9_v2_3.trg'''. Turn ON detectors, bring SVT in to 0.5 mm. Start the run and check occupancies. Increase the beam current (up to 100 nA) until you reach occupancies of ~0.15% for L0t and L0b. End run and start a new one.
 +
* '''Take production data taking''': Beam current as found above, target 8 um W. Each run should last about 4 hours.
 
** if the beam is down for less than 40 min for reasons that will not alter the beam trajectory to Hall-B, do not end the run instead pause DAQ: <font color=red> From the main hps GUI, open 'DAQ Status', click 'Pause Triggers' and confirm </font>
 
** if the beam is down for less than 40 min for reasons that will not alter the beam trajectory to Hall-B, do not end the run instead pause DAQ: <font color=red> From the main hps GUI, open 'DAQ Status', click 'Pause Triggers' and confirm </font>
 
** Then retract the SVT to 3 mm, leave the bias voltages ON. After the beam is back and the halo and the detector rates look the same, bring the SVT to 0.5 mm and Resume DAQ: <font color=red> From the main hps GUI, open 'DAQ Status', click 'Resume Triggers' and confirm" </font>  
 
** Then retract the SVT to 3 mm, leave the bias voltages ON. After the beam is back and the halo and the detector rates look the same, bring the SVT to 0.5 mm and Resume DAQ: <font color=red> From the main hps GUI, open 'DAQ Status', click 'Resume Triggers' and confirm" </font>  

Revision as of 05:52, 19 October 2021


[edit]


Svtpic.png

Ecalpic.png