https://wiki.jlab.org/clas12-run/api.php?action=feedcontributions&user=Carman&feedformat=atomclas12-run - User contributions [en]2024-03-29T00:10:20ZUser contributionsMediaWiki 1.35.7https://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7456Template:ShortTermSchedule-RGK2024-03-10T12:14:15Z<p>Carman: /* Run Plan: Mar. 9 - Mar. 11, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 10 - Mar. 11, 2024''' ==<br />
<br />
'''Production Running ... to the end!!'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.<br />
- Turn all detectors off and put BMT HV in safe mode<br />
- Ramp torus and solenoid to zero field (contact Eugene to do this)<br />
- Call to put Hall B in Restricted Access<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7455Template:ShortTermSchedule-RGK2024-03-10T00:19:53Z<p>Carman: /* Run Plan: Mar. 8 - Mar. 11, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 9 - Mar. 11, 2024''' ==<br />
<br />
'''Production Running ... to the end!!'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.<br />
- Turn all detectors off and put BMT HV in safe mode<br />
- Ramp torus and solenoid to zero field (contact Eugene to do this)<br />
- Call to put Hall B in Restricted Access<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7454Template:ShortTermSchedule-RGK2024-03-08T21:56:02Z<p>Carman: </p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 8 - Mar. 11, 2024''' ==<br />
<br />
'''Production Running ... to the end!!'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.<br />
- Turn all detectors off and put BMT HV in safe mode<br />
- Ramp torus and solenoid to zero field (contact Eugene to do this)<br />
- Call to put Hall B in Restricted Access<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Run_Group_K&diff=7453Run Group K2024-03-08T12:32:01Z<p>Carman: </p>
<hr />
<div><!--####################################### General ########################################--><br />
= General =<br />
<br />
{| {{TableStyle1}}<br />
<br />
| valign=top |<br />
==General==<br />
===[https://logbooks.jlab.org/book/hallb Logbook]===<br />
===[http://www.jlab.org/Hall-B/shifts Shift Schedule]===<br />
===[https://docs.google.com/spreadsheets/d/1p_NaWUtR5q7lrO3np076EcClwUNqVzb2NymTndiqI8k/edit?usp=sharing Run Coordinator Schedule]===<br />
===[https://www.jlab.org/Hall-B/run-web/rgk/ESAD_HallB-CLAS12_rgK.pdf ESAD], [https://www.jlab.org/Hall-B/run-web/rgk/COO_HallB-CLAS12_RGK.pdf COO], [https://www.jlab.org/Hall-B/run-web/rgk/RSAD_HallB-CLAS12_rgk.pdf RSAD]===<br />
===[https://logbooks.jlab.org/checklists/151 Shift Checklist] ===<br />
===[https://ace.jlab.org/btm/timesheet/eb Beam Time Accounting]===<br />
* '''[https://ace.jlab.org/cdn/doc/btm/userguide.pdf Beam Time Accounting User Guide]'''.<br />
===[https://accweb.acc.jlab.org/hco/readiness Hot Checkout]===<br />
<br />
| valign=top |<br />
==Manuals==<br />
=====Systems=====<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/beamline/manual/beamline_manual.pdf Beamline]<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/torus/Hall_B_Torus_Power-Up_and_Power-Down_Procedure.pdf Torus]<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/torus/Hall_B_Solenoid_Power-Up_and_Power-Down_Procedure.pdf Solenoid]<br />
* [https://docs.google.com/document/d/1kBNmLYg2gqa4XjWgMpbh0rBUxkSAupqdnMV4THepv7k/edit#heading=h.13kef88y2w8q Cryotarget]<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/daq/opman_master.pdf DAQ]<br />
* [[Media:clas12controls_shift.pdf|Slow Controls]]<br />
=====Detectors=====<br />
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/dc/Drift-chamber-operating-procedure.pdf DC]<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/ftof/ftof_manual.pdf FTOF]<br />
* [https://clasweb.jlab.org/wiki/images/a/a2/Ec_manual.pdf ECAL]<br />
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/ltcc/manual/ltcc_manual.pdf LTCC]<br />
* [https://clasweb.jlab.org/wiki/images/f/f1/HTCC_MANUAL.pdf HTCC]<br />
* RICH: [https://github.com/JeffersonLab/clas12-manuals/raw/master/rich/RICH_Manual.pdf Expert] [https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf Shift]<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/ctof/ctof_manual.pdf CTOF]<br />
* [https://clasweb.jlab.org/wiki/images/9/97/Ops_manual_cnd.pdf CND]<br />
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/svt/svt_operation_manual.pdf SVT]<br />
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/mm/Documentation_Shifters_MVT.pdf MVT] and its [https://wiki.jlab.org/clas12-run/images/b/bf/MVT_for_Dummies.pdf Turn-on procedure]<br />
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/ft/FT-Manual.pdf FT]<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/band/band_om.pdf BAND]<br />
<br />
=====Software=====<br />
* [https://wiki.jlab.org/clas12-run/images/c/c9/CedManual.pdf CED]<br />
* [https://wiki.jlab.org/clas12-run/images/f/fd/CLAS12Mon_documentation.pdf mon12]<br />
<br />
| valign=top |<br />
==Procedures==<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam]<br />
* [[Media:clas12moller.pdf|Performing M&oslash;ller Runs]]<br />
* [[Media:HarpScanManual.pdf|Performing Harp Scans]]<br />
* [https://wiki.jlab.org/hps-run/images/0/0c/Accessing_the_tunnel.pdf Accessing the Tunnel/Hall]<br />
<br />
==Logbooks==<br />
<font size=3><br />
* [https://logbooks.jlab.org/book/elog MCC]<br />
* [https://logbooks.jlab.org/book/halog Hall-A]<br />
* [https://logbooks.jlab.org/book/hblog Hall-B]<br />
* [https://logbooks.jlab.org/book/hclog Hall-C]<br />
* [https://logbooks.jlab.org/book/hdlog Hall-D]<br />
</font><br />
<br />
|}<br />
<br />
= Phone Numbers =<br />
<!--####################################### PHONE NUMBERS #############################################--><br />
{{PhoneNumbers}}<br />
<!--- JUST MODIFY AND SAVE ANYTHING IN THIS COMMENT BLOCK TO FORCE A REFRESH OF THE PHONE NUMBERS TEMPLATE! --><br />
<br />
<!--####################################### Short Term Schedule #############################################--><br />
= Short Term Schedule =<br />
<br />
'''[https://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&action=edit Click to Edit]''' solely this tab. P.S.: You must click on the top Edit, next to Read, followed by "Save changes" to force the current page to refresh. <br><br />
<br />
{{ShortTermSchedule-RGK}}<br />
<br />
<!--####################################### GENERAL INFORMATION #############################################--><br />
= General Information =<br />
<br />
This tab contains information on <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
*'''Beam Restoration'''<br />
<br />
== '''Recent Changes''' ==<br />
<br />
=== New '''MVT LV''' Reboot Procedure ===<br />
See '''https://logbooks.jlab.org/entry/4217011''' for detailed information on rebooting the MVT LV when observing a drop in BMT strip occupancies. This gets done upon request of DAQ or MVT expert only.<br />
* Turn '''LV OFF from MVT Overview->Low Voltage->MVT-All'''. LV status indicators should change from green to black; <br />
* '''Wait 20 seconds''', then '''turn LV back from the same menu'''.<br />
* In the alarm handler, with a 2-minute alarm delay, there can be an alarm "NActiveCrates", the status is also seen on the MVT Overview GUI. This alarm will be cleared 2 min after LV is turned back ON. <br />
* Reboot mvt1, mvt2, and mvt3 ROCS. <br />
* Start a run with restart DAQ (Cancel &rarr; Reset &rarr; Configure &rarr; Download &rarr; Prestart &rarr; Go). <br />
* '''If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert'''. <br />
<br />
=== RICH issues ===<br />
* The RICH fibers alarm leads to web guidance aka logbook entry [https://logbooks.jlab.org/entry/3562273 3562273 - RICH recovery procedure]. <br />
* Check the RICH manual for the current guidance: '''https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf'''<br />
* See below for current issues<br />
<br />
=== Rapid/Controlled Access to the Hall ===<br />
* Ask MCC to stop the beam. Wait for the beacon to stop flashing (15-20 minutes) before access. Rapid access is controlled access without RadCon.<br />
* After higher beam current or a Moller run, the beacon will not stop flashing anytime soon. Then, escorted access, viz the ARM, is needed. In that case, keep the beam until the ARM arrives at the Counting House.<br />
<br />
=== 24/7 ZOOM connection for Counting House ===<br />
* Click on [https://jlab-org.zoomgov.com/j/1618614939 https://jlab-org.zoomgov.com/j/1618614939], included in "Remote Shifts" in tab "Shift Worker" <br />
* choose the option to "'''join from browser'''" (''Chrome is recommended'') and ignore all other messages to update the ZOOM APP in the pop-up windows,. <br />
* Enter the passcode from the logbook entry in tab "Shift Worker"<br />
<br />
== '''Current Issues''' == <br />
<br />
=== Lights in the Hall ===<br />
The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF because of light leaks of some of the detectors. If these lights are switched on during an access, they '''should be switched off when leaving the Hall'''. <br />
* Refer to these photos: ON: [https://logbooks.jlab.org/entry/3825712], OFF: [https://logbooks.jlab.org/entry/3825731]<br />
* We have a '''new dome light switch outside of the hall''' in the labyrinth. See logbook entry: https://logbooks.jlab.org/entry/4204460<br />
* When the dome lights are switched off, they cannot be turned back on immediately, they require 10-15 min to cool down.<br />
<br />
=== Beamline ===<br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
*'''After the HWP change''' <br />
** The absolute values of the SLM and FCUP '''charge asymmetry''' (Q-Asym) should be less than 0.1%. If they are not, contact the Beamline Expert.<br />
** Start a new run<br />
* '''Tagger Magnet Procedure:''' If the tagger magnet needs to be turned off, tell the operator to '''ONLY''' use '''the script for degaussing, NEVER do it "by hand"!''' The latter method might/will trip the circuit breaker for the power supply in the Hall.<br />
<br />
=== BMT / SVT ===<br />
* If new hot channels appear, '''call the SVT/MM expert Yuri Gotra''' (757-541-7539). These channels need to be addressed by the expert.<br />
* '''BMT HV trips''': no screenshots are necessary, power-cycle the channel HV '''as fast as possible''' (the ''underlying script will take care of ramping it up''), note the information in the shift summary. If the same channel trips frequently, ask the expert on call for guidance.<br />
* BMT HV S1 L2 STRIP in safe mode (low voltage) by expert - appears blue in MVT overview<br />
* BMT HV S1 L5 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview<br />
* BMT HV S2 L6 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview<br />
<br />
=== CND ===<br />
* CAMAC crate alarm: <br />
** CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, can be done via the alarm handler. <br />
** After reboot, the CFD thresholds need to be set by running a script, see page 12 in the CND manual at tab "General", https://clasweb.jlab.org/wiki/images/9/97/Ops_manual_cnd.pdf<br />
<br />
=== DAQ ===<br />
* Some ROCs keep printing error messages while functioning properly; please see their list in this logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] to avoid unnecessary reboots since the printout in the ROC terminal won't change. The message will appear in the DAQ run control if they get disconnected! <br />
* <font color=red>'''NEW STANDARD''' end and start of the run:</font> End run, Cancel, Reset, <u> Download</u> , Prestart, Go. This will ensure proper compression of the FADCs and therefore a smaller data rate.<br />
* roc reboot instructions:<br />
** To reboot i.e. adcecal1, type on a clasrun terminal: clasrun> roc_reboot adcecal1<br />
** To check that the crate is back alive, type:clasrun> ping adcecal1<br />
** The ping will start to answer as soon as the crate communicates again. <br />
<br />
=== DC ===<br />
* Make sure to log every DC trip in the shift summary. Make sure to list WHERE and why, possibly, the trip occurred.<br />
<br />
=== ECAL/PCAL ===<br />
* "ECAL_SEC6_UO26 Noisy" https://logbooks.jlab.org/entry/4241957<br />
* "PCAL_HV_SEC2_U25 turned off" https://logbooks.jlab.org/entry/4247187, https://logbooks.jlab.org/entry/4247400<br />
<br />
=== FTOF ===<br />
* FTOF S2 Paddle 19-left and S4 Paddle 16-left are known to be "weak" channels that tend to come and go depending on torus polarity and rates. This cannot be fixed during this run period; see https://logbooks.jlab.org/entry/4219555 and https://logbooks.jlab.org/entry/4219876.<br />
* "FTOF HV Adjustment - S5 P2 2R" https://logbooks.jlab.org/entry/4249754<br />
<br />
=== RICH ===<br />
* '''Known problematic PMTs and tile''':<br />
** You don't need to report about it.<br />
** PMT 2 (sector 1) and PMT 92 (sector 4) are not completely dead and may be visible depending on statistics.<br />
** Problematic tiles and PMTs:<br />
*** Sector 1 Tile 21 dead (PMT 55,56,57)<br />
*** Sector 1 Tile 1 PMT 2<br />
*** Sector 4 Tile 34 PMT 92<br />
<br />
== '''Beam Restoration''' == <br />
<br />
* Study the manual: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam]. If you do not feel confident to do this by yourself, contact the Beamline Expert.<br />
<br />
* Find all Reference values on the white board at tab Short_Term_Schedule<br />
<br />
=== Restoring Beam after Short Downtime ===<br />
<br />
* Ask for 5 nA beam current and check the 2C24A and 2H01 beam (x, y) positions against the Reference Values (tab "Short Term Schedule") after <br />
** beam steering or orbit change<br />
** change in beam current, e.g., after a target change<br />
** If BPM 2C24A and 2H01 positions are off, (not within +/-0.1 mm), ask MCC to bring them to the reference values<br />
<br />
=== Beam Tuning to Tagger Yoke Dump ===<br />
<br />
Study the manual: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam]. <br />
* Contact Eugene Pasyuk if issues arise.<br />
<br />
* Ask MCC to energize the tagger magnet<br />
:- blank collimator<br />
:- beam type "Photon"<br />
<br />
* All CLAS12 detectors HV off (BMT HV in safe mode)<br />
<br />
* Ask MCC to mask the beam halo counters (FSDs: Upstream, Midstream, Downstream, BOM) <br />
* Ask MCC for 5 nA beam current and make sure the Orbit Locks are OFF;<br />
* If necessary, ask MCC to bring the 2C21A and 2C24A beam positions to the Reference Values<br />
* Take harp scans<br />
:- at Harp 2C21A (Upstream Right Counter)<br />
:- at Tagger Harp 2C24A Upstream Right Counter)<br />
* If the beam trips, abort the scan and restart. The beam must be on during the scan, otherwise the fit to the beam profile will not work. <br />
* Compare the results with the Harp Scan References <br />
* The fit ranges might need to be adjusted manually to assess the fit results<br />
<br />
* If good, log the new scan results.<br />
<br />
=== M&oslash;ller run ===<br />
<br />
Follow the standard procedure as described in the manual [https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf Performing M&oslash;ller Runs].<br />
* Contact Nathan Baltzell if issues arise<br />
<br />
A few points to note:<br />
* '''Request 20 nA''' , Orbit Locks should be off<br />
* The BPMs 2C21 and 2C24A may be out of range after the M&oslash;ller configuration. <br />
* Keep running until the polarization uncertainty is < 1.5%<br />
<br />
=== Beam Tuning to Faraday Cup ===<br />
<br />
Study the manual: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam], and take into account the first steps mentioned therein. <br />
<br />
This is typically done after tuning to the tagger dump (and possibly taking a Moller run).<br />
<br />
* All CLAS12 detectors HV off (BMT HV in safe mode)<br />
<br />
* Ask MCC to de-energize the tagger magnet<br />
:- 20 mm collimator<br />
:- beam type electron<br />
:- beam blocker out<br />
* If initial beam tune, target should be "Empty"<br />
* Ask MCC to unmask beam halos<br />
* Set the halo counter FSD thresholds to 1 MHz and the integration time interval to 50 milliseconds<br />
* Insert the Downstream Viewer, Chromax, in the beamline<br />
* Ask MCC for 5 nA beam current<br />
* If necessary, ask MCC to bring the beam positions at 2C24A and 2H01 to the Reference Values<br />
* Take a harp scan at 2H01 (Midstream Left)<br />
* If the beam trips, abort and restart. The beam must be on during the scan, otherwise the fit to the beam profile will not work. <br />
* Compare the results with the Harp Scan References <br />
* If good, log the new scan results.<br />
<br />
Once done and before resuming the production data-taking:<br />
* Retract the Downstream Viewer from the beamline<br />
* Put the FSDs thresholds and integration time to their reference values<br />
* Turn all detector HV ON, for MVT "HV ON - Full Voltage"<br />
* MCC might need to adjust the beam positions after going to the production beam current.<br />
<br />
<!--####################################### Shift Expert ################################################--><br />
= Shift Expert =<br />
<br />
Come to your shift in time for the '''shift change''', 10-15 minutes before the start of your shift. <br />
* If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
Follow the '''Short Term Schedule'''<br />
* The RC must be notified before changing run conditions<br />
<br />
Operate the '''Data Acquisition'''<br />
<br />
Take action on and log '''alarms'''<br />
<br />
At '''the end of the shift''', submit the '''strip charts''' to the logbook <br />
* If they are not up already: (CS-Studio &rarr; Tools &rarr; Strip Charts &rarr; livePlot)<br />
* Right click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters"<br />
* Choose a '''time-span width of 10 hours''' (right-click below x-axis)<br />
* <font color=red> To make a logbook entry:</font><br />
:- Right click within the grid of one of the charts, choose "Make Logbook Entry"<br />
:- The title of the logbook entry can be changed, eg to Strip charts<br />
:- Un-click ELOG, select HBLOG, and click on "Make Entry" to submit<br />
<br />
'''Communicate''' with your co-shift person:<br />
* Remind them to read the tab 'Shift Worker'.<br />
* Discuss any issues with the shift worker before making extra logbook entries.<br />
* Remind the shift worker of the '''end-of-shift Checklist'''.<br />
* <font color=red> Use the CS-Studio '''Logbook entry tool''' for all screen shots (but the strip charts)!</font><br />
* Note that the Logbook Entry tool puts the entry in the HBRUN logbook by default. Other logbooks can be added or selected from the drop down menu. <br />
<br />
Check for and read any comments to '''logbook entries''' made during your shift.<br />
<br />
Keep your '''shift summary''' up to date in HBLOG. Record all significant happenings. <br />
* Refer to relevant logbook entries in the shift summary.<br />
* Include a run list for the shift with relevant run information.<br />
<br />
Ensure that all '''monitoring plots''' and are logged and checked against the reference plots for every single run.<br />
* Both, you and the shift worker should run mon12 and '''reset & check spectra frequently'''.<br />
<br />
* If the worker shift is remote, maintain communication over Zoom. <br />
<br />
* If you have any other questions or uncertainties about what to do, call the RC.<br />
<br />
The shift worker (if in person) should log the '''clas12online'' reconstruction plots at the end of a run. Running the program on more than one CH computer has been causing problems.<br />
<br />
In case of '''RICH issues''', check the RICH manual for the current guidance: https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf<br />
<br />
'''New MVT LV Reboot Procedure''' can be found at tab 'GENERAL INFORMATION'.<br />
<br />
'''[https://ace.jlab.org/btm Fill out BTA]''' hourly;<br />
* Accelerator beam time (do not change these values):<br />
** ABU: acceptable beam used <br />
** BANU: beam acceptable but not used (should be reflected in our PCC and UED)<br />
** BNA: beam not acceptable (e.g., tuning, drifting, not focused)<br />
** ACC: Accelerator Configuration Change (e.g., pass change)<br />
** OFF: Accelerator is down<br />
* Experiment beam time (do change these values):<br />
** ER: Experiment ready (should be 60 minutes - PCC - UED)<br />
** PCC: Planned configuration change (when the beam is masked while radiators are moved, target change, DAQ (stopping/starting runs, tests, etc.)<br />
** UED: Unplanned experiment down (hardware failure, DAQ crashes, our problems, ...)<br />
** ''Exception'': ''BANU, due to time spent on beam tuning and BPM checks after beam down, should be counted as ER on our side''.<br />
* Enter fields at the "Shift Information" tab.<br />
* You must save at 7:00, 15:00, and 23:00, to send info to MCC. To see the save button, click 'edit all' or 'edit cc hours.' <br />
* Acknowledge the popup error message about the last hour not being completed by clicking OK.<br />
* Sign, viz log completed 8-hour sheet. <br />
* '''Note: we can change the time sheet up to 48 hours after completion.''' <br />
<br />
<!--####################################### Shift Worker ################################################--><br />
= Shift Worker =<br />
<br />
Come to your shift in time for the '''shift change''', 10-15 minutes before the start of your shift;<br />
* If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
Discuss any issue with the shift expert before making extra logbook entries; ask the shift expert to note the ongoing issue in the shift summary.<br />
<br />
<font color=red> Use the CS-Studio '''Logbook entry tool''' for all screen shots (but the strip charts)! </font><br />
<br />
=== Frequently ===<br />
<br />
Reset and check mon12 histograms frequently, preferably each 1h<br />
* Note that some plots have radio buttons at the bottom to choose the sector. Remember to cycle through and check all sectors.<br />
<br />
=== Once per run ===<br />
<br />
Note that the CS-Studio '''Logbook Entry tool''' puts the entry in the HBRUN logbook by default. Other logbooks can be added or selected from the drop down menu. <br />
<br />
Using the Logbook Entry tool, submit EPICS '''screenshots''' to the HBRUN logbook (one logbook entry) '''with beam ON'''<br />
# Beamline overview (remote shift: in VNC or [https://hallbopi.jlab.org/webopi3.3/w?opi=beamline/clas12-web.opi Web Browser])<br />
# DAQ status<br />
# CLAS12 trigger rates <br />
<br />
Upload '''mon12''' monitoring plots to the logbook with sufficient statistics and compare them to the reference and recent uploads (see {{#switchtablink:Monitoring|Monitoring}} tab).<br />
<br />
At the '''end of the run''', submit the '''strip charts''' to the logbook <br />
* If they are not up already: (CS-Studio &rarr; Tools &rarr; Strip Charts &rarr; livePlot)<br />
* Right click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters"<br />
* Choose a '''time-span width of 4 hours''', compatible with the run duration (right-click below x-axis)<br />
* <font color=red> To make a logbook entry:</font><br />
:- Right click within the grid of one of the charts, choose "Make Logbook Entry"<br />
:- The title of the logbook entry can be changed, eg to Strip charts<br />
:- Un-click ELOG, select HBLOG, and click on "Make Entry" to submit<br />
<br />
At the '''end of the run''', upload the '''[https://github.com/JeffersonLab/caos/tree/main#readme clas12online]''' plots to the logbook.<br />
* The program can continue through a standard end/start of a run. However, after a DAQ restart, you must back out and restart clas12online.<br />
* If the DAQ has to be restarted, you can still make the upload before backing out.<br />
<br />
=== Once per shift ===<br />
<br />
Fill the '''[https://logbooks.jlab.org/checklists/151 shift checklist]''';<br />
* During production, get relevant values from the epics screens Beamline Overview, CLAS12 DAQ Status and CLAS12 Trigger;<br />
* During extended downtime, get relevant values from the latest EPICS screenshots that you made during production <br />
<br />
== For Remote Shifts ==<br />
<font color=red>'''Please inform the PDL that your shifts will be remote.''' </font color=red> <br />
Remote shifts are listed [[upcoming-remote-shifts|here]]<br />
<br />
You must test your setup, including Zoom and VNC connections, at least 24 hours before your first shift!<br />
* Zoom for 24-7 communication with Counting House:<br />
** In the Zoom app: [https://jlab-org.zoomgov.com/j/1618614939 https://jlab-org.zoomgov.com/j/1618614939]<br />
** Or in a web browser: [https://jlab-org.zoomgov.com/wc/1618614939/join?pwd=U003MnRuNVdiU1EzaFpXV0JuNWV1Zz09 https://jlab-org.zoomgov.com/wc/1618614939/join?pwd=U003MnRuNVdiU1EzaFpXV0JuNWV1Zz09]<br />
** The passcode is required and contained in [https://logbooks.jlab.org/entry/4158818 this log entry]<br />
** Remind the expert in the counting house to restart their ZOOM, if necessary<br />
* Remote VNC connection instructions: https://logbooks.jlab.org/entry/3906039<br />
* '''If you mistyped''' (username, pincode, passcode,...) a string of numbers will appear with text asking you to respond to this challenge. Back out with ctrl_c and you get another try! After N+1 mistypes you will be locked out. For several hours after that you will not even be able to get to the public JLab webpages.<br />
** All necessary applications should be available from the desktop menu (left/right click on the desktop)<br />
** EPICS GUIs should be accessed '''ONLY''' via the desktop menu or by running <tt>clascss-remote</tt>.<br />
<!--* [https://userweb.jlab.org/~baltzell/clas12/shift/remote-demo.mp4 Remote Demonstration Video (150 MB)]--><br />
** Some charts are also accessible via web browser: [https://epicsweb.jlab.org/wave/?myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Upstream+and+Midstream+Halo+Counters&fullscreen=false&layoutMode=2&viewerMode=2&pv=scaler_cS3b&pv=scaler_cS4b&pv=scaler_cS6b&pv=scaler_cS12b&pv=scaler_cS13b&pv=scaler_cS14b&pv=scaler_cS15b&scaler_cS3blabel=scaler_cS3b&scaler_cS3bcolor=%23a6cee3&scaler_cS3byAxisLabel=Rate++%28Hz%29&scaler_cS3byAxisMin=&scaler_cS3byAxisMax=&scaler_cS3byAxisLog&scaler_cS3bscaler=&start=2020-08-08+09%3A02%3A36&end=2020-08-08+09%3A07%3A36&scaler_cS4blabel=scaler_cS4b&scaler_cS4bcolor=%231f78b4&scaler_cS4byAxisLabel=&scaler_cS4byAxisMin=&scaler_cS4byAxisMax=&scaler_cS4byAxisLog=&scaler_cS4bscaler=&scaler_cS5byAxisLabel=&scaler_cS5byAxisMin=&scaler_cS5byAxisMax=&scaler_cS5byAxisLog=&scaler_cS5bscaler=&scaler_cS6blabel=scaler_cS6b&scaler_cS6bcolor=%2333a02c&scaler_cS6byAxisLabel=&scaler_cS6byAxisMin=&scaler_cS6byAxisMax=&scaler_cS6byAxisLog=&scaler_cS6bscaler=&scaler_cS7byAxisLabel=&scaler_cS7byAxisMin=&scaler_cS7byAxisMax=&scaler_cS7byAxisLog=&scaler_cS7bscaler=&scaler_cS12blabel=scaler_cS12b&scaler_cS12bcolor=%23e31a1c&scaler_cS12byAxisLabel=&scaler_cS12byAxisMin=&scaler_cS12byAxisMax=&scaler_cS12byAxisLog=&scaler_cS12bscaler=&scaler_cS13blabel=scaler_cS13b&scaler_cS13bcolor=%23fdbf6f&scaler_cS13byAxisLabel=&scaler_cS13byAxisMin=&scaler_cS13byAxisMax=&scaler_cS13byAxisLog=&scaler_cS13bscaler=&scaler_cS14blabel=scaler_cS14b&scaler_cS14bcolor=%23ff7f00&scaler_cS14byAxisLabel=&scaler_cS14byAxisMin=&scaler_cS14byAxisMax=&scaler_cS14byAxisLog=&scaler_cS14bscaler=&scaler_cS15blabel=scaler_cS15b&scaler_cS15bcolor=%23cab2d6&scaler_cS15byAxisLabel=&scaler_cS15byAxisMin=&scaler_cS15byAxisMax=&scaler_cS15byAxisLog=&scaler_cS15bscaler= Upstream/Midstream Halo Counters], [https://epicsweb.jlab.org/wave/?myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Downstream+Halo+Counters&fullscreen=false&layoutMode=2&viewerMode=2&pv=scalerS8b&pv=scalerS9b&scalerS8blabel=scalerS8b&scalerS8bcolor=%23a6cee3&scalerS8byAxisLabel=Rate++%28Hz%29&scalerS8byAxisMin=&scalerS8byAxisMax=&scalerS8byAxisLog&scalerS8bscaler=&pv=scalerS10b&pv=scalerS11b&scalerS9blabel=scalerS9b&scalerS9bcolor=%231f78b4&scalerS9byAxisLabel=&scalerS9byAxisMin=&scalerS9byAxisMax=&scalerS9byAxisLog=&scalerS9bscaler=&scalerS10blabel=scalerS10b&scalerS10bcolor=%23b2df8a&scalerS10byAxisLabel=&scalerS10byAxisMin=&scalerS10byAxisMax=&scalerS10byAxisLog=&scalerS10bscaler=&scalerS11blabel=scalerS11b&scalerS11bcolor=%2333a02c&scalerS11byAxisLabel=&scalerS11byAxisMin=&scalerS11byAxisMax=&scalerS11byAxisLog=&scalerS11bscaler= Downstream Halo Counters], [https://epicsweb.jlab.org/wave/?start=2020-07-08+16%3A50%3A02&end=2020-07-08+16%3A55%3A02&myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Beam+Currents&fullscreen=false&layoutMode=2&viewerMode=2&pv=IPM2C21A&pv=IPM2C24A&pv=scaler_calc1b&IPM2C21Alabel=IPM2C21A&IPM2C21Acolor=%23a6cee3&IPM2C21AyAxisLabel=Beam+Current+%28nA%29&IPM2C21AyAxisMin=0&IPM2C21AyAxisMax=300&IPM2C21AyAxisLog&IPM2C21Ascaler=&scaler_calc1blabel=Faraday+Cup&scaler_calc1bcolor=%23b2df8a&scaler_calc1byAxisLabel=&scaler_calc1byAxisMin=&scaler_calc1byAxisMax=&scaler_calc1byAxisLog&scaler_calc1bscaler= Beam Currents], [https://epicsweb.jlab.org/wave/?start=2020-08-03+12%3A30%3A57&end=2020-08-03+12%3A35%3A57&myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=BPM+Positions+%28Y-Axis+is+mean+%2B%2F-+0.5+mm%29&fullscreen=false&layoutMode=3&viewerMode=2&pv=IPM2C24A.XPOS&pv=IPM2C24A.YPOS&pv=IPM2H01.XPOS&pv=IPM2H01.YPOS&IPM2C24A.XPOSlabel=IPM2C24A.XPOS&IPM2C24A.XPOScolor=%23e31a1c&IPM2C24A.XPOSyAxisLabel=&IPM2C24A.XPOSyAxisMin=-2.0&IPM2C24A.XPOSyAxisMax=+1.0&IPM2C24A.XPOSyAxisLog&IPM2C24A.XPOSscaler=&IPM2C24A.YPOSlabel=IPM2C24A.YPOS&IPM2C24A.YPOScolor=pink&IPM2C24A.YPOSyAxisLabel=&IPM2C24A.YPOSyAxisMin=-2.0&IPM2C24A.YPOSyAxisMax=1.0&IPM2C24A.YPOSyAxisLog&IPM2C24A.YPOSscaler=&IPM2H01.XPOSlabel=IPM2H01.XPOS&IPM2H01.XPOScolor=darkgreen&IPM2H01.XPOSyAxisLabel=&IPM2H01.XPOSyAxisMin=-2.0&IPM2H01.XPOSyAxisMax=1.0&IPM2H01.XPOSyAxisLog&IPM2H01.XPOSscaler=&IPM2H01.YPOSlabel=IPM2H01.YPOS&IPM2H01.YPOScolor=lightgreen&IPM2H01.YPOSyAxisLabel=&IPM2H01.YPOSyAxisMin=-2.0&IPM2H01.YPOSyAxisMax=1.0&IPM2H01.YPOSyAxisLog&IPM2H01.YPOSscaler=#a6cee3&IPM2C24A.XPOSyAxisLabel=2C24+X+(mm)&IPM2C24A.XPOSyAxisMin=-1.5&IPM2C24A.XPOSyAxisMax=-0.5&IPM2C24A.XPOSyAxisLog&IPM2C24A.XPOSscaler=&IPM2C24A.YPOSlabel=IPM2C24A.YPOS&IPM2C24A.YPOScolor=%231f78b4&IPM2C24A.YPOSyAxisLabel=2C24+Y+(mm)&IPM2C24A.YPOSyAxisMin=0.3&IPM2C24A.YPOSyAxisMax=1.3&IPM2C24A.YPOSyAxisLog&IPM2C24A.YPOSscaler=&IPM2H01.XPOSlabel=IPM2H01.XPOS&IPM2H01.XPOScolor=pink&IPM2H01.XPOSyAxisLabel=2H01+X+(mm)&IPM2H01.XPOSyAxisMin=-0.6&IPM2H01.XPOSyAxisMax=0.4&IPM2H01.XPOSyAxisLog&IPM2H01.XPOSscaler=&IPM2H01.YPOSlabel=IPM2H01.YPOS&IPM2H01.YPOScolor=darkred&IPM2H01.YPOSyAxisLabel=2H01+Y+(mm)&IPM2H01.YPOSyAxisMin=0.4&IPM2H01.YPOSyAxisMax=1.4&IPM2H01.YPOSyAxisLog&IPM2H01.YPOSscaler= BPM Positions]<br />
<br />
<br />
<!--####################################### Run Coordinator ################################################--><br />
= Run Coordinator =<br />
<br />
Check the '''upcoming shifts''', and if necessary, coordinate with the PDL to contact shift takers about their training and site access status.<br />
<br />
'''Remote shifts''' are listed [[Upcoming-remote-shifts|here]].<br />
<br />
'''Backup shift personnel''' is listed [https://jeffersonlab-my.sharepoint.com/:x:/r/personal/baltzell_jlab_org/Documents/Backup%20Shifters.xlsx?d=wf18dc5909cf84424840d73cc9bd8ce8e&csf=1&web=1&e=QwY1fs here].<br />
<br />
'''Meeting ZOOM connections:''' see tab {{#switchtablink:Important Links|Important Links}}<br />
<br />
=== Daily ===<br />
<br />
* '''Report at the PD/RC and attend the MCC/OPS meetings''' (weekdays 7:45 AM and 8 AM Daily, MCC building). The PD will communicate when and how meetings happen on the weekend.<br />
<br />
* Update the run plan in tab '''{{#switchtablink:Short_Term_Schedule|Short Term Schedule}}''' (and on the white board in CH) in coordination with the RG-K experiment coordinators (i.e., Annalisa, Daniel) and communicate it to the shift crew. <br />
<br />
* Log the '''RC Daily summary''' in the HBLOG. <br />
<br />
* Update the '''list of runs''' taken on the [https://docs.google.com/spreadsheets/d/1xplXDIiio_TkimucPBSf7i-bAbbM7mpWzZ1zevt4edQ/edit#gid=0 Google Spreadsheet]<br />
<br />
* '''[[https://ace.jlab.org/btm/timesheet/eb BTA time sheet]''': Make sure, the "Beam Available Not Used" (BANU) time is accounted for as explained at tab {{#switchtablink:Shift_Expert|Shift Expert}}. The BTA information can be modified post-signature.<br />
** NOTE: "After 48 hours you cannot modify a User signed timesheet unless you are the signer, Hall Manager, or Admin"<br />
<br />
* Run the daily '''RC meetings''' in CH Room 200C and on ZOOM<br />
** Mo-Tu,Th-Fr at 13:00 ET in the Counting House Conference Room<br />
** Wednesdays at 3 PM, zoom only<br />
** Weekends upon agreement<br />
** Send a '''daily invitation''' for the RC meeting to mailing lists hallb, clas12_rgk, clas_members.<br />
** Keep the '''Daily RC Meeting Minutes''' at [https://clasweb.jlab.org/wiki/index.php/Run_Group_K Run_Group_K wiki], tab "RGK FALL 2023 / SPRING 2024" <br />
<br />
* Connect to '''Zoom in CH Room 200C''':<br />
** Turn on the projector with the white remote control, then log into your CUE account. If not listed yet, click "Not listed?" in the bottom left to add your account. <br />
** Once logged in, use the recommended Google Chrome to join the ZOOM meeting on the browser or use the ZOOM application. <br />
** Since the room doesn't have audio, don't connect with the computer audio, but choose "Call Me," then enter the number in the small Cisco answering device. Once it rings, answer the call, and you will be prompted to join the meeting. <br />
** The room has a camera, which can be turned on via ZOOM. <br />
<br />
=== Weekly ===<br />
<br />
*'''MCC/OPS planning meeting''', on Wednesdays at 13:30, MCC building.<br />
** Submit (save) the online form '''[https://ace.jlab.org/apps/pd/run-coordinator-reports Run Coordinator Weekly Summary]''' before the meeting and present the contents at the meeting.<br />
** The summary covers the data taking status '''from 7 am on the previous Wednesday to 7 am on the current Wednesday'''.<br />
** '''Beam time accounting''': [https://ace.jlab.org/btm/reports/physics-summary Beam Time Manager; Physics Time Accounting]<br />
** For the '''percentage of scheduled experiment hours to date''' contact Daniel Carman.<br />
** The '''total experiment data collected to date''' can be retrieved from the up-to-date "Accumulated Charge" depicted at [https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.html]<br />
<br />
*'''Hall B meeting''' is on Mondays at 9 AM. Present your summary slides that should be sent beforehand to the Hall B leader, Patrick Achenbach. <br />
<br />
<br />
<!--####################################### MONITORING ################################################--><br />
= Monitoring =<br />
<br />
{| {{TableStyle1}}<br />
| valign=top |<br />
=== Webcams ===<br />
* [http://cctv1.jlab.org Tagger Beam Dump Viewer]<br />
* [http://hallbcam02.jlab.org Hall Fisheye]; [http://hallbcam00.jlab.org/aca/index.html#view Additional Hall Cams]<br />
* Faraday Cup beam viewer<br />
** To reboot it, run <tt>beam-viewer-reboot</tt><br />
* Counting House Cameras: [https://www.jlab.org/~baltzell/ch-abcd.html 2x2], [https://hallach-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall A], [https://hallbch-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall B], [https://hallcch-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall C], [https://halldch-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall D]<br />
<br />
| valign=top |<br />
=== EPICS ===<br />
* [https://hallbopi.jlab.org/webopi3.3/w?opi=beamline/clas12-web.opi Hall B] (CUE Login)<br />
* [https://epicsweb.jlab.org epicsweb]<br />
:&bull; [https://epicsweb.jlab.org/wedm/screen?edl=/cs/opshome/edm/wall/Status_W_Accel.edl Accelerator Status]<br />
:&bull; [https://epicsweb.jlab.org/wave Strip Charts]<br />
<br />
| valign=top |<br />
=== Data Quality ===<br />
* mon12 histograms: [https://clas12mon.jlab.org/mon12/histograms/?reference=4263114 reference (run 19868)]<br />
* [https://clasweb.jlab.org/hydra/dashboard2.html Hydra] (CUE Login) Google-Chrome ONLY, Not Firefox!<br />
* [https://github.com/JeffersonLab/caos/tree/main#readme clas12mltrack/clas12online]: <br />
:&bull; '''New'''; displaying real-time reconstructed vertices & various event topologies<br />
* [https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.html Data Accumulation Timeline] [https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.pdf PDF] [https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.xlsx Excel Spreadsheet] <br />
|}<br />
<br />
<!--####################################### Important Links ################################################--><br />
= Important Links =<br />
<br />
{| {{TableStyle1}}<br />
| valign=top |<br />
===Hall-B===<br />
* [https://clasweb.jlab.org/wiki/index.php/CLAS12_OPS_Doc Operation Safety Procedures]<br />
* [https://clasweb.jlab.org/wiki/index.php/Run_Group_K Run Group K Analysis Wiki]<br />
* [http://clasweb.jlab.org/rcdb RCDB]<br />
* [https://clasweb.jlab.org/cgi-bin/ccdb/objects CCDB]<br />
<br />
| valign=top |<br />
===Accelerator===<br />
* [http://accboard.acc.jlab.org Accelerator Whiteboard]<br />
* [https://accweb.acc.jlab.org/apps/pd/shift-plans Program Deputy Shift Plans]<br />
* [https://cebaf.jlab.org/pd/run-coordinator-reports Run Coordinator Reports]<br />
* [https://ace.jlab.org/btm/reports/physics-summary Beam Time Accounting Reports]<br />
* [https://opsweb.acc.jlab.org/CSUEApps/PSSestamp/psslog.php?numdays=5&entry_types_wanted%5BACCESS%5D=ACCESS&group_by=AREA&output_format=SCROLLABLE PSS Elog]<br />
* [http://opsweb.acc.jlab.org/internal/ops/ops_webpage/restrictions/ops_restrictions.html Operational Restrictions]<br />
<br />
| valign=top |<br />
===ZOOM Meetings===<br />
* 07:45 [https://jlab-org.zoomgov.com/j/1611456010?pwd=d2RJWTJQRDM0ZkNaZ1dpTmtLWDAwQT09 RC/PD Morning Meeting]<br />
* 08:00 [https://jlab-org.zoomgov.com/j/1601304841?pwd=Z1RIOVVUdkdXL2R2LzREZUNOUlh1dz09 MCC/OPS Morning and Wednesday 1:30 Meeting]<br />
* [https://logbooks.jlab.org/entry/4000274 See also this logbook entry]<br />
* Daily Hall B Run Coordinator Meeting: <br />
** [https://jlab-org.zoomgov.com/j/1613823885?pwd=U0FYcUNObys4dEZmRlNnbG1aVDN4UT09 URL Link] (''including Passcode'')<br />
** Meeting ID: 161 382 3885<br />
** Passcode: see emails<br />
* [https://logbooks.jlab.org/entry/4158818 Hall B Remote Shifts & Counting House]<br />
|}<br />
<br />
<br />
<headertabs/><br />
__NOEDITSECTION__<br />
__NOTOC__<br />
{| {{TableStyle1}}<br />
| valign=top style="text-align:center"|<br />
[[Image:clas12design.png|500px]]<br />
|}</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Run_Group_K&diff=7452Run Group K2024-03-07T12:30:38Z<p>Carman: </p>
<hr />
<div><!--####################################### General ########################################--><br />
= General =<br />
<br />
{| {{TableStyle1}}<br />
<br />
| valign=top |<br />
==General==<br />
===[https://logbooks.jlab.org/book/hallb Logbook]===<br />
===[http://www.jlab.org/Hall-B/shifts Shift Schedule]===<br />
===[https://docs.google.com/spreadsheets/d/1p_NaWUtR5q7lrO3np076EcClwUNqVzb2NymTndiqI8k/edit?usp=sharing Run Coordinator Schedule]===<br />
===[https://www.jlab.org/Hall-B/run-web/rgk/ESAD_HallB-CLAS12_rgK.pdf ESAD], [https://www.jlab.org/Hall-B/run-web/rgk/COO_HallB-CLAS12_RGK.pdf COO], [https://www.jlab.org/Hall-B/run-web/rgk/RSAD_HallB-CLAS12_rgk.pdf RSAD]===<br />
===[https://logbooks.jlab.org/checklists/151 Shift Checklist] ===<br />
===[https://ace.jlab.org/btm/timesheet/eb Beam Time Accounting]===<br />
* '''[https://ace.jlab.org/cdn/doc/btm/userguide.pdf Beam Time Accounting User Guide]'''.<br />
===[https://accweb.acc.jlab.org/hco/readiness Hot Checkout]===<br />
<br />
| valign=top |<br />
==Manuals==<br />
=====Systems=====<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/beamline/manual/beamline_manual.pdf Beamline]<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/torus/Hall_B_Torus_Power-Up_and_Power-Down_Procedure.pdf Torus]<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/torus/Hall_B_Solenoid_Power-Up_and_Power-Down_Procedure.pdf Solenoid]<br />
* [https://docs.google.com/document/d/1kBNmLYg2gqa4XjWgMpbh0rBUxkSAupqdnMV4THepv7k/edit#heading=h.13kef88y2w8q Cryotarget]<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/daq/opman_master.pdf DAQ]<br />
* [[Media:clas12controls_shift.pdf|Slow Controls]]<br />
=====Detectors=====<br />
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/dc/Drift-chamber-operating-procedure.pdf DC]<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/ftof/ftof_manual.pdf FTOF]<br />
* [https://clasweb.jlab.org/wiki/images/a/a2/Ec_manual.pdf ECAL]<br />
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/ltcc/manual/ltcc_manual.pdf LTCC]<br />
* [https://clasweb.jlab.org/wiki/images/f/f1/HTCC_MANUAL.pdf HTCC]<br />
* RICH: [https://github.com/JeffersonLab/clas12-manuals/raw/master/rich/RICH_Manual.pdf Expert] [https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf Shift]<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/ctof/ctof_manual.pdf CTOF]<br />
* [https://clasweb.jlab.org/wiki/images/9/97/Ops_manual_cnd.pdf CND]<br />
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/svt/svt_operation_manual.pdf SVT]<br />
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/mm/Documentation_Shifters_MVT.pdf MVT] and its [https://wiki.jlab.org/clas12-run/images/b/bf/MVT_for_Dummies.pdf Turn-on procedure]<br />
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/ft/FT-Manual.pdf FT]<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/band/band_om.pdf BAND]<br />
<br />
=====Software=====<br />
* [https://wiki.jlab.org/clas12-run/images/c/c9/CedManual.pdf CED]<br />
* [https://wiki.jlab.org/clas12-run/images/f/fd/CLAS12Mon_documentation.pdf mon12]<br />
<br />
| valign=top |<br />
==Procedures==<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam]<br />
* [[Media:clas12moller.pdf|Performing M&oslash;ller Runs]]<br />
* [[Media:HarpScanManual.pdf|Performing Harp Scans]]<br />
* [https://wiki.jlab.org/hps-run/images/0/0c/Accessing_the_tunnel.pdf Accessing the Tunnel/Hall]<br />
<br />
==Logbooks==<br />
<font size=3><br />
* [https://logbooks.jlab.org/book/elog MCC]<br />
* [https://logbooks.jlab.org/book/halog Hall-A]<br />
* [https://logbooks.jlab.org/book/hblog Hall-B]<br />
* [https://logbooks.jlab.org/book/hclog Hall-C]<br />
* [https://logbooks.jlab.org/book/hdlog Hall-D]<br />
</font><br />
<br />
|}<br />
<br />
= Phone Numbers =<br />
<!--####################################### PHONE NUMBERS #############################################--><br />
{{PhoneNumbers}}<br />
<!--- JUST MODIFY AND SAVE ANYTHING IN THIS COMMENT BLOCK TO FORCE A REFRESH OF THE PHONE NUMBERS TEMPLATE! --><br />
<br />
<!--####################################### Short Term Schedule #############################################--><br />
= Short Term Schedule =<br />
<br />
'''[https://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&action=edit Click to Edit]''' solely this tab. P.S.: You must click on the top Edit, next to Read, followed by "Save changes" to force the current page to refresh. <br><br />
<br />
{{ShortTermSchedule-RGK}}<br />
<br />
<!--####################################### GENERAL INFORMATION #############################################--><br />
= General Information =<br />
<br />
This tab contains information on <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
*'''Beam Restoration'''<br />
<br />
== '''Recent Changes''' ==<br />
<br />
=== New '''MVT LV''' Reboot Procedure ===<br />
See '''https://logbooks.jlab.org/entry/4217011''' for detailed information on rebooting the MVT LV when observing a drop in BMT strip occupancies. This gets done upon request of DAQ or MVT expert only.<br />
* Turn '''LV OFF from MVT Overview->Low Voltage->MVT-All'''. LV status indicators should change from green to black; <br />
* '''Wait 20 seconds''', then '''turn LV back from the same menu'''.<br />
* In the alarm handler, with a 2-minute alarm delay, there can be an alarm "NActiveCrates", the status is also seen on the MVT Overview GUI. This alarm will be cleared 2 min after LV is turned back ON. <br />
* Reboot mvt1, mvt2, and mvt3 ROCS. <br />
* Start a run with restart DAQ (Cancel &rarr; Reset &rarr; Configure &rarr; Download &rarr; Prestart &rarr; Go). <br />
* '''If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert'''. <br />
<br />
=== RICH issues ===<br />
* The RICH fibers alarm leads to web guidance aka logbook entry [https://logbooks.jlab.org/entry/3562273 3562273 - RICH recovery procedure]. <br />
* Check the RICH manual for the current guidance: '''https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf'''<br />
* See below for current issues<br />
<br />
=== Rapid/Controlled Access to the Hall ===<br />
* Ask MCC to stop the beam. Wait for the beacon to stop flashing (15-20 minutes) before access. Rapid access is controlled access without RadCon.<br />
* After higher beam current or a Moller run, the beacon will not stop flashing anytime soon. Then, escorted access, viz the ARM, is needed. In that case, keep the beam until the ARM arrives at the Counting House.<br />
<br />
=== 24/7 ZOOM connection for Counting House ===<br />
* Click on [https://jlab-org.zoomgov.com/j/1618614939 https://jlab-org.zoomgov.com/j/1618614939], included in "Remote Shifts" in tab "Shift Worker" <br />
* choose the option to "'''join from browser'''" (''Chrome is recommended'') and ignore all other messages to update the ZOOM APP in the pop-up windows,. <br />
* Enter the passcode from the logbook entry in tab "Shift Worker"<br />
<br />
== '''Current Issues''' == <br />
<br />
=== Lights in the Hall ===<br />
The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF because of light leaks of some of the detectors. If these lights are switched on during an access, they '''should be switched off when leaving the Hall'''. <br />
* Refer to these photos: ON: [https://logbooks.jlab.org/entry/3825712], OFF: [https://logbooks.jlab.org/entry/3825731]<br />
* We have a '''new dome light switch outside of the hall''' in the labyrinth. See logbook entry: https://logbooks.jlab.org/entry/4204460<br />
* When the dome lights are switched off, they cannot be turned back on immediately, they require 10-15 min to cool down.<br />
<br />
=== Beamline ===<br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
*'''After the HWP change''' <br />
** The absolute values of the SLM and FCUP '''charge asymmetry''' (Q-Asym) should be less than 0.1%. If they are not, contact the Beamline Expert.<br />
** Start a new run<br />
* '''Tagger Magnet Procedure:''' If the tagger magnet needs to be turned off, tell the operator to '''ONLY''' use '''the script for degaussing, NEVER do it "by hand"!''' The latter method might/will trip the circuit breaker for the power supply in the Hall.<br />
<br />
=== BMT / SVT ===<br />
* If new hot channels appear, '''call the SVT/MM expert Yuri Gotra''' (757-541-7539). These channels need to be addressed by the expert.<br />
* '''BMT HV trips''': no screenshots are necessary, power-cycle the channel HV '''as fast as possible''' (the ''underlying script will take care of ramping it up''), note the information in the shift summary. If the same channel trips frequently, ask the expert on call for guidance.<br />
* BMT HV S1 L2 STRIP in safe mode (low voltage) by expert - appears blue in MVT overview<br />
* BMT HV S1 L5 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview<br />
* BMT HV S2 L6 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview<br />
<br />
=== CND ===<br />
* CAMAC crate alarm: <br />
** CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, can be done via the alarm handler. <br />
** After reboot, the CFD thresholds need to be set by running a script, see page 12 in the CND manual at tab "General", https://clasweb.jlab.org/wiki/images/9/97/Ops_manual_cnd.pdf<br />
<br />
=== DAQ ===<br />
* Some ROCs keep printing error messages while functioning properly; please see their list in this logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] to avoid unnecessary reboots since the printout in the ROC terminal won't change. The message will appear in the DAQ run control if they get disconnected! <br />
* <font color=red>'''NEW STANDARD''' end and start of the run:</font> End run, Cancel, Reset, <u> Download</u> , Prestart, Go. This will ensure proper compression of the FADCs and therefore a smaller data rate.<br />
* roc reboot instructions:<br />
** To reboot i.e. adcecal1, type on a clasrun terminal: clasrun> roc_reboot adcecal1<br />
** To check that the crate is back alive, type:clasrun> ping adcecal1<br />
** The ping will start to answer as soon as the crate communicates again. <br />
<br />
=== DC ===<br />
* Make sure to log every DC trip in the shift summary. Make sure to list WHERE and why, possibly, the trip occurred.<br />
<br />
=== ECAL/PCAL ===<br />
* "ECAL_SEC6_UO26 Noisy" https://logbooks.jlab.org/entry/4241957<br />
* "PCAL_HV_SEC2_U25 turned off" https://logbooks.jlab.org/entry/4247187, https://logbooks.jlab.org/entry/4247400<br />
<br />
=== FTOF ===<br />
* FTOF S2 Paddle 19-left and S4 Paddle 16-left are known to be "weak" channels that tend to come and go depending on torus polarity and rates. This cannot be fixed during this run period; see https://logbooks.jlab.org/entry/4219555 and https://logbooks.jlab.org/entry/4219876.<br />
* "FTOF HV Adjustment - S5 P2 2R" https://logbooks.jlab.org/entry/4249754<br />
<br />
=== RICH ===<br />
* '''Known problematic PMTs and tile''':<br />
** You don't need to report about it.<br />
** PMT 2 (sector 1) and PMT 92 (sector 4) are not completely dead and may be visible depending on statistics.<br />
** Problematic tiles and PMTs:<br />
*** Sector 1 Tile 21 dead (PMT 55,56,57)<br />
*** Sector 1 Tile 1 PMT 2<br />
*** Sector 4 Tile 34 PMT 92<br />
<br />
== '''Beam Restoration''' == <br />
<br />
* Study the manual: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam]. If you do not feel confident to do this by yourself, contact the Beamline Expert.<br />
<br />
* Find all Reference values on the white board at tab Short_Term_Schedule<br />
<br />
=== Restoring Beam after Short Downtime ===<br />
<br />
* Ask for 5 nA beam current and check the 2C24A and 2H01 beam (x, y) positions against the Reference Values (tab "Short Term Schedule") after <br />
** beam steering or orbit change<br />
** change in beam current, e.g., after a target change<br />
** If BPM 2C24A and 2H01 positions are off, (not within +/-0.1 mm), ask MCC to bring them to the reference values<br />
<br />
=== Beam Tuning to Tagger Yoke Dump ===<br />
<br />
Study the manual: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam]. <br />
* Contact Eugene Pasyuk if issues arise.<br />
<br />
* Ask MCC to energize the tagger magnet<br />
:- blank collimator<br />
:- beam type "Photon"<br />
<br />
* All CLAS12 detectors HV off (BMT HV in safe mode)<br />
<br />
* Ask MCC to mask the beam halo counters (FSDs: Upstream, Midstream, Downstream, BOM) <br />
* Ask MCC for 5 nA beam current and make sure the Orbit Locks are OFF;<br />
* If necessary, ask MCC to bring the 2C21A and 2C24A beam positions to the Reference Values<br />
* Take harp scans<br />
:- at Harp 2C21A (Upstream Right Counter)<br />
:- at Tagger Harp 2C24A Upstream Right Counter)<br />
* If the beam trips, abort the scan and restart. The beam must be on during the scan, otherwise the fit to the beam profile will not work. <br />
* Compare the results with the Harp Scan References <br />
* The fit ranges might need to be adjusted manually to assess the fit results<br />
<br />
* If good, log the new scan results.<br />
<br />
=== M&oslash;ller run ===<br />
<br />
Follow the standard procedure as described in the manual [https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf Performing M&oslash;ller Runs].<br />
* Contact Nathan Baltzell if issues arise<br />
<br />
A few points to note:<br />
* '''Request 20 nA''' , Orbit Locks should be off<br />
* The BPMs 2C21 and 2C24A may be out of range after the M&oslash;ller configuration. <br />
* Keep running until the polarization uncertainty is < 1.5%<br />
<br />
=== Beam Tuning to Faraday Cup ===<br />
<br />
Study the manual: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam], and take into account the first steps mentioned therein. <br />
<br />
This is typically done after tuning to the tagger dump (and possibly taking a Moller run).<br />
<br />
* All CLAS12 detectors HV off (BMT HV in safe mode)<br />
<br />
* Ask MCC to de-energize the tagger magnet<br />
:- 20 mm collimator<br />
:- beam type electron<br />
:- beam blocker out<br />
* If initial beam tune, target should be "Empty"<br />
* Ask MCC to unmask beam halos<br />
* Set the halo counter FSD thresholds to 1 MHz and the integration time interval to 50 milliseconds<br />
* Insert the Downstream Viewer, Chromax, in the beamline<br />
* Ask MCC for 5 nA beam current<br />
* If necessary, ask MCC to bring the beam positions at 2C24A and 2H01 to the Reference Values<br />
* Take a harp scan at 2H01 (Midstream Left)<br />
* If the beam trips, abort and restart. The beam must be on during the scan, otherwise the fit to the beam profile will not work. <br />
* Compare the results with the Harp Scan References <br />
* If good, log the new scan results.<br />
<br />
Once done and before resuming the production data-taking:<br />
* Retract the Downstream Viewer from the beamline<br />
* Put the FSDs thresholds and integration time to their reference values<br />
* Turn all detector HV ON, for MVT "HV ON - Full Voltage"<br />
* MCC might need to adjust the beam positions after going to the production beam current.<br />
<br />
<!--####################################### Shift Expert ################################################--><br />
= Shift Expert =<br />
<br />
Come to your shift in time for the '''shift change''', 10-15 minutes before the start of your shift. <br />
* If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
Follow the '''Short Term Schedule'''<br />
* The RC must be notified before changing run conditions<br />
<br />
Operate the '''Data Acquisition'''<br />
<br />
Take action on and log '''alarms'''<br />
<br />
At '''the end of the shift''', submit the '''strip charts''' to the logbook <br />
* If they are not up already: (CS-Studio &rarr; Tools &rarr; Strip Charts &rarr; livePlot)<br />
* Right click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters"<br />
* Choose a '''time-span width of 10 hours''' (right-click below x-axis)<br />
* <font color=red> To make a logbook entry:</font><br />
:- Right click within the grid of one of the charts, choose "Make Logbook Entry"<br />
:- The title of the logbook entry can be changed, eg to Strip charts<br />
:- Un-click ELOG, select HBLOG, and click on "Make Entry" to submit<br />
<br />
'''Communicate''' with your co-shift person:<br />
* Remind them to read the tab 'Shift Worker'.<br />
* Discuss any issues with the shift worker before making extra logbook entries.<br />
* Remind the shift worker of the '''end-of-shift Checklist'''.<br />
* <font color=red> Use the CS-Studio '''Logbook entry tool''' for all screen shots (but the strip charts)!</font><br />
* Note that the Logbook Entry tool puts the entry in the HBRUN logbook by default. Other logbooks can be added or selected from the drop down menu. <br />
<br />
Check for and read any comments to '''logbook entries''' made during your shift.<br />
<br />
Keep your '''shift summary''' up to date in HBLOG. Record all significant happenings. <br />
* Refer to relevant logbook entries in the shift summary.<br />
* Include a run list for the shift with relevant run information.<br />
<br />
Ensure that all '''monitoring plots''' and are logged and checked against the reference plots for every single run.<br />
* Both, you and the shift worker should run mon12 and '''reset & check spectra frequently'''.<br />
<br />
* If the worker shift is remote, maintain communication over Zoom. <br />
<br />
* If you have any other questions or uncertainties about what to do, call the RC.<br />
<br />
The shift worker (if in person) should log the '''clas12online'' reconstruction plots at the end of a run. Running the program on more than one CH computer has been causing problems.<br />
<br />
In case of '''RICH issues''', check the RICH manual for the current guidance: https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf<br />
<br />
'''New MVT LV Reboot Procedure''' can be found at tab 'GENERAL INFORMATION'.<br />
<br />
'''[https://ace.jlab.org/btm Fill out BTA]''' hourly;<br />
* Accelerator beam time (do not change these values):<br />
** ABU: acceptable beam used <br />
** BANU: beam acceptable but not used (should be reflected in our PCC and UED)<br />
** BNA: beam not acceptable (e.g., tuning, drifting, not focused)<br />
** ACC: Accelerator Configuration Change (e.g., pass change)<br />
** OFF: Accelerator is down<br />
* Experiment beam time (do change these values):<br />
** ER: Experiment ready (should be 60 minutes - PCC - UED)<br />
** PCC: Planned configuration change (when the beam is masked while radiators are moved, target change, DAQ (stopping/starting runs, tests, etc.)<br />
** UED: Unplanned experiment down (hardware failure, DAQ crashes, our problems, ...)<br />
** ''Exception'': ''BANU, due to time spent on beam tuning and BPM checks after beam down, should be counted as ER on our side''.<br />
* Enter fields at the "Shift Information" tab.<br />
* You must save at 7:00, 15:00, and 23:00, to send info to MCC. To see the save button, click 'edit all' or 'edit cc hours.' <br />
* Acknowledge the popup error message about the last hour not being completed by clicking OK.<br />
* Sign, viz log completed 8-hour sheet. <br />
* '''Note: we can change the time sheet up to 48 hours after completion.''' <br />
<br />
<!--####################################### Shift Worker ################################################--><br />
= Shift Worker =<br />
<br />
Come to your shift in time for the '''shift change''', 10-15 minutes before the start of your shift;<br />
* If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
Discuss any issue with the shift expert before making extra logbook entries; ask the shift expert to note the ongoing issue in the shift summary.<br />
<br />
<font color=red> Use the CS-Studio '''Logbook entry tool''' for all screen shots (but the strip charts)! </font><br />
<br />
=== Frequently ===<br />
<br />
Reset and check mon12 histograms frequently, preferably each 1h<br />
* Note that some plots have radio buttons at the bottom to choose the sector. Remember to cycle through and check all sectors.<br />
<br />
=== Once per run ===<br />
<br />
Note that the CS-Studio '''Logbook Entry tool''' puts the entry in the HBRUN logbook by default. Other logbooks can be added or selected from the drop down menu. <br />
<br />
Using the Logbook Entry tool, submit EPICS '''screenshots''' to the HBRUN logbook (one logbook entry) '''with beam ON'''<br />
# Beamline overview (remote shift: in VNC or [https://hallbopi.jlab.org/webopi3.3/w?opi=beamline/clas12-web.opi Web Browser])<br />
# DAQ status<br />
# CLAS12 trigger rates <br />
<br />
Upload '''mon12''' monitoring plots to the logbook with sufficient statistics and compare them to the reference and recent uploads (see {{#switchtablink:Monitoring|Monitoring}} tab).<br />
<br />
At the '''end of the run''', submit the '''strip charts''' to the logbook <br />
* If they are not up already: (CS-Studio &rarr; Tools &rarr; Strip Charts &rarr; livePlot)<br />
* Right click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters"<br />
* Choose a '''time-span width of 4 hours''', compatible with the run duration (right-click below x-axis)<br />
* <font color=red> To make a logbook entry:</font><br />
:- Right click within the grid of one of the charts, choose "Make Logbook Entry"<br />
:- The title of the logbook entry can be changed, eg to Strip charts<br />
:- Un-click ELOG, select HBLOG, and click on "Make Entry" to submit<br />
<br />
At the '''end of the run''', upload the '''[https://github.com/JeffersonLab/caos/tree/main#readme clas12online]''' plots to the logbook.<br />
* The program can continue through a standard end/start of a run. However, after a DAQ restart, you must back out and restart clas12online.<br />
* If the DAQ has to be restarted, you can still make the upload before backing out.<br />
<br />
=== Once per shift ===<br />
<br />
Fill the '''[https://logbooks.jlab.org/checklists/151 shift checklist]''';<br />
* During production, get relevant values from the epics screens Beamline Overview, CLAS12 DAQ Status and CLAS12 Trigger;<br />
* During extended downtime, get relevant values from the latest EPICS screenshots that you made during production <br />
<br />
== For Remote Shifts ==<br />
<font color=red>'''Please inform the PDL that your shifts will be remote.''' </font color=red> <br />
Remote shifts are listed [[upcoming-remote-shifts|here]]<br />
<br />
You must test your setup, including Zoom and VNC connections, at least 24 hours before your first shift!<br />
* Zoom for 24-7 communication with Counting House:<br />
** In the Zoom app: [https://jlab-org.zoomgov.com/j/1618614939 https://jlab-org.zoomgov.com/j/1618614939]<br />
** Or in a web browser: [https://jlab-org.zoomgov.com/wc/1618614939/join?pwd=U003MnRuNVdiU1EzaFpXV0JuNWV1Zz09 https://jlab-org.zoomgov.com/wc/1618614939/join?pwd=U003MnRuNVdiU1EzaFpXV0JuNWV1Zz09]<br />
** The passcode is required and contained in [https://logbooks.jlab.org/entry/4158818 this log entry]<br />
** Remind the expert in the counting house to restart their ZOOM, if necessary<br />
* Remote VNC connection instructions: https://logbooks.jlab.org/entry/3906039<br />
* '''If you mistyped''' (username, pincode, passcode,...) a string of numbers will appear with text asking you to respond to this challenge. Back out with ctrl_c and you get another try! After N+1 mistypes you will be locked out. For several hours after that you will not even be able to get to the public JLab webpages.<br />
** All necessary applications should be available from the desktop menu (left/right click on the desktop)<br />
** EPICS GUIs should be accessed '''ONLY''' via the desktop menu or by running <tt>clascss-remote</tt>.<br />
<!--* [https://userweb.jlab.org/~baltzell/clas12/shift/remote-demo.mp4 Remote Demonstration Video (150 MB)]--><br />
** Some charts are also accessible via web browser: [https://epicsweb.jlab.org/wave/?myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Upstream+and+Midstream+Halo+Counters&fullscreen=false&layoutMode=2&viewerMode=2&pv=scaler_cS3b&pv=scaler_cS4b&pv=scaler_cS6b&pv=scaler_cS12b&pv=scaler_cS13b&pv=scaler_cS14b&pv=scaler_cS15b&scaler_cS3blabel=scaler_cS3b&scaler_cS3bcolor=%23a6cee3&scaler_cS3byAxisLabel=Rate++%28Hz%29&scaler_cS3byAxisMin=&scaler_cS3byAxisMax=&scaler_cS3byAxisLog&scaler_cS3bscaler=&start=2020-08-08+09%3A02%3A36&end=2020-08-08+09%3A07%3A36&scaler_cS4blabel=scaler_cS4b&scaler_cS4bcolor=%231f78b4&scaler_cS4byAxisLabel=&scaler_cS4byAxisMin=&scaler_cS4byAxisMax=&scaler_cS4byAxisLog=&scaler_cS4bscaler=&scaler_cS5byAxisLabel=&scaler_cS5byAxisMin=&scaler_cS5byAxisMax=&scaler_cS5byAxisLog=&scaler_cS5bscaler=&scaler_cS6blabel=scaler_cS6b&scaler_cS6bcolor=%2333a02c&scaler_cS6byAxisLabel=&scaler_cS6byAxisMin=&scaler_cS6byAxisMax=&scaler_cS6byAxisLog=&scaler_cS6bscaler=&scaler_cS7byAxisLabel=&scaler_cS7byAxisMin=&scaler_cS7byAxisMax=&scaler_cS7byAxisLog=&scaler_cS7bscaler=&scaler_cS12blabel=scaler_cS12b&scaler_cS12bcolor=%23e31a1c&scaler_cS12byAxisLabel=&scaler_cS12byAxisMin=&scaler_cS12byAxisMax=&scaler_cS12byAxisLog=&scaler_cS12bscaler=&scaler_cS13blabel=scaler_cS13b&scaler_cS13bcolor=%23fdbf6f&scaler_cS13byAxisLabel=&scaler_cS13byAxisMin=&scaler_cS13byAxisMax=&scaler_cS13byAxisLog=&scaler_cS13bscaler=&scaler_cS14blabel=scaler_cS14b&scaler_cS14bcolor=%23ff7f00&scaler_cS14byAxisLabel=&scaler_cS14byAxisMin=&scaler_cS14byAxisMax=&scaler_cS14byAxisLog=&scaler_cS14bscaler=&scaler_cS15blabel=scaler_cS15b&scaler_cS15bcolor=%23cab2d6&scaler_cS15byAxisLabel=&scaler_cS15byAxisMin=&scaler_cS15byAxisMax=&scaler_cS15byAxisLog=&scaler_cS15bscaler= Upstream/Midstream Halo Counters], [https://epicsweb.jlab.org/wave/?myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Downstream+Halo+Counters&fullscreen=false&layoutMode=2&viewerMode=2&pv=scalerS8b&pv=scalerS9b&scalerS8blabel=scalerS8b&scalerS8bcolor=%23a6cee3&scalerS8byAxisLabel=Rate++%28Hz%29&scalerS8byAxisMin=&scalerS8byAxisMax=&scalerS8byAxisLog&scalerS8bscaler=&pv=scalerS10b&pv=scalerS11b&scalerS9blabel=scalerS9b&scalerS9bcolor=%231f78b4&scalerS9byAxisLabel=&scalerS9byAxisMin=&scalerS9byAxisMax=&scalerS9byAxisLog=&scalerS9bscaler=&scalerS10blabel=scalerS10b&scalerS10bcolor=%23b2df8a&scalerS10byAxisLabel=&scalerS10byAxisMin=&scalerS10byAxisMax=&scalerS10byAxisLog=&scalerS10bscaler=&scalerS11blabel=scalerS11b&scalerS11bcolor=%2333a02c&scalerS11byAxisLabel=&scalerS11byAxisMin=&scalerS11byAxisMax=&scalerS11byAxisLog=&scalerS11bscaler= Downstream Halo Counters], [https://epicsweb.jlab.org/wave/?start=2020-07-08+16%3A50%3A02&end=2020-07-08+16%3A55%3A02&myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Beam+Currents&fullscreen=false&layoutMode=2&viewerMode=2&pv=IPM2C21A&pv=IPM2C24A&pv=scaler_calc1b&IPM2C21Alabel=IPM2C21A&IPM2C21Acolor=%23a6cee3&IPM2C21AyAxisLabel=Beam+Current+%28nA%29&IPM2C21AyAxisMin=0&IPM2C21AyAxisMax=300&IPM2C21AyAxisLog&IPM2C21Ascaler=&scaler_calc1blabel=Faraday+Cup&scaler_calc1bcolor=%23b2df8a&scaler_calc1byAxisLabel=&scaler_calc1byAxisMin=&scaler_calc1byAxisMax=&scaler_calc1byAxisLog&scaler_calc1bscaler= Beam Currents], [https://epicsweb.jlab.org/wave/?start=2020-08-03+12%3A30%3A57&end=2020-08-03+12%3A35%3A57&myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=BPM+Positions+%28Y-Axis+is+mean+%2B%2F-+0.5+mm%29&fullscreen=false&layoutMode=3&viewerMode=2&pv=IPM2C24A.XPOS&pv=IPM2C24A.YPOS&pv=IPM2H01.XPOS&pv=IPM2H01.YPOS&IPM2C24A.XPOSlabel=IPM2C24A.XPOS&IPM2C24A.XPOScolor=%23e31a1c&IPM2C24A.XPOSyAxisLabel=&IPM2C24A.XPOSyAxisMin=-2.0&IPM2C24A.XPOSyAxisMax=+1.0&IPM2C24A.XPOSyAxisLog&IPM2C24A.XPOSscaler=&IPM2C24A.YPOSlabel=IPM2C24A.YPOS&IPM2C24A.YPOScolor=pink&IPM2C24A.YPOSyAxisLabel=&IPM2C24A.YPOSyAxisMin=-2.0&IPM2C24A.YPOSyAxisMax=1.0&IPM2C24A.YPOSyAxisLog&IPM2C24A.YPOSscaler=&IPM2H01.XPOSlabel=IPM2H01.XPOS&IPM2H01.XPOScolor=darkgreen&IPM2H01.XPOSyAxisLabel=&IPM2H01.XPOSyAxisMin=-2.0&IPM2H01.XPOSyAxisMax=1.0&IPM2H01.XPOSyAxisLog&IPM2H01.XPOSscaler=&IPM2H01.YPOSlabel=IPM2H01.YPOS&IPM2H01.YPOScolor=lightgreen&IPM2H01.YPOSyAxisLabel=&IPM2H01.YPOSyAxisMin=-2.0&IPM2H01.YPOSyAxisMax=1.0&IPM2H01.YPOSyAxisLog&IPM2H01.YPOSscaler=#a6cee3&IPM2C24A.XPOSyAxisLabel=2C24+X+(mm)&IPM2C24A.XPOSyAxisMin=-1.5&IPM2C24A.XPOSyAxisMax=-0.5&IPM2C24A.XPOSyAxisLog&IPM2C24A.XPOSscaler=&IPM2C24A.YPOSlabel=IPM2C24A.YPOS&IPM2C24A.YPOScolor=%231f78b4&IPM2C24A.YPOSyAxisLabel=2C24+Y+(mm)&IPM2C24A.YPOSyAxisMin=0.3&IPM2C24A.YPOSyAxisMax=1.3&IPM2C24A.YPOSyAxisLog&IPM2C24A.YPOSscaler=&IPM2H01.XPOSlabel=IPM2H01.XPOS&IPM2H01.XPOScolor=pink&IPM2H01.XPOSyAxisLabel=2H01+X+(mm)&IPM2H01.XPOSyAxisMin=-0.6&IPM2H01.XPOSyAxisMax=0.4&IPM2H01.XPOSyAxisLog&IPM2H01.XPOSscaler=&IPM2H01.YPOSlabel=IPM2H01.YPOS&IPM2H01.YPOScolor=darkred&IPM2H01.YPOSyAxisLabel=2H01+Y+(mm)&IPM2H01.YPOSyAxisMin=0.4&IPM2H01.YPOSyAxisMax=1.4&IPM2H01.YPOSyAxisLog&IPM2H01.YPOSscaler= BPM Positions]<br />
<br />
<br />
<!--####################################### Run Coordinator ################################################--><br />
= Run Coordinator =<br />
<br />
Check the '''upcoming shifts''', and if necessary, coordinate with the PDL to contact shift takers about their training and site access status.<br />
<br />
'''Remote shifts''' are listed [[Upcoming-remote-shifts|here]].<br />
<br />
'''Backup shift personnel''' is listed [https://jeffersonlab-my.sharepoint.com/:x:/r/personal/baltzell_jlab_org/Documents/Backup%20Shifters.xlsx?d=wf18dc5909cf84424840d73cc9bd8ce8e&csf=1&web=1&e=QwY1fs here].<br />
<br />
'''Meeting ZOOM connections:''' see tab {{#switchtablink:Important Links|Important Links}}<br />
<br />
=== Daily ===<br />
<br />
* '''Report at the PD/RC and attend the MCC/OPS meetings''' (weekdays 7:45 AM and 8 AM Daily, MCC building). The PD will communicate when and how meetings happen on the weekend.<br />
<br />
* Update the run plan in tab '''{{#switchtablink:Short_Term_Schedule|Short Term Schedule}}''' (and on the white board in CH) in coordination with the RG-K experiment coordinators (i.e., Annalisa, Daniel) and communicate it to the shift crew. <br />
<br />
* Log the '''RC Daily summary''' in the HBLOG. <br />
<br />
* Update the '''list of runs''' taken on the [https://docs.google.com/spreadsheets/d/1xplXDIiio_TkimucPBSf7i-bAbbM7mpWzZ1zevt4edQ/edit#gid=0 Google Spreadsheet]<br />
<br />
* '''[[https://ace.jlab.org/btm/timesheet/eb BTA time sheet]''': Make sure, the "Beam Available Not Used" (BANU) time is accounted for as explained at tab {{#switchtablink:Shift_Expert|Shift Expert}}. The BTA information can be modified post-signature.<br />
** NOTE: "After 48 hours you cannot modify a User signed timesheet unless you are the signer, Hall Manager, or Admin"<br />
<br />
* Run the daily '''RC meetings''' in CH Room 200C and on ZOOM<br />
** Mo-Tu,Th-Fr at 13:00 ET in the Counting House Conference Room<br />
** Wednesdays at 3 PM, zoom only<br />
** Weekends upon agreement<br />
** Send a '''daily invitation''' for the RC meeting to mailing lists hallb, clas12_rgk, clas_members.<br />
** Keep the '''Daily RC Meeting Minutes''' at [https://clasweb.jlab.org/wiki/index.php/Run_Group_K Run_Group_K wiki], tab "RGK FALL 2023 / SPRING 2024" <br />
<br />
* Connect to '''Zoom in CH Room 200C''':<br />
** Turn on the projector with the white remote control, then log into your CUE account. If not listed yet, click "Not listed?" in the bottom left to add your account. <br />
** Once logged in, use the recommended Google Chrome to join the ZOOM meeting on the browser or use the ZOOM application. <br />
** Since the room doesn't have audio, don't connect with the computer audio, but choose "Call Me," then enter the number in the small Cisco answering device. Once it rings, answer the call, and you will be prompted to join the meeting. <br />
** The room has a camera, which can be turned on via ZOOM. <br />
<br />
=== Weekly ===<br />
<br />
*'''MCC/OPS planning meeting''', on Wednesdays at 13:30, MCC building.<br />
** Submit (save) the online form '''[https://ace.jlab.org/apps/pd/run-coordinator-reports Run Coordinator Weekly Summary]''' before the meeting and present the contents at the meeting.<br />
** The summary covers the data taking status '''from 7 am on the previous Wednesday to 7 am on the current Wednesday'''.<br />
** '''Beam time accounting''': [https://ace.jlab.org/btm/reports/physics-summary Beam Time Manager; Physics Time Accounting]<br />
** For the '''percentage of scheduled experiment hours to date''' contact Daniel Carman.<br />
** The '''total experiment data collected to date''' can be retrieved from the up-to-date "Accumulated Charge" depicted at [https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.html]<br />
<br />
*'''Hall B meeting''' is on Mondays at 9 AM. Present your summary slides that should be sent beforehand to the Hall B leader, Patrick Achenbach. <br />
<br />
<br />
<!--####################################### MONITORING ################################################--><br />
= Monitoring =<br />
<br />
{| {{TableStyle1}}<br />
| valign=top |<br />
=== Webcams ===<br />
* [http://cctv1.jlab.org Tagger Beam Dump Viewer]<br />
* [http://hallbcam02.jlab.org Hall Fisheye]; [http://hallbcam00.jlab.org/aca/index.html#view Additional Hall Cams]<br />
* Faraday Cup beam viewer<br />
** To reboot it, run <tt>beam-viewer-reboot</tt><br />
* Counting House Cameras: [https://www.jlab.org/~baltzell/ch-abcd.html 2x2], [https://hallach-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall A], [https://hallbch-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall B], [https://hallcch-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall C], [https://halldch-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall D]<br />
<br />
| valign=top |<br />
=== EPICS ===<br />
* [https://hallbopi.jlab.org/webopi3.3/w?opi=beamline/clas12-web.opi Hall B] (CUE Login)<br />
* [https://epicsweb.jlab.org epicsweb]<br />
:&bull; [https://epicsweb.jlab.org/wedm/screen?edl=/cs/opshome/edm/wall/Status_W_Accel.edl Accelerator Status]<br />
:&bull; [https://epicsweb.jlab.org/wave Strip Charts]<br />
<br />
| valign=top |<br />
=== Data Quality ===<br />
* mon12 histograms: [https://clas12mon.jlab.org/mon12/histograms/?reference=4254919 reference (run 19734)]<br />
* [https://clasweb.jlab.org/hydra/dashboard2.html Hydra] (CUE Login) Google-Chrome ONLY, Not Firefox!<br />
* [https://github.com/JeffersonLab/caos/tree/main#readme clas12mltrack/clas12online]: <br />
:&bull; '''New'''; displaying real-time reconstructed vertices & various event topologies<br />
* [https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.html Data Accumulation Timeline] [https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.pdf PDF] [https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.xlsx Excel Spreadsheet] <br />
|}<br />
<br />
<!--####################################### Important Links ################################################--><br />
= Important Links =<br />
<br />
{| {{TableStyle1}}<br />
| valign=top |<br />
===Hall-B===<br />
* [https://clasweb.jlab.org/wiki/index.php/CLAS12_OPS_Doc Operation Safety Procedures]<br />
* [https://clasweb.jlab.org/wiki/index.php/Run_Group_K Run Group K Analysis Wiki]<br />
* [http://clasweb.jlab.org/rcdb RCDB]<br />
* [https://clasweb.jlab.org/cgi-bin/ccdb/objects CCDB]<br />
<br />
| valign=top |<br />
===Accelerator===<br />
* [http://accboard.acc.jlab.org Accelerator Whiteboard]<br />
* [https://accweb.acc.jlab.org/apps/pd/shift-plans Program Deputy Shift Plans]<br />
* [https://cebaf.jlab.org/pd/run-coordinator-reports Run Coordinator Reports]<br />
* [https://ace.jlab.org/btm/reports/physics-summary Beam Time Accounting Reports]<br />
* [https://opsweb.acc.jlab.org/CSUEApps/PSSestamp/psslog.php?numdays=5&entry_types_wanted%5BACCESS%5D=ACCESS&group_by=AREA&output_format=SCROLLABLE PSS Elog]<br />
* [http://opsweb.acc.jlab.org/internal/ops/ops_webpage/restrictions/ops_restrictions.html Operational Restrictions]<br />
<br />
| valign=top |<br />
===ZOOM Meetings===<br />
* 07:45 [https://jlab-org.zoomgov.com/j/1611456010?pwd=d2RJWTJQRDM0ZkNaZ1dpTmtLWDAwQT09 RC/PD Morning Meeting]<br />
* 08:00 [https://jlab-org.zoomgov.com/j/1601304841?pwd=Z1RIOVVUdkdXL2R2LzREZUNOUlh1dz09 MCC/OPS Morning and Wednesday 1:30 Meeting]<br />
* [https://logbooks.jlab.org/entry/4000274 See also this logbook entry]<br />
* Daily Hall B Run Coordinator Meeting: <br />
** [https://jlab-org.zoomgov.com/j/1613823885?pwd=U0FYcUNObys4dEZmRlNnbG1aVDN4UT09 URL Link] (''including Passcode'')<br />
** Meeting ID: 161 382 3885<br />
** Passcode: see emails<br />
* [https://logbooks.jlab.org/entry/4158818 Hall B Remote Shifts & Counting House]<br />
|}<br />
<br />
<br />
<headertabs/><br />
__NOEDITSECTION__<br />
__NOTOC__<br />
{| {{TableStyle1}}<br />
| valign=top style="text-align:center"|<br />
[[Image:clas12design.png|500px]]<br />
|}</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7451Template:ShortTermSchedule-RGK2024-03-07T12:21:37Z<p>Carman: /* Run Plan: Mar. 7 - Mar. 11, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 7 - Mar. 11, 2024''' ==<br />
<br />
'''Production Running ... to the end!!'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.<br />
- Turn all detectors off and put BMT HV in safe mode<br />
- Ramp torus and solenoid to zero field (contact Eugene to do this)<br />
- Call to put Hall B in Restricted Access<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7450Template:ShortTermSchedule-RGK2024-03-07T12:11:52Z<p>Carman: </p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 7 - Mar. 11, 2024''' ==<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.<br />
- Turn all detectors off and put BMT HV in safe mode<br />
- Ramp torus and solenoid to zero field (contact Eugene to do this)<br />
- Call to put Hall B in Restricted Access<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7449Template:ShortTermSchedule-RGK2024-03-06T22:02:50Z<p>Carman: /* Run Plan: Mar. 6 - Mar. 11, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 6 - Mar. 11, 2024''' ==<br />
<br />
'''Beam Restore'''<br />
- An hour before MCC is ready to deliver beam, call Eugene to ramp the torus up to full field (it is presently parked at 500 A).<br />
- 30 minutes before beam delivery:<br />
- Call MCC to energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon)<br />
- Turn all CLAS12 detectors off<br />
- Call Yuri to put BMT HV in safe mode (system is flushing after service today)<br />
- Tune beam to tagger yoke dump at 5 nA<br />
- Take harp scans at 2C21A and 2C24A and compare to reference plots (have MCC tune beam to match reference scan as necessary) (contact Eugene for questions)<br />
- Call MCC to turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
- Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
- Take harp scan at 2H01 and compare to reference plot (have MCC tune beam to match reference scan as necessary) (contact Eugene for questions)<br />
- When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.<br />
- Turn all detectors off and put BMT HV in safe mode<br />
- Ramp torus and solenoid to zero field (contact Eugene to do this)<br />
- Call to put Hall B in Restricted Access<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7448Template:ShortTermSchedule-RGK2024-03-06T22:01:13Z<p>Carman: /* Run Plan: Mar. 6 - Mar. 11, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 6 - Mar. 11, 2024''' ==<br />
<br />
'''Beam Restore'''<br />
- An hour before MCC is ready to deliver beam, call Eugene to ramp the torus up to full field (it is presently parked at 500 A).<br />
- 30 minutes before beam delivery:<br />
- Call MCC to energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon)<br />
- Turn all CLAS12 detectors off<br />
- Call Yuri to put BMT HV in safe mode (system is flushing after service today)<br />
- Tune beam to tagger yoke dump at 5 nA (contact Eugene for questions)<br />
- Take harp scans at 2C21A and 2C24A and compare to reference plots (have MCC tune beam to match reference scan as necessary)<br />
- Call MCC to turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
- Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
- Take harp scan at 2H01 and compare to reference plot (have MCC tune beam to match reference scan as necessary)<br />
- When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.<br />
- Turn all detectors off and put BMT HV in safe mode<br />
- Ramp torus and solenoid to zero field (contact Eugene to do this)<br />
- Call to put Hall B in Restricted Access<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7447Template:ShortTermSchedule-RGK2024-03-06T21:59:08Z<p>Carman: </p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 6 - Mar. 11, 2024''' ==<br />
<br />
'''Beam Restore'''<br />
- An hour before MCC is ready to deliver beam, call Eugene to ramp the torus up to full field (it is presently parked at 500 A).<br />
- 30 minutes before beam delivery, call MCC to energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off, BMT HV in safe mode)<br />
- Tune beam to tagger yoke dump at 5 nA (contact Eugene for questions)<br />
- Take harp scans at 2C21A and 2C24A and compare to reference plots (have MCC tune beam to match reference scan as necessary)<br />
- Call MCC to turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
- Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
- Take harp scan at 2H01 and compare to reference plot (have MCC tune beam to match reference scan as necessary)<br />
- When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.<br />
- Turn all detectors off and put BMT HV in safe mode<br />
- Ramp torus and solenoid to zero field (contact Eugene to do this)<br />
- Call to put Hall B in Restricted Access<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7446Template:ShortTermSchedule-RGK2024-03-06T19:43:48Z<p>Carman: </p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 6 - Mar. 11, 2024''' ==<br />
<br />
'''Beam Restore'''<br />
- When approval is given by RC, call Eugene to ramp up the torus and solenoid magnets to nominal settings<br />
- 30 minutes before beam delivery, call MCC to energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off, BMT HV in safe mode)<br />
- Tune beam to tagger yoke dump at 5 nA (contact Eugene for questions)<br />
- Take harp scans at 2C21A and 2C24A and compare to reference plots (have MCC tune beam to match reference scan as necessary)<br />
- Call MCC to turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
- Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
- Take harp scan at 2H01 and compare to reference plot (have MCC tune beam to match reference scan as necessary)<br />
- When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.<br />
- Turn all detectors off and put BMT HV in safe mode<br />
- Ramp torus and solenoid to zero field (contact Eugene to do this)<br />
- Call to put Hall B in Restricted Access<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Run_Group_K&diff=7445Run Group K2024-03-06T19:39:20Z<p>Carman: </p>
<hr />
<div><!--####################################### General ########################################--><br />
= General =<br />
<br />
{| {{TableStyle1}}<br />
<br />
| valign=top |<br />
==General==<br />
===[https://logbooks.jlab.org/book/hallb Logbook]===<br />
===[http://www.jlab.org/Hall-B/shifts Shift Schedule]===<br />
===[https://docs.google.com/spreadsheets/d/1p_NaWUtR5q7lrO3np076EcClwUNqVzb2NymTndiqI8k/edit?usp=sharing Run Coordinator Schedule]===<br />
===[https://www.jlab.org/Hall-B/run-web/rgk/ESAD_HallB-CLAS12_rgK.pdf ESAD], [https://www.jlab.org/Hall-B/run-web/rgk/COO_HallB-CLAS12_RGK.pdf COO], [https://www.jlab.org/Hall-B/run-web/rgk/RSAD_HallB-CLAS12_rgk.pdf RSAD]===<br />
===[https://logbooks.jlab.org/checklists/151 Shift Checklist] ===<br />
===[https://ace.jlab.org/btm/timesheet/eb Beam Time Accounting]===<br />
* '''[https://ace.jlab.org/cdn/doc/btm/userguide.pdf Beam Time Accounting User Guide]'''.<br />
===[https://accweb.acc.jlab.org/hco/readiness Hot Checkout]===<br />
<br />
| valign=top |<br />
==Manuals==<br />
=====Systems=====<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/beamline/manual/beamline_manual.pdf Beamline]<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/torus/Hall_B_Torus_Power-Up_and_Power-Down_Procedure.pdf Torus]<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/torus/Hall_B_Solenoid_Power-Up_and_Power-Down_Procedure.pdf Solenoid]<br />
* [https://docs.google.com/document/d/1kBNmLYg2gqa4XjWgMpbh0rBUxkSAupqdnMV4THepv7k/edit#heading=h.13kef88y2w8q Cryotarget]<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/daq/opman_master.pdf DAQ]<br />
* [[Media:clas12controls_shift.pdf|Slow Controls]]<br />
=====Detectors=====<br />
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/dc/Drift-chamber-operating-procedure.pdf DC]<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/ftof/ftof_manual.pdf FTOF]<br />
* [https://clasweb.jlab.org/wiki/images/a/a2/Ec_manual.pdf ECAL]<br />
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/ltcc/manual/ltcc_manual.pdf LTCC]<br />
* [https://clasweb.jlab.org/wiki/images/f/f1/HTCC_MANUAL.pdf HTCC]<br />
* RICH: [https://github.com/JeffersonLab/clas12-manuals/raw/master/rich/RICH_Manual.pdf Expert] [https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf Shift]<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/ctof/ctof_manual.pdf CTOF]<br />
* [https://clasweb.jlab.org/wiki/images/9/97/Ops_manual_cnd.pdf CND]<br />
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/svt/svt_operation_manual.pdf SVT]<br />
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/mm/Documentation_Shifters_MVT.pdf MVT] and its [https://wiki.jlab.org/clas12-run/images/b/bf/MVT_for_Dummies.pdf Turn-on procedure]<br />
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/ft/FT-Manual.pdf FT]<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/band/band_om.pdf BAND]<br />
<br />
=====Software=====<br />
* [https://wiki.jlab.org/clas12-run/images/c/c9/CedManual.pdf CED]<br />
* [https://wiki.jlab.org/clas12-run/images/f/fd/CLAS12Mon_documentation.pdf mon12]<br />
<br />
| valign=top |<br />
==Procedures==<br />
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam]<br />
* [[Media:clas12moller.pdf|Performing M&oslash;ller Runs]]<br />
* [[Media:HarpScanManual.pdf|Performing Harp Scans]]<br />
* [https://wiki.jlab.org/hps-run/images/0/0c/Accessing_the_tunnel.pdf Accessing the Tunnel/Hall]<br />
<br />
==Logbooks==<br />
<font size=3><br />
* [https://logbooks.jlab.org/book/elog MCC]<br />
* [https://logbooks.jlab.org/book/halog Hall-A]<br />
* [https://logbooks.jlab.org/book/hblog Hall-B]<br />
* [https://logbooks.jlab.org/book/hclog Hall-C]<br />
* [https://logbooks.jlab.org/book/hdlog Hall-D]<br />
</font><br />
<br />
|}<br />
<br />
= Phone Numbers =<br />
<!--####################################### PHONE NUMBERS #############################################--><br />
{{PhoneNumbers}}<br />
<!--- JUST MODIFY AND SAVE ANYTHING IN THIS COMMENT BLOCK TO FORCE A REFRESH OF THE PHONE NUMBERS TEMPLATE! --><br />
<br />
<!--####################################### Short Term Schedule #############################################--><br />
= Short Term Schedule =<br />
<br />
'''[https://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&action=edit Click to Edit]''' solely this tab. P.S.: You must click on the top Edit, next to Read, followed by "Save changes" to force the current page to refresh. <br><br />
<br />
{{ShortTermSchedule-RGK}}<br />
<br />
<!--####################################### GENERAL INFORMATION #############################################--><br />
= General Information =<br />
<br />
This tab contains information on <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
*'''Beam Restoration'''<br />
<br />
== '''Recent Changes''' ==<br />
<br />
=== New '''MVT LV''' Reboot Procedure ===<br />
See '''https://logbooks.jlab.org/entry/4217011''' for detailed information on rebooting the MVT LV when observing a drop in BMT strip occupancies. This gets done upon request of DAQ or MVT expert only.<br />
* Turn '''LV OFF from MVT Overview->Low Voltage->MVT-All'''. LV status indicators should change from green to black; <br />
* '''Wait 20 seconds''', then '''turn LV back from the same menu'''.<br />
* In the alarm handler, with a 2-minute alarm delay, there can be an alarm "NActiveCrates", the status is also seen on the MVT Overview GUI. This alarm will be cleared 2 min after LV is turned back ON. <br />
* Reboot mvt1, mvt2, and mvt3 ROCS. <br />
* Start a run with restart DAQ (Cancel &rarr; Reset &rarr; Configure &rarr; Download &rarr; Prestart &rarr; Go). <br />
* '''If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert'''. <br />
<br />
=== RICH issues ===<br />
* The RICH fibers alarm leads to web guidance aka logbook entry [https://logbooks.jlab.org/entry/3562273 3562273 - RICH recovery procedure]. <br />
* Check the RICH manual for the current guidance: '''https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf'''<br />
* See below for current issues<br />
<br />
=== Rapid/Controlled Access to the Hall ===<br />
* Ask MCC to stop the beam. Wait for the beacon to stop flashing (15-20 minutes) before access. Rapid access is controlled access without RadCon.<br />
* After higher beam current or a Moller run, the beacon will not stop flashing anytime soon. Then, escorted access, viz the ARM, is needed. In that case, keep the beam until the ARM arrives at the Counting House.<br />
<br />
=== 24/7 ZOOM connection for Counting House ===<br />
* Click on [https://jlab-org.zoomgov.com/j/1618614939 https://jlab-org.zoomgov.com/j/1618614939], included in "Remote Shifts" in tab "Shift Worker" <br />
* choose the option to "'''join from browser'''" (''Chrome is recommended'') and ignore all other messages to update the ZOOM APP in the pop-up windows,. <br />
* Enter the passcode from the logbook entry in tab "Shift Worker"<br />
<br />
<br />
== '''Current Issues''' == <br />
<br />
=== Lights in the Hall ===<br />
The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF because of light leaks of some of the detectors. If these lights are switched on during an access, they '''should be switched off when leaving the Hall'''. <br />
* Refer to these photos: ON: [https://logbooks.jlab.org/entry/3825712], OFF: [https://logbooks.jlab.org/entry/3825731]<br />
* We have a '''new dome light switch outside of the hall''' in the labyrinth. See logbook entry: https://logbooks.jlab.org/entry/4204460<br />
* When the dome lights are switched off, they cannot be turned back on immediately, they require 10-15 min to cool down.<br />
<br />
=== Beamline ===<br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
*'''After the HWP change''' <br />
** The absolute values of the SLM and FCUP '''charge asymmetry''' (Q-Asym) should be less than 0.1%. If they are not, contact the Beamline Expert.<br />
** Start a new run<br />
* '''Tagger Magnet Procedure:''' If the tagger magnet needs to be turned off, tell the operator to '''ONLY''' use '''the script for degaussing, NEVER do it "by hand"!''' The latter method might/will trip the circuit breaker for the power supply in the Hall.<br />
<br />
=== BMT / SVT ===<br />
* If new hot channels appear, '''call the SVT/MM expert Yuri Gotra''' (757-541-7539). These channels need to be addressed by the expert.<br />
* '''BMT HV trips''': no screenshots are necessary, power-cycle the channel HV '''as fast as possible''' (the ''underlying script will take care of ramping it up''), note the information in the shift summary. If the same channel trips frequently, ask the expert on call for guidance.<br />
* BMT HV S1 L2 STRIP in safe mode (low voltage) by expert - appears blue in MVT overview<br />
* BMT HV S1 L5 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview<br />
* BMT HV S2 L6 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview<br />
<br />
=== CND ===<br />
* CAMAC crate alarm: <br />
** CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, can be done via the alarm handler. <br />
** After reboot, the CFD thresholds need to be set by running a script, see page 12 in the CND manual at tab "General", https://clasweb.jlab.org/wiki/images/9/97/Ops_manual_cnd.pdf<br />
<br />
=== DAQ ===<br />
* Some ROCs keep printing error messages while functioning properly; please see their list in this logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] to avoid unnecessary reboots since the printout in the ROC terminal won't change. The message will appear in the DAQ run control if they get disconnected! <br />
* <font color=red>'''NEW STANDARD''' end and start of the run:</font> End run, Cancel, Reset, <u> Download</u> , Prestart, Go. This will ensure proper compression of the FADCs and therefore a smaller data rate.<br />
* roc reboot instructions:<br />
** To reboot i.e. adcecal1, type on a clasrun terminal: clasrun> roc_reboot adcecal1<br />
** To check that the crate is back alive, type:clasrun> ping adcecal1<br />
** The ping will start to answer as soon as the crate communicates again. <br />
<br />
=== DC ===<br />
* Make sure to log every DC trip in the shift summary. Make sure to list WHERE and why, possibly, the trip occurred.<br />
<br />
=== ECAL/PCAL ===<br />
* "ECAL_SEC6_UO26 Noisy" https://logbooks.jlab.org/entry/4241957<br />
* "PCAL_HV_SEC2_U25 turned off" https://logbooks.jlab.org/entry/4247187, https://logbooks.jlab.org/entry/4247400<br />
<br />
=== FTOF ===<br />
* FTOF S2 Paddle 19-left and S4 Paddle 16-left are known to be "weak" channels that tend to come and go depending on torus polarity and rates. This cannot be fixed during this run period; see https://logbooks.jlab.org/entry/4219555 and https://logbooks.jlab.org/entry/4219876.<br />
* "FTOF HV Adjustment - S5 P2 2R" https://logbooks.jlab.org/entry/4249754<br />
<br />
=== RICH ===<br />
* '''Known problematic PMTs and tile''':<br />
** You don't need to report about it.<br />
** PMT 2 (sector 1) and PMT 92 (sector 4) are not completely dead and may be visible depending on statistics.<br />
** Problematic tiles and PMTs:<br />
*** Sector 1 Tile 21 dead (PMT 55,56,57)<br />
*** Sector 1 Tile 1 PMT 2<br />
*** Sector 4 Tile 34 PMT 92<br />
<br />
== '''Beam Restoration''' == <br />
<br />
* Study the manual: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam]. If you do not feel confident to do this by yourself, contact the Beamline Expert.<br />
<br />
* Find all Reference values on the white board at tab Short_Term_Schedule<br />
<br />
=== Restoring Beam after Short Downtime ===<br />
<br />
* Ask for 5 nA beam current and check the 2C24A and 2H01 beam (x, y) positions against the Reference Values (tab "Short Term Schedule") after <br />
** beam steering or orbit change<br />
** change in beam current, e.g., after a target change<br />
** If BPM 2C24A and 2H01 positions are off, (not within +/-0.1 mm), ask MCC to bring them to the reference values<br />
<br />
=== Beam Tuning to Tagger Yoke Dump ===<br />
<br />
Study the manual: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam]. <br />
* Contact Eugene Pasyuk if issues arise.<br />
<br />
* Ask MCC to energize the tagger magnet<br />
:- blank collimator<br />
:- beam type "Photon"<br />
<br />
* All CLAS12 detectors HV off (BMT HV in safe mode)<br />
<br />
* Ask MCC to mask the beam halo counters (FSDs: Upstream, Midstream, Downstream, BOM) <br />
* Ask MCC for 5 nA beam current and make sure the Orbit Locks are OFF;<br />
* If necessary, ask MCC to bring the 2C21A and 2C24A beam positions to the Reference Values<br />
* Take harp scans<br />
:- at Harp 2C21A (Upstream Right Counter)<br />
:- at Tagger Harp 2C24A Upstream Right Counter)<br />
* If the beam trips, abort the scan and restart. The beam must be on during the scan, otherwise the fit to the beam profile will not work. <br />
* Compare the results with the Harp Scan References <br />
* The fit ranges might need to be adjusted manually to assess the fit results<br />
<br />
* If good, log the new scan results.<br />
<br />
=== M&oslash;ller run ===<br />
<br />
Follow the standard procedure as described in the manual [https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf Performing M&oslash;ller Runs].<br />
* Contact Nathan Baltzell if issues arise<br />
<br />
A few points to note:<br />
* '''Request 20 nA''' , Orbit Locks should be off<br />
* The BPMs 2C21 and 2C24A may be out of range after the M&oslash;ller configuration. <br />
* Keep running until the polarization uncertainty is < 1.5%<br />
<br />
=== Beam Tuning to Faraday Cup ===<br />
<br />
Study the manual: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam], and take into account the first steps mentioned therein. <br />
<br />
This is typically done after tuning to the tagger dump (and possibly taking a Moller run).<br />
<br />
* All CLAS12 detectors HV off (BMT HV in safe mode)<br />
<br />
* Ask MCC to de-energize the tagger magnet<br />
:- 20 mm collimator<br />
:- beam type electron<br />
:- beam blocker out<br />
* If initial beam tune, target should be "Empty"<br />
* Ask MCC to unmask beam halos<br />
* Set the halo counter FSD thresholds to 1 MHz and the integration time interval to 50 milliseconds<br />
* Insert the Downstream Viewer, Chromax, in the beamline<br />
* Ask MCC for 5 nA beam current<br />
* If necessary, ask MCC to bring the beam positions at 2C24A and 2H01 to the Reference Values<br />
* Take a harp scan at 2H01 (Midstream Left)<br />
* If the beam trips, abort and restart. The beam must be on during the scan, otherwise the fit to the beam profile will not work. <br />
* Compare the results with the Harp Scan References <br />
* If good, log the new scan results.<br />
<br />
Once done and before resuming the production data-taking:<br />
* Retract the Downstream Viewer from the beamline<br />
* Put the FSDs thresholds and integration time to their reference values<br />
* Turn all detector HV ON, for MVT "HV ON - Full Voltage"<br />
* MCC might need to adjust the beam positions after going to the production beam current.<br />
<br />
<br />
<!--####################################### Shift Expert ################################################--><br />
= Shift Expert =<br />
<br />
Come to your shift in time for the '''shift change''', 10-15 minutes before the start of your shift. <br />
* If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
Follow the '''Short Term Schedule'''<br />
* The RC must be notified before changing run conditions<br />
<br />
Operate the '''Data Acquisition'''<br />
<br />
Take action on and log '''alarms'''<br />
<br />
At '''the end of the shift''', submit the '''strip charts''' to the logbook <br />
* If they are not up already: (CS-Studio &rarr; Tools &rarr; Strip Charts &rarr; livePlot)<br />
* Right click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters"<br />
* Choose a '''time-span width of 10 hours''' (right-click below x-axis)<br />
* <font color=red> To make a logbook entry:</font><br />
:- Right click within the grid of one of the charts, choose "Make Logbook Entry"<br />
:- The title of the logbook entry can be changed, eg to Strip charts<br />
:- Un-click ELOG, select HBLOG, and click on "Make Entry" to submit<br />
<br />
'''Communicate''' with your co-shift person:<br />
* Remind them to read the tab 'Shift Worker'.<br />
* Discuss any issues with the shift worker before making extra logbook entries.<br />
* Remind the shift worker of the '''end-of-shift Checklist'''.<br />
* <font color=red> Use the CS-Studio '''Logbook entry tool''' for all screen shots (but the strip charts)!</font><br />
* Note that the Logbook Entry tool puts the entry in the HBRUN logbook by default. Other logbooks can be added or selected from the drop down menu. <br />
<br />
<br />
Check for and read any comments to '''log-book entries''' made during your shift.<br />
<br />
Keep your '''shift summary''' up to date in HBLOG. Record all significant happenings. <br />
* Refer to relevant logbook entries in the shift summary.<br />
* Include a run list for the shift with relevant run information.<br />
<br />
Ensure that all '''monitoring plots''' and are logged and checked against the reference plots for every single run.<br />
* Both, you and the shift worker should run mon12 and '''reset & check spectra frequently'''.<br />
<br />
* If the worker shift is remote, maintain communication over Zoom. <br />
<br />
* If you have any other questions or uncertainties about what to do, call the RC.<br />
<br />
The shift worker (if in person) should log the '''clas12online'' reconstruction plots at the end of a run. Running the program on more than one CH computer has been causing problems.<br />
<br />
In case of '''RICH issues''', check the RICH manual for the current guidance: https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf<br />
<br />
'''New MVT LV Reboot Procedure''' can be found at tab 'GENERAL INFORMATION'.<br />
<br />
<br />
'''[https://ace.jlab.org/btm Fill out BTA]''' hourly;<br />
* Accelerator beam time (do not change these values):<br />
** ABU: acceptable beam used <br />
** BANU: beam acceptable but not used (should be reflected in our PCC and UED)<br />
** BNA: beam not acceptable (e.g., tuning, drifting, not focused)<br />
** ACC: Accelerator Configuration Change (e.g., pass change)<br />
** OFF: Accelerator is down<br />
* Experiment beam time (do change these values):<br />
** ER: Experiment ready (should be 60 minutes - PCC - UED)<br />
** PCC: Planned configuration change (when the beam is masked while radiators are moved, target change, DAQ (stopping/starting runs, tests, etc.)<br />
** UED: Unplanned experiment down (hardware failure, DAQ crashes, our problems, ...)<br />
** ''Exception'': ''BANU, due to time spent on beam tuning and BPM checks after beam down, should be counted as ER on our side''.<br />
* Enter fields at the "Shift Information" tab.<br />
* You must save at 7:00, 15:00, and 23:00, to send info to MCC. To see the save button, click 'edit all' or 'edit cc hours.' <br />
* Acknowledge the popup error message about the last hour not being completed by clicking OK.<br />
* Sign, viz log completed 8-hour sheet. <br />
* '''Note: we can change the time sheet up to 48 hours after completion.''' <br />
<br />
<br />
<!--####################################### Shift Worker ################################################--><br />
= Shift Worker =<br />
<br />
Come to your shift in time for the '''shift change''', 10-15 minutes before the start of your shift;<br />
* If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
Discuss any issue with the shift expert before making extra logbook entries; ask the shift expert to note the ongoing issue in the shift summary.<br />
<br />
<font color=red> Use the CS-Studio '''Logbook entry tool''' for all screen shots (but the strip charts)! </font><br />
<br />
=== Frequently ===<br />
<br />
Reset and check non12 histograms frequently, preferably each 1h<br />
* Note that some plots have radio buttons at the bottom to choose the sector. Remember to cycle through and check all sectors.<br />
<br />
=== Once per run ===<br />
<br />
Note that the CS-Studio '''Logbook Entry tool''' puts the entry in the HBRUN logbook by default. Other logbooks can be added or selected from the drop down menu. <br />
<br />
Using the Logbook Entry tool, submit EPICS '''screenshots''' to the HBRUN logbook (one logbook entry) '''with beam ON'''<br />
# Beamline overview (remote shift: in VNC or [https://hallbopi.jlab.org/webopi3.3/w?opi=beamline/clas12-web.opi Web Browser])<br />
# DAQ status<br />
# CLAS12 trigger rates <br />
<br />
Upload '''mon12''' monitoring plots to the logbook with sufficient statistics and compare them to the reference and recent uploads (see {{#switchtablink:Monitoring|Monitoring}} tab).<br />
<br />
At the '''end of the run''', submit the '''strip charts''' to the logbook <br />
* If they are not up already: (CS-Studio &rarr; Tools &rarr; Strip Charts &rarr; livePlot)<br />
* Right click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters"<br />
* Choose a '''time-span width of 4 hours''', compatible with the run duration (right-click below x-axis)<br />
* <font color=red> To make a logbook entry:</font><br />
:- Right click within the grid of one of the charts, choose "Make Logbook Entry"<br />
:- The title of the logbook entry can be changed, eg to Strip charts<br />
:- Un-click ELOG, select HBLOG, and click on "Make Entry" to submit<br />
<br />
At the '''end of the run''', upload the '''[https://github.com/JeffersonLab/caos/tree/main#readme clas12online]''' plots to the logbook.<br />
* The program can continue through a standard end/start of a run. However, after a DAQ restart, you must back out and restart clas12online.<br />
* If the DAQ has to be restarted, you can still make the upload before backing out.<br />
<br />
<br />
=== Once per shift ===<br />
<br />
Fill the '''[https://logbooks.jlab.org/checklists/151 shift checklist]''';<br />
* During production, get relevant values from the epics screens Beamline Overview, CLAS12 DAQ Status and CLAS12 Trigger;<br />
* During extended downtime, get relevant values from the latest EPICS screenshots that you made during production <br />
<br />
== For Remote Shifts ==<br />
<font color=red>'''Please inform the PDL that your shifts will be remote.''' </font color=red> <br />
Remote shifts are listed [[upcoming-remote-shifts|here]]<br />
<br />
You must test your setup, including Zoom and VNC connections, at least 24 hours before your first shift!<br />
* Zoom for 24-7 communication with counting house:<br />
** In the Zoom app: [https://jlab-org.zoomgov.com/j/1618614939 https://jlab-org.zoomgov.com/j/1618614939]<br />
** Or in a web browser: [https://jlab-org.zoomgov.com/wc/1618614939/join?pwd=U003MnRuNVdiU1EzaFpXV0JuNWV1Zz09 https://jlab-org.zoomgov.com/wc/1618614939/join?pwd=U003MnRuNVdiU1EzaFpXV0JuNWV1Zz09]<br />
** The passcode is required and contained in [https://logbooks.jlab.org/entry/4158818 this log entry]<br />
** Remind the expert in the counting house to restart their ZOOM, if necessary<br />
* Remote VNC connection instructions: https://logbooks.jlab.org/entry/3906039<br />
* '''If you mistyped''' (username, pincode, passcode,...) a string of numbers will appear with text asking you to respond to this challenge. Back out with ctrl_c and you get another try! After N+1 mistypes you will be locked out. For several hours after that you will not even be able to get to the public JLab webpages.<br />
** All necessary applications should be available from the desktop menu (left/right click on the desktop)<br />
** EPICS GUIs should be accessed '''ONLY''' via the desktop menu or by running <tt>clascss-remote</tt>.<br />
<!--* [https://userweb.jlab.org/~baltzell/clas12/shift/remote-demo.mp4 Remote Demonstration Video (150 MB)]--><br />
** Some charts are also accessible via web browser: [https://epicsweb.jlab.org/wave/?myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Upstream+and+Midstream+Halo+Counters&fullscreen=false&layoutMode=2&viewerMode=2&pv=scaler_cS3b&pv=scaler_cS4b&pv=scaler_cS6b&pv=scaler_cS12b&pv=scaler_cS13b&pv=scaler_cS14b&pv=scaler_cS15b&scaler_cS3blabel=scaler_cS3b&scaler_cS3bcolor=%23a6cee3&scaler_cS3byAxisLabel=Rate++%28Hz%29&scaler_cS3byAxisMin=&scaler_cS3byAxisMax=&scaler_cS3byAxisLog&scaler_cS3bscaler=&start=2020-08-08+09%3A02%3A36&end=2020-08-08+09%3A07%3A36&scaler_cS4blabel=scaler_cS4b&scaler_cS4bcolor=%231f78b4&scaler_cS4byAxisLabel=&scaler_cS4byAxisMin=&scaler_cS4byAxisMax=&scaler_cS4byAxisLog=&scaler_cS4bscaler=&scaler_cS5byAxisLabel=&scaler_cS5byAxisMin=&scaler_cS5byAxisMax=&scaler_cS5byAxisLog=&scaler_cS5bscaler=&scaler_cS6blabel=scaler_cS6b&scaler_cS6bcolor=%2333a02c&scaler_cS6byAxisLabel=&scaler_cS6byAxisMin=&scaler_cS6byAxisMax=&scaler_cS6byAxisLog=&scaler_cS6bscaler=&scaler_cS7byAxisLabel=&scaler_cS7byAxisMin=&scaler_cS7byAxisMax=&scaler_cS7byAxisLog=&scaler_cS7bscaler=&scaler_cS12blabel=scaler_cS12b&scaler_cS12bcolor=%23e31a1c&scaler_cS12byAxisLabel=&scaler_cS12byAxisMin=&scaler_cS12byAxisMax=&scaler_cS12byAxisLog=&scaler_cS12bscaler=&scaler_cS13blabel=scaler_cS13b&scaler_cS13bcolor=%23fdbf6f&scaler_cS13byAxisLabel=&scaler_cS13byAxisMin=&scaler_cS13byAxisMax=&scaler_cS13byAxisLog=&scaler_cS13bscaler=&scaler_cS14blabel=scaler_cS14b&scaler_cS14bcolor=%23ff7f00&scaler_cS14byAxisLabel=&scaler_cS14byAxisMin=&scaler_cS14byAxisMax=&scaler_cS14byAxisLog=&scaler_cS14bscaler=&scaler_cS15blabel=scaler_cS15b&scaler_cS15bcolor=%23cab2d6&scaler_cS15byAxisLabel=&scaler_cS15byAxisMin=&scaler_cS15byAxisMax=&scaler_cS15byAxisLog=&scaler_cS15bscaler= Upstream/Midstream Halo Counters], [https://epicsweb.jlab.org/wave/?myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Downstream+Halo+Counters&fullscreen=false&layoutMode=2&viewerMode=2&pv=scalerS8b&pv=scalerS9b&scalerS8blabel=scalerS8b&scalerS8bcolor=%23a6cee3&scalerS8byAxisLabel=Rate++%28Hz%29&scalerS8byAxisMin=&scalerS8byAxisMax=&scalerS8byAxisLog&scalerS8bscaler=&pv=scalerS10b&pv=scalerS11b&scalerS9blabel=scalerS9b&scalerS9bcolor=%231f78b4&scalerS9byAxisLabel=&scalerS9byAxisMin=&scalerS9byAxisMax=&scalerS9byAxisLog=&scalerS9bscaler=&scalerS10blabel=scalerS10b&scalerS10bcolor=%23b2df8a&scalerS10byAxisLabel=&scalerS10byAxisMin=&scalerS10byAxisMax=&scalerS10byAxisLog=&scalerS10bscaler=&scalerS11blabel=scalerS11b&scalerS11bcolor=%2333a02c&scalerS11byAxisLabel=&scalerS11byAxisMin=&scalerS11byAxisMax=&scalerS11byAxisLog=&scalerS11bscaler= Downstream Halo Counters], [https://epicsweb.jlab.org/wave/?start=2020-07-08+16%3A50%3A02&end=2020-07-08+16%3A55%3A02&myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Beam+Currents&fullscreen=false&layoutMode=2&viewerMode=2&pv=IPM2C21A&pv=IPM2C24A&pv=scaler_calc1b&IPM2C21Alabel=IPM2C21A&IPM2C21Acolor=%23a6cee3&IPM2C21AyAxisLabel=Beam+Current+%28nA%29&IPM2C21AyAxisMin=0&IPM2C21AyAxisMax=300&IPM2C21AyAxisLog&IPM2C21Ascaler=&scaler_calc1blabel=Faraday+Cup&scaler_calc1bcolor=%23b2df8a&scaler_calc1byAxisLabel=&scaler_calc1byAxisMin=&scaler_calc1byAxisMax=&scaler_calc1byAxisLog&scaler_calc1bscaler= Beam Currents], [https://epicsweb.jlab.org/wave/?start=2020-08-03+12%3A30%3A57&end=2020-08-03+12%3A35%3A57&myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=BPM+Positions+%28Y-Axis+is+mean+%2B%2F-+0.5+mm%29&fullscreen=false&layoutMode=3&viewerMode=2&pv=IPM2C24A.XPOS&pv=IPM2C24A.YPOS&pv=IPM2H01.XPOS&pv=IPM2H01.YPOS&IPM2C24A.XPOSlabel=IPM2C24A.XPOS&IPM2C24A.XPOScolor=%23e31a1c&IPM2C24A.XPOSyAxisLabel=&IPM2C24A.XPOSyAxisMin=-2.0&IPM2C24A.XPOSyAxisMax=+1.0&IPM2C24A.XPOSyAxisLog&IPM2C24A.XPOSscaler=&IPM2C24A.YPOSlabel=IPM2C24A.YPOS&IPM2C24A.YPOScolor=pink&IPM2C24A.YPOSyAxisLabel=&IPM2C24A.YPOSyAxisMin=-2.0&IPM2C24A.YPOSyAxisMax=1.0&IPM2C24A.YPOSyAxisLog&IPM2C24A.YPOSscaler=&IPM2H01.XPOSlabel=IPM2H01.XPOS&IPM2H01.XPOScolor=darkgreen&IPM2H01.XPOSyAxisLabel=&IPM2H01.XPOSyAxisMin=-2.0&IPM2H01.XPOSyAxisMax=1.0&IPM2H01.XPOSyAxisLog&IPM2H01.XPOSscaler=&IPM2H01.YPOSlabel=IPM2H01.YPOS&IPM2H01.YPOScolor=lightgreen&IPM2H01.YPOSyAxisLabel=&IPM2H01.YPOSyAxisMin=-2.0&IPM2H01.YPOSyAxisMax=1.0&IPM2H01.YPOSyAxisLog&IPM2H01.YPOSscaler=#a6cee3&IPM2C24A.XPOSyAxisLabel=2C24+X+(mm)&IPM2C24A.XPOSyAxisMin=-1.5&IPM2C24A.XPOSyAxisMax=-0.5&IPM2C24A.XPOSyAxisLog&IPM2C24A.XPOSscaler=&IPM2C24A.YPOSlabel=IPM2C24A.YPOS&IPM2C24A.YPOScolor=%231f78b4&IPM2C24A.YPOSyAxisLabel=2C24+Y+(mm)&IPM2C24A.YPOSyAxisMin=0.3&IPM2C24A.YPOSyAxisMax=1.3&IPM2C24A.YPOSyAxisLog&IPM2C24A.YPOSscaler=&IPM2H01.XPOSlabel=IPM2H01.XPOS&IPM2H01.XPOScolor=pink&IPM2H01.XPOSyAxisLabel=2H01+X+(mm)&IPM2H01.XPOSyAxisMin=-0.6&IPM2H01.XPOSyAxisMax=0.4&IPM2H01.XPOSyAxisLog&IPM2H01.XPOSscaler=&IPM2H01.YPOSlabel=IPM2H01.YPOS&IPM2H01.YPOScolor=darkred&IPM2H01.YPOSyAxisLabel=2H01+Y+(mm)&IPM2H01.YPOSyAxisMin=0.4&IPM2H01.YPOSyAxisMax=1.4&IPM2H01.YPOSyAxisLog&IPM2H01.YPOSscaler= BPM Positions]<br />
<br />
<br />
<!--####################################### Run Coordinator ################################################--><br />
= Run Coordinator =<br />
<br />
Check the '''upcoming shifts''', and if necessary, coordinate with the PDL to contact shift takers about their training and site access status.<br />
<br />
'''Remote shifts''' are listed [[Upcoming-remote-shifts|here]].<br />
<br />
'''Backup shift personnel''' is listed [https://jeffersonlab-my.sharepoint.com/:x:/r/personal/baltzell_jlab_org/Documents/Backup%20Shifters.xlsx?d=wf18dc5909cf84424840d73cc9bd8ce8e&csf=1&web=1&e=QwY1fs here].<br />
<br />
'''Meeting ZOOM connections:''' see tab {{#switchtablink:Important Links|Important Links}}<br />
<br />
=== Daily ===<br />
<br />
* '''Report at the PD/RC and attend the MCC/OPS meetings''' (weekdays 7:45 AM and 8 AM Daily, MCC building). The PD will communicate when and how meetings happen on the weekend.<br />
<br />
* Update the run plan in tab '''{{#switchtablink:Short_Term_Schedule|Short Term Schedule}}''' (and on the white board in CH) in coordination with the RG-K experiment coordinators (i.e., Annalisa, Daniel) and communicate it to the shift crew. <br />
<br />
* Log the '''RC Daily summary''' in the HBLOG. <br />
<br />
* Update the '''list of runs''' taken on the [https://docs.google.com/spreadsheets/d/1xplXDIiio_TkimucPBSf7i-bAbbM7mpWzZ1zevt4edQ/edit#gid=0 Google Spreadsheet]<br />
<br />
* '''[[https://ace.jlab.org/btm/timesheet/eb BTA time sheet]''': Make sure, the "Beam Available Not Used" (BANU) time is accounted for as explained at tab {{#switchtablink:Shift_Expert|Shift Expert}}. The BTA information can be modified post-signature.<br />
** NOTE: "After 48 hours you cannot modify a User signed timesheet unless you are the signer, Hall Manager, or Admin"<br />
<br />
* Run the daily '''RC meetings''' in CH Room 200C and on ZOOM<br />
** Mo-Tu,Th-Fr at 13:00 ET in the Counting House Conference Room<br />
** Wednesdays at 3 PM, zoom only<br />
** Weekends upon agreement<br />
** Send a '''daily invitation''' for the RC meeting to mailing lists hallb, clas12_rgk, clas_members.<br />
** Keep the '''Daily RC Meeting Minutes''' at [https://clasweb.jlab.org/wiki/index.php/Run_Group_K Run_Group_K wiki], tab "RGK FALL 2023 / SPRING 2024" <br />
<br />
* Connect to '''Zoom in CH Room 200C''':<br />
** Turn on the projector with the white remote control, then log into your CUE account. If not listed yet, click "Not listed?" in the bottom left to add your account. <br />
** Once logged in, use the recommended Google Chrome to join the ZOOM meeting on the browser or use the ZOOM application. <br />
** Since the room doesn't have audio, don't connect with the computer audio, but choose "Call Me," then enter the number in the small Cisco answering device. Once it rings, answer the call, and you will be prompted to join the meeting. <br />
** The room has a camera, which can be turned on via ZOOM. <br />
<br />
=== Weekly ===<br />
<br />
*'''MCC/OPS planning meeting''', on Wednesdays at 13:30, MCC building.<br />
** Submit (save) the online form '''[https://ace.jlab.org/apps/pd/run-coordinator-reports Run Coordinator Weekly Summary]''' before the meeting and present the contents at the meeting.<br />
** The summary covers the data taking status '''from 7 am on the previous Wednesday to 7 am on the current Wednesday'''.<br />
** '''Beam time accounting''': [https://ace.jlab.org/btm/reports/physics-summary Beam Time Manager; Physics Time Accounting]<br />
** For the '''percentage of scheduled experiment hours to date''' contact Daniel Carman.<br />
** The '''total experiment data collected to date''' can be retrieved from the up-to-date "Accumulated Charge" depicted at [https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.html]<br />
<br />
*'''Hall B meeting''' is on Mondays at 9 AM. Present your summary slides that should be sent beforehand to the Hall B leader, Patrick Achenbach. <br />
<br />
<br />
<!--####################################### MONITORING ################################################--><br />
= Monitoring =<br />
<br />
{| {{TableStyle1}}<br />
| valign=top |<br />
=== Webcams ===<br />
* [http://cctv1.jlab.org Tagger Beam Dump Viewer]<br />
* [http://hallbcam02.jlab.org Hall Fisheye]; [http://hallbcam00.jlab.org/aca/index.html#view Additional Hall Cams]<br />
* Faraday Cup beam viewer<br />
** To reboot it, run <tt>beam-viewer-reboot</tt><br />
* Counting House Cameras: [https://www.jlab.org/~baltzell/ch-abcd.html 2x2], [https://hallach-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall A], [https://hallbch-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall B], [https://hallcch-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall C], [https://halldch-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall D]<br />
<br />
| valign=top |<br />
=== EPICS ===<br />
* [https://hallbopi.jlab.org/webopi3.3/w?opi=beamline/clas12-web.opi Hall B] (CUE Login)<br />
* [https://epicsweb.jlab.org epicsweb]<br />
:&bull; [https://epicsweb.jlab.org/wedm/screen?edl=/cs/opshome/edm/wall/Status_W_Accel.edl Accelerator Status]<br />
:&bull; [https://epicsweb.jlab.org/wave Strip Charts]<br />
<br />
| valign=top |<br />
=== Data Quality ===<br />
* mon12 histograms: [https://clas12mon.jlab.org/mon12/histograms/?reference=4254919 reference (run 19734)]<br />
* [https://clasweb.jlab.org/hydra/dashboard2.html Hydra] (CUE Login) Google-Chrome ONLY, Not Firefox!<br />
* [https://github.com/JeffersonLab/caos/tree/main#readme clas12mltrack/clas12online]: <br />
:&bull; '''New'''; displaying real-time reconstructed vertices & various event topologies<br />
* [https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.html Data Accumulation Timeline] [https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.pdf PDF] [https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.xlsx Excel Spreadsheet] <br />
|}<br />
<br />
<!--####################################### Important Links ################################################--><br />
= Important Links =<br />
<br />
{| {{TableStyle1}}<br />
| valign=top |<br />
===Hall-B===<br />
* [https://clasweb.jlab.org/wiki/index.php/CLAS12_OPS_Doc Operation Safety Procedures]<br />
* [https://clasweb.jlab.org/wiki/index.php/Run_Group_K Run Group K Analysis Wiki]<br />
* [http://clasweb.jlab.org/rcdb RCDB]<br />
* [https://clasweb.jlab.org/cgi-bin/ccdb/objects CCDB]<br />
<br />
| valign=top |<br />
===Accelerator===<br />
* [http://accboard.acc.jlab.org Accelerator Whiteboard]<br />
* [https://accweb.acc.jlab.org/apps/pd/shift-plans Program Deputy Shift Plans]<br />
* [https://cebaf.jlab.org/pd/run-coordinator-reports Run Coordinator Reports]<br />
* [https://ace.jlab.org/btm/reports/physics-summary Beam Time Accounting Reports]<br />
* [https://opsweb.acc.jlab.org/CSUEApps/PSSestamp/psslog.php?numdays=5&entry_types_wanted%5BACCESS%5D=ACCESS&group_by=AREA&output_format=SCROLLABLE PSS Elog]<br />
* [http://opsweb.acc.jlab.org/internal/ops/ops_webpage/restrictions/ops_restrictions.html Operational Restrictions]<br />
<br />
| valign=top |<br />
===ZOOM Meetings===<br />
* 07:45 [https://jlab-org.zoomgov.com/j/1611456010?pwd=d2RJWTJQRDM0ZkNaZ1dpTmtLWDAwQT09 RC/PD Morning Meeting]<br />
* 08:00 [https://jlab-org.zoomgov.com/j/1601304841?pwd=Z1RIOVVUdkdXL2R2LzREZUNOUlh1dz09 MCC/OPS Morning and Wednesday 1:30 Meeting]<br />
* [https://logbooks.jlab.org/entry/4000274 See also this logbook entry]<br />
* Daily Hall B Run Coordinator Meeting: <br />
** [https://jlab-org.zoomgov.com/j/1613823885?pwd=U0FYcUNObys4dEZmRlNnbG1aVDN4UT09 URL Link] (''including Passcode'')<br />
** Meeting ID: 161 382 3885<br />
** Passcode: see emails<br />
* [https://logbooks.jlab.org/entry/4158818 Hall B Remote Shifts & Counting House]<br />
|}<br />
<br />
<br />
<headertabs/><br />
__NOEDITSECTION__<br />
__NOTOC__<br />
{| {{TableStyle1}}<br />
| valign=top style="text-align:center"|<br />
[[Image:clas12design.png|500px]]<br />
|}</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7440Template:ShortTermSchedule-RGK2024-03-05T15:06:23Z<p>Carman: </p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 5 - Mar. 11, 2024''' ==<br />
<br />
'''Recovery from Torus/Solenoid Fast Dump'''<br />
- At 7:45 a.m. on Mar. 5 we had a second torus/solenoid fast dump incident<br />
- The magnets are recovering and mitigation strategies are now being discussed<br />
- Stay tuned on word for when the RG-K physics program will resume<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
'''Beam Studies Day'''<br />
- Beam goes off on Mar. 6 at 7 a.m.<br />
- Turn DC off and set BMT HV to safe mode; all other detectors remain on<br />
<br />
'''Beam Restore'''<br />
- Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode)<br />
- Tune beam to tagger yoke dump at 5 nA (contact Eugene for questions)<br />
- Take harp scans at 2C21A and 2C24A and compare to reference plots<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive) (contact Nathan for questions)<br />
- Call MCC to change HWP to out (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive)<br />
- Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
- Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
- Take harp scan at 2H01 and compare to reference plot<br />
- When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.<br />
- Turn all detectors off and put BMT HV in safe mode<br />
- Ramp torus and solenoid to zero field (contact Eugene to do this)<br />
- Call to put Hall B in Restricted Access<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7439Template:ShortTermSchedule-RGK2024-03-05T12:32:49Z<p>Carman: /* Run Plan: Mar. 4 - Mar. 11, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 5 - Mar. 11, 2024''' ==<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
'''Beam Studies Day'''<br />
- Beam goes off on Mar. 6 at 7 a.m.<br />
- Turn DC off and set BMT HV to safe mode; all other detectors remain on<br />
<br />
'''Beam Restore'''<br />
- Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode)<br />
- Tune beam to tagger yoke dump at 5 nA (contact Eugene for questions)<br />
- Take harp scans at 2C21A and 2C24A and compare to reference plots<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive) (contact Nathan for questions)<br />
- Call MCC to change HWP to out (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive)<br />
- Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
- Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
- Take harp scan at 2H01 and compare to reference plot<br />
- When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.<br />
- Turn all detectors off and put BMT HV in safe mode<br />
- Ramp torus and solenoid to zero field (contact Eugene to do this)<br />
- Call to put Hall B in Restricted Access<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7438Template:ShortTermSchedule-RGK2024-03-05T03:12:11Z<p>Carman: </p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 4 - Mar. 11, 2024''' ==<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
'''Beam Studies Day'''<br />
- Beam goes off on Mar. 6 at 7 a.m.<br />
- Turn DC off and set BMT HV to safe mode; all other detectors remain on<br />
<br />
'''Beam Restore'''<br />
- Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode)<br />
- Tune beam to tagger yoke dump at 5 nA (contact Eugene for questions)<br />
- Take harp scans at 2C21A and 2C24A and compare to reference plots<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive) (contact Nathan for questions)<br />
- Call MCC to change HWP to out (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive)<br />
- Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
- Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
- Take harp scan at 2H01 and compare to reference plot<br />
- When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.<br />
- Turn all detectors off and put BMT HV in safe mode<br />
- Ramp torus and solenoid to zero field (contact Eugene to do this)<br />
- Call to put Hall B in Restricted Access<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7437Template:ShortTermSchedule-RGK2024-03-04T20:09:05Z<p>Carman: /* Run Plan: Mar. 4 - Mar. 11, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 4 - Mar. 11, 2024''' ==<br />
<br />
'''Remaining Non-Production Runs'''<br />
- <strike>DC HV study - 30 minutes duration - standard production trigger (Florian will coordinate)</strike><br />
- Production run at 90 nA - Florian will check DC trip limits<br />
- DAQ configuration: PROD67_PIN, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Run duration: 90 minutes<br />
- Test with HTCC removed from trigger: (call Valery when ready)<br />
- DAQ configuration: PROD67, Trigger: rgk_noHTCC_noDC_v2.0_300MeV.trg<br />
- Beam current: 75 nA<br />
- Run duration: 2 hrs <br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
'''Beam Studies Day'''<br />
- Beam goes off on Mar. 6 at 7 a.m.<br />
- Turn DC off and set BMT HV to safe mode; all other detectors remain on<br />
<br />
'''Beam Restore'''<br />
- Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode)<br />
- Tune beam to tagger yoke dump at 5 nA (contact Eugene for questions)<br />
- Take harp scans at 2C21A and 2C24A and compare to reference plots<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive) (contact Nathan for questions)<br />
- Call MCC to change HWP to out (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive)<br />
- Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
- Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
- Take harp scan at 2H01 and compare to reference plot<br />
- When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.<br />
- Turn all detectors off and put BMT HV in safe mode<br />
- Ramp torus and solenoid to zero field (contact Eugene to do this)<br />
- Call to put Hall B in Restricted Access<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7436Template:ShortTermSchedule-RGK2024-03-04T17:43:37Z<p>Carman: /* Run Plan: Mar. 4 - Mar. 11, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 4 - Mar. 11, 2024''' ==<br />
<br />
'''Recovery from Magnet Fast Dump'''<br />
- At 12:30 p.m. ramp torus and solenoid to field - Eugene will do this<br />
- Give MCC notice of our schedule when solenoid is at half field (30 minutes until beam needed)<br />
- Request 5 nA to Faraday cup; check beam positions and halo rates<br />
- Ramp up DC and BMT to full voltage<br />
- Resume program<br />
<br />
'''Remaining Non-Production Runs'''<br />
- DC HV study - 30 minutes duration - standard production trigger (Florian will coordinate)<br />
- Production run at 90 nA - Florian will check DC trip limits<br />
- DAQ configuration: PROD67_PIN, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Run duration: 90 minutes<br />
- Test with HTCC removed from trigger: (call Valery when ready)<br />
- DAQ configuration: PROD67, Trigger: rgk_noHTCC_noDC_v2.0_300MeV<br />
- Beam current: 75 nA<br />
- Run duration: 2 hrs <br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
'''Beam Studies Day'''<br />
- Beam goes off on Mar. 6 at 7 a.m.<br />
- Turn DC off and set BMT HV to safe mode; all other detectors remain on<br />
<br />
'''Beam Restore'''<br />
- Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode)<br />
- Tune beam to tagger yoke dump at 5 nA (contact Eugene for questions)<br />
- Take harp scans at 2C21A and 2C24A and compare to reference plots<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive) (contact Nathan for questions)<br />
- Call MCC to change HWP to out (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive)<br />
- Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
- Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
- Take harp scan at 2H01 and compare to reference plot<br />
- When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.<br />
- Turn all detectors off and put BMT HV in safe mode<br />
- Ramp torus and solenoid to zero field (contact Eugene to do this)<br />
- Call to put Hall B in Restricted Access<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7435Template:ShortTermSchedule-RGK2024-03-04T17:41:55Z<p>Carman: /* Run Plan: Mar. 4 - Mar. 11, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 4 - Mar. 11, 2024''' ==<br />
<br />
'''Recovery from Magnet Fast Dump'''<br />
- At 12:30 p.m. ramp torus and solenoid to field - Eugene will do this<br />
- Give MCC notice of our schedule when solenoid is at half field (30 minutes until beam needed)<br />
- Request 5 nA to Faraday cup; check beam positions and halo rates<br />
- Ramp up DC and BMT to voltage<br />
- Resume program<br />
<br />
'''Remaining Non-Production Runs'''<br />
- DC HV study - 30 minutes duration - standard production trigger (Florian will coordinate)<br />
- Production run at 90 nA - Florian will check DC trip limits<br />
- DAQ configuration: PROD67_PIN, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Run duration: 90 minutes<br />
- Test with HTCC removed from trigger: (call Valery when ready)<br />
- DAQ configuration: PROD67, Trigger: rgk_noHTCC_noDC_v2.0_300MeV<br />
- Beam current: 75 nA<br />
- Run duration: 2 hrs <br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
'''Beam Studies Day'''<br />
- Beam goes off on Mar. 6 at 7 a.m.<br />
- Turn DC off and set BMT HV to safe mode; all other detectors remain on<br />
<br />
'''Beam Restore'''<br />
- Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode)<br />
- Tune beam to tagger yoke dump at 5 nA (contact Eugene for questions)<br />
- Take harp scans at 2C21A and 2C24A and compare to reference plots<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive) (contact Nathan for questions)<br />
- Call MCC to change HWP to out (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive)<br />
- Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
- Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
- Take harp scan at 2H01 and compare to reference plot<br />
- When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.<br />
- Turn all detectors off and put BMT HV in safe mode<br />
- Ramp torus and solenoid to zero field (contact Eugene to do this)<br />
- Call to put Hall B in Restricted Access<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7434Template:ShortTermSchedule-RGK2024-03-04T17:08:07Z<p>Carman: </p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 4 - Mar. 11, 2024''' ==<br />
<br />
'''Recovery from Magnet Fast Dump'''<br />
- When torus interlocks clear call RC to ramp up magnet (~noon)<br />
- When solenoid interlocks clear call RC to ramp up magnet (~1 p.m.)<br />
- Give MCC notice of our schedule when solenoid is at half field (30 minutes until beam needed)<br />
- Request 5 nA to Faraday cup. Check beam positions and halo rates<br />
- Ramp up DC and BMT to voltage<br />
- Resume program<br />
<br />
'''Remaining Non-Production Runs''' (scheduled for day shift on Mar. 4)<br />
- DC HV study - 30 minutes duration - standard production trigger (Florian will coordinate)<br />
- Production run at 90 nA<br />
- DAQ configuration: PROD67_PIN, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Run duration: 90 minutes<br />
- Test with HTCC removed from trigger: (call Valery when ready)<br />
- DAQ configuration: PROD67, Trigger: rgk_noHTCC_noDC_v2.0_300MeV<br />
- Beam current: 75 nA<br />
- Run duration: 2 hrs <br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
'''Beam Studies Day'''<br />
- Beam goes off on Mar. 6 at 7 a.m.<br />
- Turn DC off and set BMT HV to safe mode; all other detectors remain on<br />
<br />
'''Beam Restore'''<br />
- Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode)<br />
- Tune beam to tagger yoke dump at 5 nA (contact Eugene for questions)<br />
- Take harp scans at 2C21A and 2C24A and compare to reference plots<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive) (contact Nathan for questions)<br />
- Call MCC to change HWP to out (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive)<br />
- Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
- Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
- Take harp scan at 2H01 and compare to reference plot<br />
- When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.<br />
- Turn all detectors off and put BMT HV in safe mode<br />
- Ramp torus and solenoid to zero field (contact Eugene to do this)<br />
- Call to put Hall B in Restricted Access<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7433Template:ShortTermSchedule-RGK2024-03-04T16:40:45Z<p>Carman: </p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 4 - Mar. 11, 2024''' ==<br />
<br />
'''Recovery from Magnet Fast Dump'''<br />
- When torus interlocks clear call RC to ramp up magnet (~noon)<br />
- When solenoid interlocks clear call RC to ramp up magnet (~1 p.m.)<br />
- Give MCC notice of our schedule when solenoid is at half field (30 minutes until beam needed)<br />
- Request 5 nA to Faraday cup. Check beam positions and halo rates<br />
- Ramp up DC and BMT to voltage<br />
- Resume program<br />
<br />
'''Remaining Non-Production Runs''' (scheduled for day shift on Mar. 4)<br />
- DC HV study - 30 minutes duration - standard production trigger (Florian will coordinate)<br />
- Test with HTCC removed from trigger: (call Valery when ready)<br />
- DAQ configuration: PROD67, Trigger: rgk_noHTCC_noDC_v2.0_300MeV<br />
- Beam current: 75 nA<br />
- Run duration: 2 hrs <br />
- Production run at 90 nA<br />
- DAQ configuration: PROD67_PIN, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Run duration: 90 minutes<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
'''Beam Studies Day'''<br />
- Beam goes off on Mar. 6 at 7 a.m.<br />
- Turn DC off and set BMT HV to safe mode; all other detectors remain on<br />
<br />
'''Beam Restore'''<br />
- Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode)<br />
- Tune beam to tagger yoke dump at 5 nA (contact Eugene for questions)<br />
- Take harp scans at 2C21A and 2C24A and compare to reference plots<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive) (contact Nathan for questions)<br />
- Call MCC to change HWP to out (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive)<br />
- Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
- Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
- Take harp scan at 2H01 and compare to reference plot<br />
- When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.<br />
- Turn all detectors off and put BMT HV in safe mode<br />
- Ramp torus and solenoid to zero field (contact Eugene to do this)<br />
- Call to put Hall B in Restricted Access<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7432Template:ShortTermSchedule-RGK2024-03-04T12:33:42Z<p>Carman: /* Run Plan: Mar. 3 - Mar. 11, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 4 - Mar. 11, 2024''' ==<br />
<br />
'''Recovery from Magnet Fast Dump'''<br />
- When torus interlocks clear call RC to ramp up magnet (~10 a.m.)<br />
- When solenoid interlocks clear call RC to ramp up magnet (~noon)<br />
- Give MCC notice of our schedule when solenoid is at half field (30 minutes until beam needed)<br />
- Request 5 nA to Faraday cup. Check beam positions and halo rates<br />
- Ramp up DC and BMT to voltage<br />
- Resume production running<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
'''Remaining Non-Production Runs''' (scheduled for day shift on Mar. 4)<br />
- DC HV study - 30 minutes duration - standard production trigger (Florian will coordinate)<br />
- Test with HTCC removed from trigger:<br />
- DAQ configuration: PROD67, Trigger: rgk_noHTCC_noDC_v2.0_300MeV<br />
- Beam current: 75 nA<br />
- Run duration: 2 hrs <br />
<br />
'''Beam Studies Day'''<br />
- Beam goes off on Mar. 6 at 7 a.m.<br />
- Turn DC off and set BMT HV to safe mode; all other detectors remain on<br />
<br />
'''Beam Restore'''<br />
- Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode)<br />
- Tune beam to tagger yoke dump at 5 nA (contact Eugene for questions)<br />
- Take harp scans at 2C21A and 2C24A and compare to reference plots<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive) (contact Nathan for questions)<br />
- Call MCC to change HWP to out (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive)<br />
- Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
- Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
- Take harp scan at 2H01 and compare to reference plot<br />
- When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.<br />
- Turn all detectors off and put BMT HV in safe mode<br />
- Ramp torus and solenoid to zero field (contact Eugene to do this)<br />
- Call to put Hall B in Restricted Access<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7431Template:ShortTermSchedule-RGK2024-03-03T13:36:31Z<p>Carman: /* Run Plan: Mar. 3 - Mar. 11, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 3 - Mar. 11, 2024''' ==<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
'''Remaining Non-Production Runs''' (scheduled for day shift on Mar. 4)<br />
- DC HV study - 30 minutes duration - standard production trigger (Florian will coordinate)<br />
- Test with HTCC removed from trigger:<br />
- DAQ configuration: PROD67, Trigger: rgk_noHTCC_noDC_v2.0_300MeV<br />
- Beam current: 75 nA<br />
- Run duration: 2 hrs <br />
<br />
'''Beam Studies Day'''<br />
- Beam goes off on Mar. 6 at 7 a.m.<br />
- Turn DC off and set BMT HV to safe mode; all other detectors remain on<br />
<br />
'''Beam Restore'''<br />
- Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode)<br />
- Tune beam to tagger yoke dump at 5 nA (contact Eugene for questions)<br />
- Take harp scans at 2C21A and 2C24A and compare to reference plots<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive) (contact Nathan for questions)<br />
- Call MCC to change HWP to out (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive)<br />
- Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
- Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
- Take harp scan at 2H01 and compare to reference plot<br />
- When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.<br />
- Turn all detectors off and put BMT HV in safe mode<br />
- Ramp torus and solenoid to zero field (contact Eugene to do this)<br />
- Call to put Hall B in Restricted Access<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7430Template:ShortTermSchedule-RGK2024-03-03T13:32:41Z<p>Carman: /* See tab GENERAL INFORMATION for */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 3 - Mar. 11, 2024''' ==<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
'''Remaining Non-Production Runs''' (scheduled for day shift on Mar. 4)<br />
- DC HV study - 30 minutes duration - standard production trigger (Florian will coordinate)<br />
- Test with HTCC removed from trigger:<br />
- DAQ configuration: PROD67, Trigger: rgk_noHTCC_noDC_v2.0_300MeV<br />
- Beam current: 75 nA<br />
- Run duration: 2 hrs <br />
<br />
'''Beam Studies Day'''<br />
- Beam goes off on Mar. 6 at 7 a.m.<br />
- Turn DC off and set BMT HV to safe mode; all other detectors remain on<br />
<br />
'''Beam Restore'''<br />
- Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode)<br />
- Tune beam to tagger yoke dump at 5 nA (contact Eugene for questions)<br />
- Take harp scans at 2C21A and 2C24A and compare to reference plots<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive) (contact Nathan for questions)<br />
- Call MCC to change HWP to out (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive)<br />
- Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
- Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
- Take harp scan at 2H01 and compare to reference plot<br />
- When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7429Template:ShortTermSchedule-RGK2024-03-03T13:24:25Z<p>Carman: /* Run Plan: Mar. 3 - Mar. 6, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 3 - Mar. 11, 2024''' == (RG-K run ends on Mar. 11 at 7 a.m.)<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
'''Remaining Non-Production Runs''' (scheduled for day shift on Mar. 4)<br />
- DC HV study - 30 minutes duration - standard production trigger (Florian will coordinate)<br />
- Test with HTCC removed from trigger:<br />
- DAQ configuration: PROD67, Trigger: rgk_noHTCC_noDC_v2.0_300MeV<br />
- Beam current: 75 nA<br />
- Run duration: 2 hrs <br />
<br />
'''Beam Studies Day'''<br />
- Beam goes off on Mar. 6 at 7 a.m.<br />
- Turn DC off and set BMT HV to safe mode; all other detectors remain on<br />
<br />
'''Beam Restore'''<br />
- Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode)<br />
- Tune beam to tagger yoke dump at 5 nA (contact Eugene for questions)<br />
- Take harp scans at 2C21A and 2C24A and compare to reference plots<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive) (contact Nathan for questions)<br />
- Call MCC to change HWP to out (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive)<br />
- Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
- Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
- Take harp scan at 2H01 and compare to reference plot<br />
- When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7428Template:ShortTermSchedule-RGK2024-03-03T13:16:29Z<p>Carman: /* Run Plan: Mar. 2 - Mar. 5, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 3 - Mar. 6, 2024''' ==<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
'''Remaining Non-Production Runs''' (scheduled for day shift on Mar. 4)<br />
- DC HV study - 30 minutes duration - standard production trigger (Florian will coordinate)<br />
- Test with HTCC removed from trigger:<br />
- DAQ configuration: PROD67, Trigger: rgk_noHTCC_noDC_v2.0_300MeV<br />
- Beam current: 75 nA<br />
- Run duration: 2 hrs <br />
<br />
'''Beam Studies Day'''<br />
- Beam goes off on Mar. 6 at 7 a.m.<br />
- Turn DC off and set BMT HV to safe mode; all other detectors remain on<br />
<br />
'''Beam Restore'''<br />
- Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode)<br />
- Tune beam to tagger yoke dump at 5 nA (contact Eugene for questions)<br />
- Take harp scans at 2C21A and 2C24A and compare to reference plots<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive) (contact Nathan for questions)<br />
- Call MCC to change HWP to out (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
- Take Moller runs at 20 nA with HWP in (Helmholtz polarity positive)<br />
- Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
- Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
- Take harp scan at 2H01 and compare to reference plot<br />
- When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7427Template:ShortTermSchedule-RGK2024-03-02T13:31:50Z<p>Carman: </p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 2 - Mar. 5, 2024''' ==<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
'''Remaining Non-Production Runs''' (scheduled for day shift on Mar. 4)<br />
- DC HV study - 30 minutes duration - standard production trigger (Florian will coordinate)<br />
- Test with HTCC removed from trigger:<br />
- DAQ configuration: PROD67, Trigger: rgk_noHTCC_noDC_v2.0_300MeV<br />
- Beam current: 75 nA<br />
- Run duration: 2 hrs <br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7426Template:ShortTermSchedule-RGK2024-03-02T04:15:02Z<p>Carman: /* Run Plan: Mar. 1 - Mar. 4, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 1 - Mar. 4, 2024''' ==<br />
<br />
'''Empty Target Running'''<br />
- Empty LH2 target<br />
- Complete beam blocker calibration<br />
- Install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. <br />
- Configuration: PROD67, Trigger: rgk_noDC_empty_v1.1_300MeV.trg<br />
- Take 3 hr runs until charge collection is 10 mC using https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.html<br />
<br />
'''Luminosity Scan'''<br />
- Turn beam off and remove beam blocker<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using trigger files given below) - check and reset the mon12 plots every 30 minutes to be sure there are no problems with the detector response<br />
- Run duration: 2 hrs @ 5 nA, 30 min @ 30 nA, 30 min @ 50 nA<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg (Note: There is no trigger file with 50na in the name.)<br />
- <font color="red">NOTE</font>: For each new beam current setting after the run has started, normalize the trigger rate alarms (CLAS12 trigger screen &rarr; Alarm settings - expert &rarr; Set all normalized rate limits)<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
- <font color="red">Note</font>: After returning to the production trigger, normalize the trigger rate alarms (as above)<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7425Template:ShortTermSchedule-RGK2024-03-02T03:13:29Z<p>Carman: /* Run Plan: Mar. 1 - Mar. 4, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 1 - Mar. 4, 2024''' ==<br />
<br />
'''Empty Target Running'''<br />
- Empty LH2 target<br />
- Complete beam blocker calibration<br />
- Install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. <br />
- Configuration: PROD67, Trigger: rgk_noDC_empty_v1.1_300MeV.trg<br />
- Take 3 hr runs until charge collection is 10 mC using https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.html<br />
<br />
'''Luminosity Scan'''<br />
- Turn beam off and remove beam blocker<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using trigger files given below) - check and reset the mon12 plots every 30 minutes to be sure there are no problems with the detector response<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg (Note: There is no trigger file with 50na in the name.)<br />
- <font color="red">NOTE</font>: For each new beam current setting after the run has started, normalize the trigger rate alarms (CLAS12 trigger screen &rarr; Alarm settings - expert &rarr; Set all normalized rate limits)<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
- <font color="red">Note</font>: After returning to the production trigger, normalize the trigger rate alarms (as above)<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7424Template:ShortTermSchedule-RGK2024-03-02T03:10:58Z<p>Carman: </p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 1 - Mar. 4, 2024''' ==<br />
<br />
'''Empty Target Running'''<br />
- Empty LH2 target<br />
- Complete beam blocker calibration<br />
- Install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. <br />
- Configuration: PROD67, Trigger: rgk_noDC_empty_v1.1_300MeV.trg<br />
- Take 3 hr runs until charge collection is 10 mC using https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.html<br />
<br />
'''Luminosity Scan'''<br />
- Turn beam off and remove beam blocker<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using trigger files given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg (Note: There is no trigger file with 50na in the name.)<br />
- <font color="red">NOTE</font>: For each new beam current setting after the run has started, normalize the trigger rate alarms (CLAS12 trigger screen &rarr; Alarm settings - expert &rarr; Set all normalized rate limits)<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
- <font color="red">Note</font>: After returning to the production trigger, normalize the trigger rate alarms (as above)<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7423Template:ShortTermSchedule-RGK2024-03-01T12:28:00Z<p>Carman: /* Run Plan: Feb. 29 - Mar. 4, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Mar. 1 - Mar. 4, 2024''' ==<br />
<br />
'''Empty Target Running'''<br />
- Empty LH2 target<br />
- Complete beam blocker calibration<br />
- Install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. <br />
- Configuration: PROD67, Trigger: rgk_noDC_empty_v1.1_300MeV.trg<br />
- Take 3 hr runs until charge collection is 10 mC using https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.html<br />
<br />
'''Luminosity Scan'''<br />
- Turn beam off and remove beam blocker<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using trigger files given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg (Note: There is no trigger file with 50na in the name.)<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7422Template:ShortTermSchedule-RGK2024-03-01T01:11:05Z<p>Carman: /* Run Plan: Feb. 29 - Mar. 4, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Feb. 29 - Mar. 4, 2024''' ==<br />
<br />
'''Empty Target Running''' (Feb. 29 - starting at 11:30 a.m.)<br />
- Empty LH2 target<br />
- Complete beam blocker calibration<br />
- Install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. <br />
- Configuration: PROD67, Trigger: rgk_noDC_empty_v1.1_300MeV.trg<br />
- Take 3 hr runs until charge collection is 10 mC using https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.html<br />
<br />
'''Luminosity Scan'''<br />
- Turn beam off and remove beam blocker<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using trigger files given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg (Note: There is no trigger file with 50na in the name.)<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7421Template:ShortTermSchedule-RGK2024-03-01T01:10:32Z<p>Carman: /* Run Plan: Feb. 29 - Mar. 4, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Feb. 29 - Mar. 4, 2024''' ==<br />
<br />
'''Empty Target Running''' (Feb. 29 - starting at 11:30 p.m.)<br />
- Empty LH2 target<br />
- Complete beam blocker calibration<br />
- Install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. <br />
- Configuration: PROD67, Trigger: rgk_noDC_empty_v1.1_300MeV.trg<br />
- Take 3 hr runs until charge collection is 10 mC using https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.html<br />
<br />
'''Luminosity Scan'''<br />
- Turn beam off and remove beam blocker<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using trigger files given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg (Note: There is no trigger file with 50na in the name.)<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7420Template:ShortTermSchedule-RGK2024-02-29T21:57:49Z<p>Carman: /* Run Plan: Feb. 29 - Mar. 4, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Feb. 29 - Mar. 4, 2024''' ==<br />
<br />
'''Empty Target Running''' (Feb. 29 - starting at 11:30 p.m.)<br />
- Empty LH2 target<br />
- Complete beam blocker calibration<br />
- Install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. <br />
- Configuration: PROD67, Trigger: rgk_noDC_empty_v1.1_300MeV.trg<br />
- Take 3 hr runs until charge collection is 10 mC using https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.html<br />
<br />
'''Luminosity Scan'''<br />
- Turn beam off and remove beam blocker<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using trigger files given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg (Note: There is no trigger file with 50na in the name.)<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7417Template:ShortTermSchedule-RGK2024-02-29T17:53:55Z<p>Carman: /* Run Plan: Feb. 29 - Mar. 4, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Feb. 29 - Mar. 4, 2024''' ==<br />
<br />
'''Empty Target Running''' (Feb. 29 - starting at 11:30 p.m.)<br />
- Empty LH2 target<br />
- Complete beam blocker calibration<br />
- Install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. <br />
- Configuration: PROD67, Trigger: rgk_noDC_empty_v1.1_300MeV.trg<br />
- Take 3 hr runs until charge collection is 10 mC using https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.html<br />
<br />
'''Luminosity Scan'''<br />
- Turn beam off and remove beam blocker<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using trigger files given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg (Note: There is no trigger file with the 50na in the name.)<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7416Template:ShortTermSchedule-RGK2024-02-29T17:50:45Z<p>Carman: /* Run Plan: Feb. 29 - Mar. 4, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Feb. 29 - Mar. 4, 2024''' ==<br />
<br />
'''Empty Target Running''' (Feb.29: 11:30 a.m. - 1:30 p.m.)<br />
- Empty LH2 target<br />
- Complete beam blocker calibration<br />
- Install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. <br />
- Configuration: PROD67, Trigger: rgk_noDC_empty_v1.1_300MeV.trg<br />
- Take 3 hr runs until charge collection is 10 mC<br />
<br />
'''Luminosity Scan'''<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using triggers given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7415Template:ShortTermSchedule-RGK2024-02-29T17:42:22Z<p>Carman: /* Run Plan: Feb. 29 - Mar. 4, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Feb. 29 - Mar. 4, 2024''' ==<br />
<br />
'''Empty Target Running''' (Feb.29 - 11:30 a.m. - 1:30 p.m.)<br />
- Empty LH2 target<br />
- Complete beam blocker calibration<br />
- Install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. <br />
- Configuration: PROD67, Trigger: rgk_noDC_empty_v1.1_300MeV.trg<br />
- Take 3 hr runs until charge collection is 10 mC<br />
<br />
'''Luminosity Scan'''<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using triggers given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7414Template:ShortTermSchedule-RGK2024-02-29T16:54:14Z<p>Carman: </p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Feb. 29 - Mar. 4, 2024''' ==<br />
<br />
'''Empty Target Running''' (Feb.29 - 11:30 a.m. - 1:30 p.m.)<br />
- Empty LH2 target<br />
- Complete beam blocker calibration (Rafo will lead effort). Note: Beam blocker must be installed for running more than 5 minutes above 100 nA<br />
- When beam blocker calibration is finished, install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. <br />
- Configuration: PROD67, Trigger: rgk_noDC_empty_v1.1_300MeV.trg<br />
- Take 3 hr runs until charge collection is 10 mC (10-12 hrs of good beam)<br />
<br />
'''Luminosity Scan'''<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using triggers given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7413Template:ShortTermSchedule-RGK2024-02-29T12:33:53Z<p>Carman: /* Run Plan: Feb. 29 - Mar. 4, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Feb. 29 - Mar. 4, 2024''' ==<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
- Take production data until Rafo is available for beam blocker calibration (by noon)<br />
<br />
'''Empty Target Running'''<br />
- Turn beam off and empty LH2 target<br />
- Complete beam blocker calibration (Rafo will lead effort, duration 2 hrs). Note: Beam blocker must be installed for running more than 5 minutes above 100 nA<br />
- When beam blocker calibration is finished, install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. <br />
- Configuration: PROD67, Trigger: rgk_noDC_empty_v1.1_300MeV.trg<br />
- Take 3 hr runs until charge collection is 10 mC (10-12 hrs of good beam)<br />
<br />
'''Luminosity Scan'''<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using triggers given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7412Template:ShortTermSchedule-RGK2024-02-29T12:28:24Z<p>Carman: </p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Feb. 29 - Mar. 4, 2024''' ==<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
- Take production data until Rafo is available for beam blocker calibration (by noon)<br />
<br />
'''Empty Target Running'''<br />
- Turn beam off and empty LH2 target<br />
- Complete beam blocker calibration (Rafo will lead effort, duration 2 hrs). Note: Beam blocker must be installed for running more than 5 minutes above 100 nA<br />
- When beam blocker calibration is finished, install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. Take 3 hr runs until charge collection is 10 mC (10-12 hrs of good beam)<br />
<br />
'''Luminosity Scan'''<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using triggers given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7411Template:ShortTermSchedule-RGK2024-02-29T00:12:15Z<p>Carman: /* Run Plan: Feb. 28 - Mar. 4, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Feb. 28 - Mar. 4, 2024''' ==<br />
<br />
'''Beam Restore'''<br />
1) About 90 minutes before beam is ready for delivery: Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode))<br />
2) Follow instructions to tune beam to tagger dump yoke (contact Eugene for questions); Compare 2C21A and 2C24A harp scans to reference<br />
3) Take two M&oslash;ller runs at 20 nA with HWP out (Helmholtz polarity negative and positive) (contact Nathan for questions)<br />
4) Call MCC to change HWP to in (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
5) Take two M&oslash;ller runs at 20 nA with HWP in (Helmholtz polarity negative and positive)<br />
6) Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
7) Follow instructions to tune beam to the Faraday cup (contact Eugene for questions); Compare 2H01 harp scan to reference<br />
8) When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
9) Increase beam up to 75 nA (checking halo rates and beam positions at 25 nA and 50 nA)<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
- Take production data until Rafo is available for beam blocker calibration (by noon)<br />
<br />
'''Empty Target Running'''<br />
- Turn beam off and empty LH2 target<br />
- Complete beam blocker calibration (Rafo will lead effort, duration 2 hrs). Note: Beam blocker must be installed for running more than 5 minutes above 100 nA<br />
- When beam blocker calibration is finished, install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. Take 3 hr runs until charge collection is 10 mC (10-12 hrs of good beam)<br />
<br />
'''Luminosity Scan'''<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using triggers given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7410Template:ShortTermSchedule-RGK2024-02-28T23:08:25Z<p>Carman: /* Run Plan: Feb. 28 - Mar. 4, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Feb. 28 - Mar. 4, 2024''' ==<br />
<br />
'''Beam Restore'''<br />
1) About 90 minutes before beam is ready for delivery: Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode))<br />
2) Follow instructions to tune beam to tagger dump yoke (contact Eugene for questions); Compare 2C21A and 2C24A harp scans to reference<br />
3) Take two M&oslash;ller runs at 20 nA with HWP out (Helmholtz polarity negative and positive) (contact Nathan for questions)<br />
4) Call MCC to change HWP to in (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
5) Take two M&oslash;ller runs at 20 nA with HWP in (Helmholtz polarity negative and positive)<br />
6) Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
7) Follow instructions to tune beam to the Faraday cup (contact Eugene for questions); Compare 2H01 harp scan to reference<br />
8) When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
9) Increase beam up to 75 nA (checking halo rates and beam positions at 25 nA and 50 nA)<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
- Take production data until Rafo is available for beam blocker calibration (~8 a.m.)<br />
<br />
'''Empty Target Running'''<br />
- Turn beam off and empty LH2 target<br />
- Complete beam blocker calibration (Rafo will lead effort, duration 2 hrs). Note: Beam blocker must be installed for running more than 5 minutes above 100 nA<br />
- When beam blocker calibration is finished, install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. Take 3 hr runs until charge collection is 10 mC (10-12 hrs of good beam)<br />
<br />
'''Luminosity Scan'''<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using triggers given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7409Template:ShortTermSchedule-RGK2024-02-28T19:22:07Z<p>Carman: </p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Feb. 28 - Mar. 4, 2024''' ==<br />
<br />
'''Maintenance Day/Beam Studies (Feb. 28 7 a.m. - 10:30 p.m.)'''<br />
- <strike>When beam goes off, put BMT HV in safe mode and turn DC HV off (other detectors remain on)</strike><br />
- <strike>Call Eugene to ramp down the torus magnet</strike><br />
- Work planned during access:<br />
- Survey FMT (RadCon)<br />
- Survey downstream alcove for Rafo (escorted access with RadCon)<br />
- Adjust FC offset (Rafo)<br />
- <strike>Check transceiver on Pie Tower (Sergey)</strike><br />
- <strike>Work on FMT (Yuri, Rafo)</strike><br />
- <strike>Investigate torus VCL flange area with ice-build up (Probir)</strike><br />
- <strike>SAF111 walkthrough @ 11 a.m. (Eugene + folks)</strike><br />
- <strike>Hall B Photographs (Raffaella + Aileen)</strike><br />
- <strike>Address communication issue with HVFTOF4 (Nathan)</strike><br />
<br />
'''Beam Restore'''<br />
1) When work is completed in the hall, turn out the overhead lights and call MCC to move the hall to power permit.<br />
2) Contact Eugene to ramp the torus up to full field.<br />
3) About 90 minutes before beam is ready for delivery: Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode))<br />
4) Follow instructions to tune beam to tagger dump yoke (contact Eugene for questions); Compare 2C21A and 2C24A harp scans to reference<br />
5) Take two M&oslash;ller runs at 20 nA with HWP out (Helmholtz polarity negative and positive) (contact Nathan for questions)<br />
6) Call MCC to change HWP to in (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
7) Take two M&oslash;ller runs at 20 nA with HWP in (Helmholtz polarity negative and positive)<br />
8) Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
9) Follow instructions to tune beam to the Faraday cup (contact Eugene for questions); Compare 2H01 harp scan to reference<br />
10) When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
11) Increase beam up to 75 nA (checking halo rates and beam positions at 25 nA and 50 nA)<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
- Take production data until Rafo is available for beam blocker calibration (~8 a.m.)<br />
<br />
'''Empty Target Running'''<br />
- Turn beam off and empty LH2 target<br />
- Complete beam blocker calibration (Rafo will lead effort, duration 2 hrs). Note: Beam blocker must be installed for running more than 5 minutes above 100 nA<br />
- When beam blocker calibration is finished, install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. Take 3 hr runs until charge collection is 10 mC (10-12 hrs of good beam)<br />
<br />
'''Luminosity Scan'''<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using triggers given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7408Template:ShortTermSchedule-RGK2024-02-28T19:18:26Z<p>Carman: /* Run Plan: Feb. 28 - Mar. 4, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Feb. 28 - Mar. 4, 2024''' ==<br />
<br />
'''Maintenance Day/Beam Studies (Feb. 28 7 a.m. - 10:30 p.m.)'''<br />
- <strike>When beam goes off, put BMT HV in safe mode and turn DC HV off (other detectors remain on)</strike><br />
- <strike>Call Eugene to ramp down the torus magnet</strike><br />
- Work planned during access:<br />
- Survey FMT (RadCon)<br />
- Survey downstream alcove for Rafo (escorted access with RadCon)<br />
- <strike>Check transceiver on Pie Tower (Sergey)</strike><br />
- Adjust FC offset (Rafo)<br />
- <strike>Work on FMT (Yuri, Rafo)</strike><br />
- <strike>Investigate torus VCL flange area with ice-build up (Probir)</strike><br />
- <strike>SAF111 walkthrough @ 11 a.m. (Eugene + folks)</strike><br />
- <strike>Hall B Photographs (Raffaella + Aileen)</strike><br />
- <strike>Address communication issue with HVFTOF4 (Nathan)</strike><br />
<br />
'''Beam Restore'''<br />
1) When work is completed in the hall, turn out the overhead lights and call MCC to move the hall to power permit.<br />
2) Contact Eugene to ramp the torus up to full field.<br />
3) About 90 minutes before beam is ready for delivery: Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode))<br />
4) Follow instructions to tune beam to tagger dump yoke (contact Eugene for questions); Compare 2C21A and 2C24A harp scans to reference<br />
5) Take two M&oslash;ller runs at 20 nA with HWP out (Helmholtz polarity negative and positive) (contact Nathan for questions)<br />
6) Call MCC to change HWP to in (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
7) Take two M&oslash;ller runs at 20 nA with HWP in (Helmholtz polarity negative and positive)<br />
8) Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
9) Follow instructions to tune beam to the Faraday cup (contact Eugene for questions); Compare 2H01 harp scan to reference<br />
10) When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
11) Increase beam up to 75 nA (checking halo rates and beam positions at 25 nA and 50 nA)<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
- Take production data until Rafo is available for beam blocker calibration (~8 a.m.)<br />
<br />
'''Empty Target Running'''<br />
- Turn beam off and empty LH2 target<br />
- Complete beam blocker calibration (Rafo will lead effort, duration 2 hrs). Note: Beam blocker must be installed for running more than 5 minutes above 100 nA<br />
- When beam blocker calibration is finished, install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. Take 3 hr runs until charge collection is 10 mC (10-12 hrs of good beam)<br />
<br />
'''Luminosity Scan'''<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using triggers given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7407Template:ShortTermSchedule-RGK2024-02-28T17:54:06Z<p>Carman: /* Run Plan: Feb. 28 - Mar. 4, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Feb. 28 - Mar. 4, 2024''' ==<br />
<br />
'''Maintenance Day/Beam Studies (Feb. 28 7 a.m. - 10:30 p.m.)'''<br />
- <strike>When beam goes off, put BMT HV in safe mode and turn DC HV off (other detectors remain on)</strike><br />
- <strike>Call Eugene to ramp down the torus magnet</strike><br />
- Work planned during access:<br />
- Survey FMT (RadCon)<br />
- Survey downstream alcove for Rafo (escorted access with RadCon)<br />
- Check transceiver on Pie Tower (Sergey)<br />
- Adjust FC offset (Rafo)<br />
- Work on FMT (Yuri, Rafo)<br />
- Investigate torus VCL flange area with ice-build up (Probir)<br />
- <strike>SAF111 walkthrough @ 11 a.m. (Eugene + folks)</strike><br />
- <strike>Hall B Photographs (Raffaella + Aileen)</strike><br />
- Address communication issue with HVFTOF4 (Nathan)<br />
<br />
'''Beam Restore'''<br />
1) When work is completed in the hall, turn out the overhead lights and call MCC to move the hall to power permit.<br />
2) Contact Eugene to ramp the torus up to full field.<br />
3) About 90 minutes before beam is ready for delivery: Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode))<br />
4) Follow instructions to tune beam to tagger dump yoke (contact Eugene for questions); Compare 2C21A and 2C24A harp scans to reference<br />
5) Take two M&oslash;ller runs at 20 nA with HWP out (Helmholtz polarity negative and positive) (contact Nathan for questions)<br />
6) Call MCC to change HWP to in (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
7) Take two M&oslash;ller runs at 20 nA with HWP in (Helmholtz polarity negative and positive)<br />
8) Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
9) Follow instructions to tune beam to the Faraday cup (contact Eugene for questions); Compare 2H01 harp scan to reference<br />
10) When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
11) Increase beam up to 75 nA (checking halo rates and beam positions at 25 nA and 50 nA)<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
- Take production data until Rafo is available for beam blocker calibration (~8 a.m.)<br />
<br />
'''Empty Target Running'''<br />
- Turn beam off and empty LH2 target<br />
- Complete beam blocker calibration (Rafo will lead effort, duration 2 hrs). Note: Beam blocker must be installed for running more than 5 minutes above 100 nA<br />
- When beam blocker calibration is finished, install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. Take 3 hr runs until charge collection is 10 mC (10-12 hrs of good beam)<br />
<br />
'''Luminosity Scan'''<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using triggers given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7406Template:ShortTermSchedule-RGK2024-02-28T17:51:54Z<p>Carman: /* Run Plan: Feb. 28 - Mar. 4, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Feb. 28 - Mar. 4, 2024''' ==<br />
<br />
'''Maintenance Day/Beam Studies (Feb. 28 7 a.m. - 10:30 p.m.)'''<br />
- <strike>When beam goes off, put BMT HV in safe mode and turn DC HV off (other detectors remain on)</strike><br />
- <strike>Call Eugene to ramp down the torus magnet</strike><br />
- Work planned during access:<br />
- Survey FMT (RadCon)<br />
- Survey downstream alcove for Rafo (escorted access with RadCon)<br />
- Check transceiver on Pie Tower (Sergey)<br />
- Adjust FC offset (Rafo)<br />
- Work on FMT (Yuri, Rafo)<br />
- Investigate torus VCL flange area with ice-build up (Probir)<br />
- <strike>SAF111 walkthrough @ 11 a.m. (Eugene + folks)</strike><br />
- <strike>Hall B Photographs (Raffaella + Aileen)</strike><br />
- Address communication issue with HVFTOF4 (Nathan)<br />
<br />
'''Beam Restore'''<br />
1) When work is completed in the hall, turn out the overhead lights and call MCC to move the hall to power permit.<br />
2) Contact Eugene to ramp the torus up to full field.<br />
3) About 90 minutes before beam is ready for delivery: Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode))<br />
4) Follow instructions to tune beam to tagger dump yoke (contact Eugene for questions)<br />
5) Take two M&oslash;ller runs at 20 nA with HWP out (Helmholtz polarity negative and positive) (contact Nathan for questions)<br />
6) Call MCC to change HWP to in (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
7) Take two M&oslash;ller runs at 20 nA with HWP in (Helmholtz polarity negative and positive)<br />
8) Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
9) Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
10) Take harp scan at 2H01 and compare to reference plot<br />
11) When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
12) Increase beam up to 75 nA (checking halo rates and beam positions at 25 nA and 50 nA)<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
- Take production data until Rafo is available for beam blocker calibration (~8 a.m.)<br />
<br />
'''Empty Target Running'''<br />
- Turn beam off and empty LH2 target<br />
- Complete beam blocker calibration (Rafo will lead effort, duration 2 hrs). Note: Beam blocker must be installed for running more than 5 minutes above 100 nA<br />
- When beam blocker calibration is finished, install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. Take 3 hr runs until charge collection is 10 mC (10-12 hrs of good beam)<br />
<br />
'''Luminosity Scan'''<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using triggers given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7405Template:ShortTermSchedule-RGK2024-02-28T17:51:18Z<p>Carman: /* Run Plan: Feb. 28 - Mar. 4, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Feb. 28 - Mar. 4, 2024''' ==<br />
<br />
'''Maintenance Day/Beam Studies (Feb. 28 7 a.m. - 10:30 p.m.)'''<br />
- <strike>When beam goes off, put BMT HV in safe mode and turn DC HV off (other detectors remain on)</strike><br />
- <strike>Call Eugene to ramp down the torus magnet</strike><br />
- Work planned during access:<br />
- Survey FMT (RadCon)<br />
- Survey downstream alcove for Rafo (escorted access with RadCon)<br />
- Check transceiver on Pie Tower (Sergey)<br />
- Adjust FC offset (Rafo)<br />
- Work on FMT (Yuri, Rafo)<br />
- Investigate torus VCL flange area with ice-build up (Probir)<br />
- <strike>SAF111 walkthrough @ 11 a.m. (Eugene + folks)</strike><br />
- <strike>Hall B Photographs (Raffaella + Aileen)</strike><br />
- Address communication issue with HVFTOF4 (Nathan)<br />
<br />
'''Beam Restore'''<br />
1) When work is completed in the hall, turn out the overhead lights and call MCC to move the hall to power permit.<br />
2) Contact Eugene to ramp the torus up to full field.<br />
3) Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode))<br />
4) Follow instructions to tune beam to tagger dump yoke (contact Eugene for questions)<br />
5) Take two M&oslash;ller runs at 20 nA with HWP out (Helmholtz polarity negative and positive) (contact Nathan for questions)<br />
6) Call MCC to change HWP to in (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
7) Take two M&oslash;ller runs at 20 nA with HWP in (Helmholtz polarity negative and positive)<br />
8) Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
9) Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
10) Take harp scan at 2H01 and compare to reference plot<br />
11) When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
12) Increase beam up to 75 nA (checking halo rates and beam positions at 25 nA and 50 nA)<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
- Take production data until Rafo is available for beam blocker calibration (~8 a.m.)<br />
<br />
'''Empty Target Running'''<br />
- Turn beam off and empty LH2 target<br />
- Complete beam blocker calibration (Rafo will lead effort, duration 2 hrs). Note: Beam blocker must be installed for running more than 5 minutes above 100 nA<br />
- When beam blocker calibration is finished, install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. Take 3 hr runs until charge collection is 10 mC (10-12 hrs of good beam)<br />
<br />
'''Luminosity Scan'''<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using triggers given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7404Template:ShortTermSchedule-RGK2024-02-28T15:18:47Z<p>Carman: /* Run Plan: Feb. 28 - Mar. 4, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Feb. 28 - Mar. 4, 2024''' ==<br />
<br />
'''Maintenance Day/Beam Studies (Feb. 28 7 a.m. - 10:30 p.m.)'''<br />
- <strike>When beam goes off, put BMT HV in safe mode and turn DC HV off (other detectors remain on)</strike><br />
- <strike>Call Eugene to ramp down the torus magnet</strike><br />
- Work planned during access:<br />
- Survey FMT (RadCon)<br />
- Survey downstream alcove for Rafo (escorted access with RadCon)<br />
- Check transceiver on Pie Tower (Sergey)<br />
- Adjust FC offset (Rafo)<br />
- Work on FMT (Yuri, Rafo)<br />
- Investigate torus VCL flange area with ice-build up (Probir)<br />
- SAF111 walkthrough @ 11 a.m. (Eugene + folks)<br />
- Hall B Photographs (Raffaella + Aileen)<br />
- Address communication issue with HVFTOF4 (Nathan)<br />
<br />
'''Beam Restore'''<br />
1) When work is completed in the hall, turn out the overhead lights and call MCC to move the hall to power permit.<br />
2) Contact Eugene to ramp the torus up to full field.<br />
3) Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode))<br />
4) Follow instructions to tune beam to tagger dump yoke (contact Eugene for questions)<br />
5) Take two M&oslash;ller runs at 20 nA with HWP out (Helmholtz polarity negative and positive) (contact Nathan for questions)<br />
6) Call MCC to change HWP to in (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
7) Take two M&oslash;ller runs at 20 nA with HWP in (Helmholtz polarity negative and positive)<br />
8) Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
9) Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
10) Take harp scan at 2H01 and compare to reference plot<br />
11) When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
12) Increase beam up to 75 nA (checking halo rates and beam positions at 25 nA and 50 nA)<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
- Take production data until Rafo is available for beam blocker calibration (~8 a.m.)<br />
<br />
'''Empty Target Running'''<br />
- Turn beam off and empty LH2 target<br />
- Complete beam blocker calibration (Rafo will lead effort, duration 2 hrs). Note: Beam blocker must be installed for running more than 5 minutes above 100 nA<br />
- When beam blocker calibration is finished, install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. Take 3 hr runs until charge collection is 10 mC (10-12 hrs of good beam)<br />
<br />
'''Luminosity Scan'''<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using triggers given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7403Template:ShortTermSchedule-RGK2024-02-28T14:55:31Z<p>Carman: </p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Feb. 28 - Mar. 4, 2024''' ==<br />
<br />
'''Production Running''' (run until beam off for maintenance day/beam studies Feb. 28 at 7 a.m.)<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 5 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
'''Maintenance Day/Beam Studies (Feb. 28 7 a.m. - 10:30 p.m.)'''<br />
- When beam goes off, put BMT HV in safe mode and turn DC HV off (other detectors remain on)<br />
- Call Eugene to ramp down the torus magnet<br />
- Work planned during access:<br />
- Survey FMT (RadCon)<br />
- Survey downstream alcove for Rafo (escorted access with RadCon)<br />
- Check transceiver on Pie Tower (Sergey)<br />
- Adjust FC offset (Rafo)<br />
- Work on FMT (Yuri, Rafo)<br />
- Investigate torus VCL flange area with ice-build up (Probir)<br />
- SAF111 walkthrough @ 11 a.m. (Eugene + folks)<br />
- Hall B Photographs (Raffaella + Aileen)<br />
- Address communication issue with HVFTOF4 (Nathan)<br />
<br />
'''Beam Restore'''<br />
1) When work is completed in the hall, turn out the overhead lights and call MCC to move the hall to power permit.<br />
2) Contact Eugene to ramp the torus up to full field.<br />
3) Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode))<br />
4) Follow instructions to tune beam to tagger dump yoke (contact Eugene for questions)<br />
5) Take two M&oslash;ller runs at 20 nA with HWP out (Helmholtz polarity negative and positive) (contact Nathan for questions)<br />
6) Call MCC to change HWP to in (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
7) Take two M&oslash;ller runs at 20 nA with HWP in (Helmholtz polarity negative and positive)<br />
8) Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
9) Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
10) Take harp scan at 2H01 and compare to reference plot<br />
11) When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
12) Increase beam up to 75 nA (checking halo rates and beam positions at 25 nA and 50 nA)<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
- Take production data until Rafo is available for beam blocker calibration (~8 a.m.)<br />
<br />
'''Empty Target Running'''<br />
- Turn beam off and empty LH2 target<br />
- Complete beam blocker calibration (Rafo will lead effort, duration 2 hrs). Note: Beam blocker must be installed for running more than 5 minutes above 100 nA<br />
- When beam blocker calibration is finished, install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. Take 3 hr runs until charge collection is 10 mC (10-12 hrs of good beam)<br />
<br />
'''Luminosity Scan'''<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using triggers given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7402Template:ShortTermSchedule-RGK2024-02-28T12:25:07Z<p>Carman: /* Run Plan: Feb. 28 - Mar. 4, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Feb. 28 - Mar. 4, 2024''' ==<br />
<br />
'''Production Running''' (run until beam off for maintenance day/beam studies Feb. 28 at 7 a.m.)<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 5 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
'''Maintenance Day/Beam Studies (Feb. 28 7 a.m. - 10:30 p.m.)'''<br />
- When beam goes off, put BMT HV in safe mode and turn DC HV off (other detectors remain on)<br />
- Call Eugene to ramp down the torus magnet<br />
- Work planned during access:<br />
- Survey FMT (RadCon)<br />
- Survey downstream alcove for Rafo (escorted access with RadCon)<br />
- Check transceiver on Pie Tower (Sergey)<br />
- Adjust FC offset (Rafo)<br />
- Work on FMT (Yuri, Rafo)<br />
- Investigate torus VCL flange area with ice-build up (Probir)<br />
- SAF111 walkthrough @ 11 a.m. (Eugene + folks)<br />
- Hall B Photograghs (Raffaella + Aileen)<br />
- Address communication issue with HVFTOF4 (Nathan)<br />
<br />
'''Beam Restore'''<br />
1) When work is completed in the hall, turn out the overhead lights and call MCC to move the hall to power permit.<br />
2) Contact Eugene to ramp the torus up to full field.<br />
3) Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode))<br />
4) Follow instructions to tune beam to tagger dump yoke (contact Eugene for questions)<br />
5) Take two M&oslash;ller runs at 20 nA with HWP out (Helmholtz polarity negative and positive) (contact Nathan for questions)<br />
6) Call MCC to change HWP to in (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
7) Take two M&oslash;ller runs at 20 nA with HWP in (Helmholtz polarity negative and positive)<br />
8) Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
9) Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
10) Take harp scan at 2H01 and compare to reference plot<br />
11) When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
12) Increase beam up to 75 nA (checking halo rates and beam positions at 25 nA and 50 nA)<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
- Take production data until Rafo is available for beam blocker calibration (~8 a.m.)<br />
<br />
'''Empty Target Running'''<br />
- Turn beam off and empty LH2 target<br />
- Complete beam blocker calibration (Rafo will lead effort, duration 2 hrs). Note: Beam blocker must be installed for running more than 5 minutes above 100 nA<br />
- When beam blocker calibration is finished, install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. Take 3 hr runs until charge collection is 10 mC (10-12 hrs of good beam)<br />
<br />
'''Luminosity Scan'''<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using triggers given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carmanhttps://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&diff=7401Template:ShortTermSchedule-RGK2024-02-28T12:24:05Z<p>Carman: /* Run Plan: Feb. 27 - Mar. 4, 2024 */</p>
<hr />
<div>'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span><br />
<br />
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span><br />
<br />
== '''Important Notes''' ==<br />
<br />
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span><br />
<br />
'''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief and RC.<br />
<br />
'''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 "<font color=red>EXIT</font>" 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.<br />
<br />
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.<br />
<br />
'''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!<br />
<br />
'''Note to Shift Takers''':<br />
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K Run Info]" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.<br />
* Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes<br />
* Arrive at least 10 minutes early for '''shift change'''<br />
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.<br />
<br />
* Refresh the run wiki page/tabs; look over it/them every shift<br />
* Follow the '''Shift Expert/Worker tab's instructions'''<br />
* '''Do not spend more than 15-20 min trying to fix a problem'''. In case of any issue, contact the On-call Experts or the RC.<br />
<br />
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for === <br />
* '''Recent Changes'''<br />
* '''Current Issues'''<br />
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)<br />
<br />
== '''Run Plan: Feb. 28 - Mar. 4, 2024''' ==<br />
<br />
'''Production Running''' (run until beam off for maintenance day/beam studies Feb. 28 at 7 a.m.)<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 5 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
'''Maintenance Day/Beam Studies (Feb. 28 7 a.m. - 10:30 p.m.)'''<br />
- When beam goes off, put BMT HV in safe mode and turn DC HV off (other detectors remain on)<br />
- Call Eugene to ramp down the torus magnet<br />
- Work planned during access:<br />
- Survey FMT (RadCon)<br />
- Survey downstream alcove for Rafo (escorted access with RadCon)<br />
- Check transceiver on Pie Tower (Sergey)<br />
- Adjust FC offset (Rafo)<br />
- Work on FMT (Yuri, Rafo)<br />
- Investigate torus VCL flange area with ice-build up (Probir)<br />
- SAF111 walkthrough @ 11 a.m. (Eugene + folks)<br />
- Hall B Photograghs (Raffaella + Aileen)<br />
- Address communication issue with HVFTOF4 (Nathan)<br />
<br />
'''Beam Restore'''<br />
1) When work is completed in the hall, turn out the overhead lights and call MCC to move the hall to power permit.<br />
2) Contact Eugene to ramp the torus up to full field.<br />
3) Energize tagger magnet and prepare for beam delivery to tagger yoke dump (blank collimator, beam type photon, CLAS12 detectors off (BMT HV in safe mode))<br />
4) Follow instructions to tune beam to tagger dump yoke (contact Eugene for questions)<br />
5) Take two Moller runs at 20 nA with HWP out (Helmholtz polarity negative and positive) (contact Nathan for questions)<br />
6) Call MCC to change HWP to in (coordinate with Hall C beforehand!); after transition contact Hall C to run flipper script; check charge asymmetry (contact Eugene if it is outside tolerance)<br />
7) Take two Moller runs at 20 nA with HWP in (Helmholtz polarity negative and positive)<br />
8) Turn beam off and degauss tagger magnet (20 mm collimator, beam type electron)<br />
9) Tune 5 nA beam to Faraday cup (check beam positions) (contact Eugene for questions)<br />
10) Take harp scan at 2H01 and compare to reference plot<br />
11) When the tune is acceptable (halo monitors and beam positions at 2C21A, 2C24A, 2H01), turn all CLAS12 detectors on<br />
12) Increase beam up to 75 nA (checking halo rates and beam positions at 25 nA and 50 nA)<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
- Take production data until Rafo is available for beam blocker calibration (~8 a.m.)<br />
<br />
'''Empty Target Running'''<br />
- Turn beam off and empty LH2 target<br />
- Complete beam blocker calibration (Rafo will lead effort, duration 2 hrs). Note: Beam blocker must be installed for running more than 5 minutes above 100 nA<br />
- When beam blocker calibration is finished, install beam blocker. Request 200 nA to the FC and begin DAQ for empty target running. Take 3 hr runs until charge collection is 10 mC (10-12 hrs of good beam)<br />
<br />
'''Luminosity Scan'''<br />
- Fill target (duration 30 min)<br />
- Take production data at beam currents of 5 nA, 30 nA, 50 nA (using triggers given below)<br />
- Run duration: 10M triggers for each beam current<br />
- 5 nA DAQ configuration: PROD67, Trigger: rgk_5na_noDC_v1.1_300MeV.trg<br />
- 30 nA DAQ configuration: PROD67, Trigger: rgk_30na_noDC_v1.1_300MeV.trg<br />
- 50 nA DAQ configuration: PROD67, Trigger: rgk_45na_noDC_v1.1_300MeV.trg<br />
<br />
'''Production Running'''<br />
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg<br />
- Beam current request: 75 nA (at 2C21A)<br />
- Run duration: 3 hrs<br />
<br />
=== Related Information ===<br />
Find detailed information at tab "GENERAL INFORMATION".<br />
<br />
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time. <br />
<br />
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running"). <br />
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").<br />
<br />
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.<br />
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).<br />
<br />
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.<br />
<br />
* '''Beam tuning and M&oslash;ller runs'''<br />
** Generally, Detector HV OFF but <br />
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''<br />
** Turn <b> DC HV </b> off only for beam tuning<br />
<br />
'''Access to the Hall'''<br />
* If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).<br />
* Check in with the shift personnel before entering the hall.<br />
<br />
{| {{TableStyle1}}<br />
<br />
== <font color=Navy> '''DAQ Operation''' & Related Information </font> == <br />
<br />
| valign=top width=50% |<br />
<br />
<font color=red>'''NEW STANDARD''' end and start of the run:</font><br />
:- "End run"<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.<br />
<br />
'''Restart DAQ''' <br />
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:<br />
:- "Cancel"<br />
:- "Reset"<br />
:- "Configure"<br />
:- "Download"<br />
:- "Prestart"<br />
:- "Go"<br />
<br />
| valign=top |<br />
<br />
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.<br />
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] . <br />
* If a ROC is disconnected, the message will appear in the run control message window.<br />
* If a '''ROC has crashed'''.<br />
** Find out which one (look for busy ROCs)<br />
** End the current run<br />
** Issue a '''roc_reboot''' command on just that ROC<br />
** ''PING'' the ROC to check that it is back up (some take longer than others)<br />
** '''Restart DAQ'''<br />
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. <br />
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.<br />
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.<br />
* In case of '''DAQ Disk space alarm''', call the DAQ expert.<br />
* Contact the DAQ expert if you have any questions or doubts about how to proceed.<br />
<br />
|}<br />
<br />
== <font color=Navy> '''Triggers files'''</font> ==<br />
<br />
{| class="wikitable"<br />
|-<br />
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.<br />
|-<br />
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.<br />
|-<br />
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.<br />
|-<br />
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.<br />
|}<br />
<br />
== <font color=Navy> '''Reference Values''' </font> ==<br />
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} --><br />
<br />
=== FSD Thresholds ===<br />
* Upstream: 2 kHz<br />
* Midstream: 2 kHz<br />
* Downstream: 100 kHz<br />
* BOM: 50 kHz<br />
* 5 ms dwell time<br />
<br />
=== Nominal Beam Positions ===<br />
<br />
'''2C21A''' (not important for production)<br />
* x = -0.4 mm<br />
* y = +0.7 mm<br />
<br />
'''2C24A''' <br />
* x = -1.7 mm<br />
* y = +0.5 mm<br />
<br />
'''2H01''' <br />
* x = -0.7 mm<br />
* y = +0.6 mm<br />
<br />
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4252495<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496<br />
<br />
2H01: https://logbooks.jlab.org/entry/4252514<br />
<br />
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===<br />
<br />
2C21A: https://logbooks.jlab.org/entry/4240375<br />
<br />
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378<br />
<br />
2H01: https://logbooks.jlab.org/entry/4240397</div>Carman