Difference between revisions of "Template:ShortTermSchedule-RGD"
Jump to navigation
Jump to search
Line 30: | Line 30: | ||
== '''Run Plan for''' '''Oct. 11th to Oct. 13th''', 2023 == | == '''Run Plan for''' '''Oct. 11th to Oct. 13th''', 2023 == | ||
− | * '''Thursday, Oct. 12th, | + | * '''Thursday, Oct. 12th, Day Shift''': |
:• '''As soon as the MCC is ready to send the beam, please call Eugene'''. Please follow the steps to establish the beam to tagger dump, energize the tagger magnet, and take a harp scan in 2C21 and 2C24 using 5 nA beam current, then Eugene will take a Møller run with a 1/2-wave plate out. | :• '''As soon as the MCC is ready to send the beam, please call Eugene'''. Please follow the steps to establish the beam to tagger dump, energize the tagger magnet, and take a harp scan in 2C21 and 2C24 using 5 nA beam current, then Eugene will take a Møller run with a 1/2-wave plate out. | ||
:• Next, the collimator needs to be moved to a 20 mm position, mask beam halos, and send the beam to FC, then take a harp scan in 2H01 and compare their results with the reference one at the bottom of this page. | :• Next, the collimator needs to be moved to a 20 mm position, mask beam halos, and send the beam to FC, then take a harp scan in 2H01 and compare their results with the reference one at the bottom of this page. | ||
Line 39: | Line 39: | ||
::- ''DAQ Config.'': <tt>PROD66</tt>. <font color=blue> Follow the DAQ instructions below to change its configurations and load new trigger files.</font> | ::- ''DAQ Config.'': <tt>PROD66</tt>. <font color=blue> Follow the DAQ instructions below to change its configurations and load new trigger files.</font> | ||
::- ''Trigger file'': '''rgd_v1.0_no_DC.trg'''. <font color=blue><center>-----''If everything goes well, that should bring us to the Day shift''----</font> | ::- ''Trigger file'': '''rgd_v1.0_no_DC.trg'''. <font color=blue><center>-----''If everything goes well, that should bring us to the Day shift''----</font> | ||
− | * '''Thursday, Oct. 12th, Day Shift''': | + | * '''Thursday, Oct. 12th, Swing Shift''': |
+ | :• Continue the LD2 outbending production with 50 nA and 100 M runs by using the following configuration: | ||
+ | ::- ''DAQ Config.'': <tt>PROD66</tt>. <font color=blue> Follow the DAQ instructions below to change its configurations and load new trigger files.</font> | ||
+ | ::- ''Trigger file'': '''rgd_v1.0_no_DC.trg'''. <font color=blue><center>-----''If everything goes well, that should bring us to the Owl shift''----</font> | ||
+ | * '''Friday, Oct. 13th, Owl Shift''': | ||
+ | :• Continue the LD2 outbending production with 50 nA and 100 M runs by using the following configuration: | ||
+ | ::- ''DAQ Config.'': <tt>PROD66</tt>. <font color=blue> Follow the DAQ instructions below to change its configurations and load new trigger files.</font> | ||
+ | ::- ''Trigger file'': '''rgd_v1.0_no_DC.trg'''. <font color=blue><center>-----''If everything goes well, that should bring us to the Owl shift''----</font> | ||
+ | * '''Friday, Oct. 13th, Day Shift''': | ||
:• Depending on the status of the run during the shift changeover, please end the run once it reaches 100 M, then start the RICH threshold scans. | :• Depending on the status of the run during the shift changeover, please end the run once it reaches 100 M, then start the RICH threshold scans. | ||
:• Please ask MCC for 35 nA and take three 1h 30min runs with BEAM-ON and the following DAQ configuration and trigger files : | :• Please ask MCC for 35 nA and take three 1h 30min runs with BEAM-ON and the following DAQ configuration and trigger files : | ||
Line 56: | Line 64: | ||
::- ''DAQ Config.'': <tt>PROD66</tt>. <font color=blue> Follow the DAQ instructions below to change its configurations and load new trigger files.</font> | ::- ''DAQ Config.'': <tt>PROD66</tt>. <font color=blue> Follow the DAQ instructions below to change its configurations and load new trigger files.</font> | ||
::- ''Trigger file'': '''rgd_v1.0_no_DC.trg'''. <font color=blue><center>-----''If everything goes well, that should bring us to the Swing shift''----</font> | ::- ''Trigger file'': '''rgd_v1.0_no_DC.trg'''. <font color=blue><center>-----''If everything goes well, that should bring us to the Swing shift''----</font> | ||
− | * ''' | + | * '''Friday, Oct. 13th, Swing Shift''': |
:• Continue the LD2 outbending production with 50 nA and 100 M runs by using the following configuration: | :• Continue the LD2 outbending production with 50 nA and 100 M runs by using the following configuration: | ||
::- ''DAQ Config.'': <tt>PROD66</tt>. <font color=blue> Follow the DAQ instructions below to change its configurations and load new trigger files.</font> | ::- ''DAQ Config.'': <tt>PROD66</tt>. <font color=blue> Follow the DAQ instructions below to change its configurations and load new trigger files.</font> | ||
::- ''Trigger file'': '''rgd_v1.0_no_DC.trg'''. <font color=blue><center>-----''If everything goes well, that should bring us to the Owl shift''----</font> | ::- ''Trigger file'': '''rgd_v1.0_no_DC.trg'''. <font color=blue><center>-----''If everything goes well, that should bring us to the Owl shift''----</font> | ||
− | * ''' | + | * '''Saturday, Oct. 14th, Owl Shift''': |
:• Continue LD2 outbending production with 50 nA by taking 100 M runs with the following configuration: | :• Continue LD2 outbending production with 50 nA by taking 100 M runs with the following configuration: | ||
::- ''DAQ Config.'': <tt>PROD66</tt>. <font color=blue> Follow the DAQ instructions below to load new trigger file.</font> | ::- ''DAQ Config.'': <tt>PROD66</tt>. <font color=blue> Follow the DAQ instructions below to load new trigger file.</font> | ||
::- ''Trigger file'': '''rgd_out_v1.0.trg'''. <font color=blue><center>-----''If everything goes well, that should bring us to the Day shift''----</font> | ::- ''Trigger file'': '''rgd_out_v1.0.trg'''. <font color=blue><center>-----''If everything goes well, that should bring us to the Day shift''----</font> | ||
''' P.S.: At 7:30 AM, please call the engineering-on-call to inform him that we want to change the target position downstairs to the solid target position by the end of this run, and thus, we need him to come for controlled access. Don't end the run even if it exceeds 100 M until the engineer arrives'''. <font color=blue><center>-----''If everything goes well, that should bring us to the Day shift''----</font></center> | ''' P.S.: At 7:30 AM, please call the engineering-on-call to inform him that we want to change the target position downstairs to the solid target position by the end of this run, and thus, we need him to come for controlled access. Don't end the run even if it exceeds 100 M until the engineer arrives'''. <font color=blue><center>-----''If everything goes well, that should bring us to the Day shift''----</font></center> | ||
− | * ''' | + | * '''Saturday, Oct. 14th, Day Shift''': |
:• In parallel with controlled access, empty the cryo-target cell and insert CxC solid target in the beamline from the drop menu in the cryo-target GUI. For more details, please refer to the cryo-target and flag assembly: [https://docs.google.com/document/d/1kBNmLYg2gqa4XjWgMpbh0rBUxkSAupqdnMV4THepv7k/edit#heading=h.13kef88y2w8q manual]. | :• In parallel with controlled access, empty the cryo-target cell and insert CxC solid target in the beamline from the drop menu in the cryo-target GUI. For more details, please refer to the cryo-target and flag assembly: [https://docs.google.com/document/d/1kBNmLYg2gqa4XjWgMpbh0rBUxkSAupqdnMV4THepv7k/edit#heading=h.13kef88y2w8q manual]. | ||
:• Ask MCC for 50 nA and start CxC outbending production of 100 M runs with the following configuration: | :• Ask MCC for 50 nA and start CxC outbending production of 100 M runs with the following configuration: |
Revision as of 08:01, 12 October 2023
Run Coordinator: Susan Schadmand (757) 575-7540 (or 757-223-6213)
PDL: Nathan Baltzell (9-)757 876-1789 , x5902 office
RG/Analysis Coordinator (AC): Lamiaa El Fassi (630) 605-4259
Daily RC Meetings at 13:00 in CH Room 200C, and on ZOOM: URL Link (Meeting ID: 1611984219; Passcode: RGD-RC23), except on Wednesdays, which is on ZOOM ONLY @ 15:30 due to the conflict with the 13:30 MCC meeting.
Important Notes
- In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House
- 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.
- Remote shift: If needed, worker shifts can be taken from off-site. Inform the PDL and RC. Also, make sure that you follow the instructions under the "Worker Shift" Tab - you need some lead time to set up!
- Note to shift takers, please:
- ◊ Read the logbook, be aware of previous 24 hours
- ◊ Arrive at least 10 minutes early for shift change
- ◊ Refresh the run wiki pages; look over them every shift
- - Follow the expert/worker shift instructions
- ◊ Communicate with your co-shift person
- - The shift expert should know about and refer to logbook entries in their shift summary
- - The shift worker should discuss an issue with the shift expert before making extra logbook entries
- ◊ For advice, do not hesitate to call the RC first and foremost, day and night.
- ◊ For the required controlled access to change the LD2 and solid targets position down in the hall, please refer to this logbook entry #: 419613 for its requirement.
- ◊ Do NOT change FSD settings without approval from RC or beamline expert!
Run Plan for Oct. 11th to Oct. 13th, 2023
. DAQ configuration
Reference ValuesFSD Thresholds from RG-D
Harp Scan References from RG-D
IA for Q Asymmetry |
General Instructions:
Every Shift:
Every Run:
To access the Hall:
|