Difference between revisions of "Run Group E"

From clas12-run
Jump to navigation Jump to search
Line 106: Line 106:
  
 
* If you have any other questions or uncertainties about what to do, call the RC.
 
* If you have any other questions or uncertainties about what to do, call the RC.
 
 
* '''New RICH recovery protocol'''
 
:• See '''https://logbooks.jlab.org/entry/4201728''' for important details.
 
:• In case of a RICH issue a '''screen shot of both scalers and temperatures''' should be logged in the '''RICH logbook''' before running the appropriate recovery.
 
:•  '''Issues''' can be seen from missing tiles in the scaler and temperature GUIs or the occupancy as seen in MON12. Do not stop an ongoing run, but do the '''fast recovery between runs'''.
 
:• If the issue is seen in the scaler but not in the temperature GUI, then you should do a full recovery; see https://logbooks.jlab.org/entry/4214184. This might preempt the daily full recovery.
 
:• '''Daily full RICH recovery''' remains part of the protocol, preferably done during the daytime and only between runs; do not stop an ongoing run. State in your shift summary that you did the recovery (or why you did not).
 
:• '''Avoid unnecessary recoveries''', see https://logbooks.jlab.org/entry/4208477. The RICH overview GUI shows how many seconds have passed since the last full recovery. Also, there is a minor alarm when 24 hours have passed since the last full recovery. Acknowledge the alarm and wait for the end of the run before running the recovery.
 
:• Note that you have to '''RESTART DAQ from scratch (cancel-->reset-->configure-->download-->Prestart-->Go); see DAQ Opration under {{#switchtablink:Short_Term_Schedule|Short Term Schedule}}, after any RICH recovery'''.
 
::◊ In case of getting a '''ROC error''' during the recovery, it's advised to "'''roc_reboot rich4'''" in the '''DAQ VNC terminal'''.
 
:• '''If the beam is ON and a RICH recovery is taking more than 5 min, please call the RICH expert''', preferably ''the secondary number before the primary''.
 
* For any '''RICH problems overnight or on weekends/holidays, please call the RICH expert''', preferably ''the secondary number before the primary'', '''along with the RC''' (''eventually the AC will get involved'') to discuss and fix the issue! 
 
 
  
 
* '''New MVT LV Reboot Procedure'''
 
* '''New MVT LV Reboot Procedure'''
Line 129: Line 115:
 
::◊ Start a run by initializing DAQ from scratch: cancel-->reset-->configure-->download-->Prestart-->Go.  
 
::◊ Start a run by initializing DAQ from scratch: cancel-->reset-->configure-->download-->Prestart-->Go.  
 
::◊ '''If the beam is ON, and a reboot process takes more than 5 min, please call the DAQ and/or SVT/MVT/MM expert'''.  
 
::◊ '''If the beam is ON, and a reboot process takes more than 5 min, please call the DAQ and/or SVT/MVT/MM expert'''.  
 
  
 
* '''[https://bta.acc.jlab.org Fill out BTA]''' hourly;
 
* '''[https://bta.acc.jlab.org Fill out BTA]''' hourly;
:• Accelerator beam time:
 
::◊ ABU: acceptable beam used,
 
::◊ BANU: beam acceptable but not used (''should be reflected in our PCC or UED'');
 
:::- ''Exception: BANU due to beam tuning with harp scans or Moller runs might be included in BNA''.
 
::◊ BNA: beam not acceptable (e.g., tuning, drifting, not focused);
 
::◊ ACC: Accelerator configuration change (e.g., pass change or Maintenance/beam studies recovery);
 
::◊ OFF: Accelerator is down.
 
:• Experiment beam time (do change these values):
 
::◊ ER: Experiment ready (should be 1 hour - PCC - UED)
 
::◊ PCC: Planned configuration change (beam tuning with harp scans or Moller runs, target change, DAQ; e.g., stopping/starting runs, tests, etc.)
 
::◊ UED: Unplanned experiment down (hardware failure, DAQ crashes, or experiment/hall problems)
 
:::- ''Exception: BANU, due to time spent on drifting beam positions after beam down, may be counted as ER on our side''.
 
:• Enter fields at the "Shift Information" tab;
 
:• 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.' You can check here, https://ace.jlab.org/btm/reports/activity-audit, whether you saved correctly!
 
::◊ Acknowledge the popup error message about the last hour not being completed by clicking OK.
 
:• Sign, viz log completed 8-hour sheet.
 
:• '''Note: we can change the timesheet up to 48 hours after completion.'''
 
  
 
= Shift Worker =
 
= Shift Worker =
Line 218: Line 186:
 
=== Data Quality ===
 
=== Data Quality ===
 
* MON12 histograms: reference and most recent uploads  
 
* MON12 histograms: reference and most recent uploads  
:&bull; '''New'''; 95 nA on CuSn target (S<sub>T</sub>=+1.0): [https://clas12mon.jlab.org/mon12/histograms/?reference=4223511 run 18875]
+
** [https://clas12mon.jlab.org/mon12/histograms/?reference=4223511 run 18875]
* [https://clasweb.jlab.org/clas12online/timelines/rg-d/RGD2023_progress_all.html Total Charge on Target Plot]
+
* [https://clasweb.jlab.org/clas12online/timelines/ Total Charge on Target Plot]
* [https://clasweb.jlab.org/hydra/dashboard2.html Hydra] (CUE Login) Google-Chrome ONLY, Not Firefox!
+
* [https://clasweb.jlab.org/hydra/dashboard2.html Hydra] (CUE Login)
 
|}
 
|}
  

Revision as of 11:53, 26 February 2024

[edit]


Clas12design.png