Difference between revisions of "Template:ShortTermSchedule-RGD"
Jump to navigation
Jump to search
Line 42: | Line 42: | ||
::- ''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></center> | ::- ''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></center> | ||
* '''Sunday, Oct. 7th, Owl Shift''': | * '''Sunday, Oct. 7th, Owl Shift''': | ||
− | :• | + | :• It depends on the status of the run from the previous shift; please continue the run until it reaches 100 M with CuSn target, then switch to Carbon. The previous shift leader will instruct the Owl shift expert on how to move the solid target from CuSn to CxC. For more details, please refer to the cryo-target and flag assembly [https://docs.google.com/document/d/1kBNmLYg2gqa4XjWgMpbh0rBUxkSAupqdnMV4THepv7k/edit#heading=h.13kef88y2w8q manual]. |
− | + | :• Once done, please call MCC to take the beam away, remove the beam blocker, and then ask for 50 nA and 100 M triggers with CxC target until the end of the Owl shift with the same DAQ and trigger configurations: | |
+ | ::- ''DAQ Config.'': <tt>PROD66</tt>. <font color=blue> Follow the DAQ instructions below to change its configurations.</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></center> | ||
* '''Sunday, Oct. 8th, Day Shift''': | * '''Sunday, Oct. 8th, Day Shift''': | ||
+ | :• It depends on the status of the run from the previous shift; please continue the run until it reaches 100 M with the CxC target, then we will switch to CuSn. | ||
:• '''Solid-target, CuSn Configuration, Luminosity Scan (cont'd)''': | :• '''Solid-target, CuSn Configuration, Luminosity Scan (cont'd)''': | ||
::‡'''P.S.: Before starting each luminosity scan run, please call ''in advance'' the SVT/MVT experts, Yuri and Rafo ''at least 45 min and 30 min, respectively'', to check the HV setting of MVT'''. | ::‡'''P.S.: Before starting each luminosity scan run, please call ''in advance'' the SVT/MVT experts, Yuri and Rafo ''at least 45 min and 30 min, respectively'', to check the HV setting of MVT'''. | ||
− | ::‡ Continue the luminosity scan with the specified trigger files but | + | ::‡ Continue the luminosity scan with the specified trigger files but and the following DAQ configuration: |
:::- ''DAQ Config.'': <tt>PROD66_PIN</tt>. <font color=blue> Follow the DAQ instructions below to change its configurations.</font> | :::- ''DAQ Config.'': <tt>PROD66_PIN</tt>. <font color=blue> Follow the DAQ instructions below to change its configurations.</font> | ||
− | ::‡ Ask MCC for | + | ::‡ Ask MCC to stop the beam, put the beam blocker in then ask for 130 nA and take a 25 M triggers run with the following trigger file: |
− | :::- '' | + | :::- ''Trigger file'': '''rgd_v1.0_no_DC_100nA.trg'''. <font color=blue> Follow the DAQ instructions below to load a new trigger file</font>. |
− | + | ::‡ Depending on the stability of detectors in the last CuSn higher beam currents run, we can take a 25 M run @ 150 nA with the same DAQ and trigger configurations. | |
− | + | :• In case 500 M triggers are already collected with CuSn and CxC Targets, we will flip the torus magnet polarity and change the target back to the LD2 position. | |
− | ::‡ Depending on the stability of detectors in the last CuSn higher beam currents run, we can take a 25 M run @ 150 nA. | + | :• ''To be continued and confirmed tomorrow morning during the Day shift''! |
− | :• | + | <!--:• Continue '''CuSn''' data-taking with 130 nA (''TBD after Lumi. scan is done'') and 100 M triggers runs until the end of the Swing shift. |
− | :• Continue '''CuSn''' data-taking with 130 nA (''TBD after Lumi. scan is done'') and 100 M triggers runs until the end of the Swing shift. | + | * '''Sunday, Oct. 8th, Swing Shift''':--> |
− | * '''Sunday, Oct. 8th, Swing Shift''': | + | :•<font color=Brown> Please call Eugene to change the torus polarity to the outbending configuration. In parallel, Engineering-on-call/Xiangdong Wei should be called so the engineer will perform a controlled access to move the target back to the LD2 position while the RC/Xiaodong will fill the LD2 cell. </font> |
− | :•<font color=Brown> Please call Eugene to change the torus polarity to the outbending configuration. In parallel, Engineering-on-call/Xiangdong Wei should be called so | + | :• Once the torus is ramped up to the outbending setting, take another 50 M triggers run @ 35 nA with LD2 for the trigger validation and ECAL calibration run requested by Valery and Cole, respectively: |
− | :• Once the torus is ramped up to the outbending setting, take another 50 M triggers run @ 35 nA with LD2 for the ECAL calibration | ||
::- ''DAQ Config.'': <tt>PROD66_PIN</tt>. <font color=blue> Follow the DAQ instructions below to change its configurations.</font> | ::- ''DAQ Config.'': <tt>PROD66_PIN</tt>. <font color=blue> Follow the DAQ instructions below to change its configurations.</font> | ||
::- ''Trigger file'': '''rgd_v1.0_no_DC.trg'''. | ::- ''Trigger file'': '''rgd_v1.0_no_DC.trg'''. | ||
Line 65: | Line 67: | ||
::- ''Trigger file'': '''rgd_out_v1.0.trg'''. | ::- ''Trigger file'': '''rgd_out_v1.0.trg'''. | ||
:• ''To-be-continued''.... | :• ''To-be-continued''.... | ||
− | <!--** Once the access is done, please ask MCC for 165 nA and take 100 M triggers runs with an empty target for a couple of hours with the same <tt>PROD66</tt> DAQ configuration, but the following trigger file: ''Trigger file'': '''rgd_v1.0_no_DC_100nA.trg'''-->. | + | <!--** Once the access is done, please ask MCC for 165 nA and take 100 M triggers runs with an empty target for a couple of hours with the same <tt>PROD66</tt> DAQ configuration, but the following trigger file: ''Trigger file'': '''rgd_v1.0_no_DC_100nA.trg'''<font color=blue><center>-----''If everything goes well, that should bring us to the Swing shift''----</font>-->. |
<!-- | <!-- | ||
Revision as of 15:51, 7 October 2023
Run Coordinator: Susan Schadmand (757) 575-7540
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.
Run Plan for Oct. 7th to Oct. 8th, 2023
. DAQ configuration
Reference ValuesFSD Thresholds from RG-D
Harp Scan References from RG-D |
General Instructions:
Every Shift:
Every Run:
To access the Hall:
|