Difference between revisions of "Template:ShortTermSchedule-RGE"
Line 93: | Line 93: | ||
* HWP IN: [https://logbooks.jlab.org/entry/4194811 4194811] and [https://logbooks.jlab.org/entry/4195453 4195453] | * HWP IN: [https://logbooks.jlab.org/entry/4194811 4194811] and [https://logbooks.jlab.org/entry/4195453 4195453] | ||
* HWP OUT: [https://logbooks.jlab.org/entry/4195738 4195738] and [https://logbooks.jlab.org/entry/4195733 4195733] | * HWP OUT: [https://logbooks.jlab.org/entry/4195738 4195738] and [https://logbooks.jlab.org/entry/4195733 4195733] | ||
+ | |||
+ | === Upstream Halo counters === | ||
+ | If reading on the upstream halo counters exceeds 10, please, contact MCC. | ||
|} | |} |
Revision as of 11:20, 27 April 2024
Run Coordinator: Taisiya Mineeva (757) 575-7540
PDL: Nathan Baltzell (757) 876-1789, Office: x5902
Important Notes
- In case of medical or fire emergency, call 911 or 9-911 from a LANDLINE phone in the Counting House and inform the Crew Chief and RC.
- In case of evacuation of the Counting Room (e.g., due to a fire alarm), grab the shift expert phone and leave the room through the "EXIT" door leading to the parking lot. Do not leave through the hallway! Call the RC once outside so the latter will call MCC to turn the beam OFF to Hall B and inform other Hall B staff members.
- If you have symptoms or a positive COVID test, do NOT come to your shift - instead, inform the PDL and the RC and JLab medical services immediately to arrange replacements.
Please put all essential information on the main hall B log HBLOG. Some important alarms have been documented on HBRUN. Use the pulldown menu to choose where an error is reported.
Run PlanTake production data! Don't break anything! Keep an eye on the backgrounds, for example as seen in the halo counters, and on the 2C24 and 2H01 BPM positions. Both of these give confidence that the beam remains centered on the RGE target. Production data taking
In case of the need to manipulate the whole target system - cryotarget or solids - please contact the target experts.
DC firmware test plan (LD2 + Pb)1) Take one run each with 1M events with the trigger files and beam current at 70nA
2) Take one run with 500k events and beam current at 35nA with trigger file rge_inb_v1.0_200MeV_dcrb17_2.trg 3) Take one run with 500k events and beam current at 35nA with trigger file rge_inb_v1.0_200MeV_dcrb17_4.trg Before the last run call DC expert Florian so that he can change back the firmware after the last run is finished. Note:
LD2+Pb runs
For information on triggers, please see here: https://logbooks.jlab.org/entry/4267187 Long term run plan [1] |
ReferencesBPM PositionsThe most important BPMs to monitor are 2C24 and 2H01, from the point of view of assuring the beam remains centered on the RGE target. The values of the others can be influenced by other steering/focusing beamline elements.
Harp ScansFSD ThresholdsDo NOT change FSD settings without approval from RC or beamline expert!
Charge AsymmetryUpstream Halo countersIf reading on the upstream halo counters exceeds 10, please, contact MCC. |
General Reminders
|
DAQ Operation
|