Difference between revisions of "Run Group E"
Jump to navigation
Jump to search
| (32 intermediate revisions by 3 users not shown) | |||
| Line 20: | Line 20: | ||
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/torus/Hall_B_Torus_Power-Up_and_Power-Down_Procedure.pdf Torus] | * [https://github.com/JeffersonLab/clas12-manuals/raw/master/torus/Hall_B_Torus_Power-Up_and_Power-Down_Procedure.pdf Torus] | ||
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/torus/Hall_B_Solenoid_Power-Up_and_Power-Down_Procedure.pdf Solenoid] | * [https://github.com/JeffersonLab/clas12-manuals/raw/master/torus/Hall_B_Solenoid_Power-Up_and_Power-Down_Procedure.pdf Solenoid] | ||
| − | * [https://docs.google.com/document/d/1kBNmLYg2gqa4XjWgMpbh0rBUxkSAupqdnMV4THepv7k/edit#heading=h.13kef88y2w8q Cryotarget] | + | <!--* [https://docs.google.com/document/d/1kBNmLYg2gqa4XjWgMpbh0rBUxkSAupqdnMV4THepv7k/edit#heading=h.13kef88y2w8q Cryotarget]--> |
| + | * [https://wiki.jlab.org/clas12-run/images/4/49/Hall_B_Cryotarget_Controls_Manual_and_RGE_Solid_Target.pdf Cryotarget & RG-E Solid-foil Assembly] | ||
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/daq/opman_master.pdf DAQ] | * [https://github.com/JeffersonLab/clas12-manuals/raw/master/daq/opman_master.pdf DAQ] | ||
* [[Media:clas12controls_shift.pdf|Slow Controls]] | * [[Media:clas12controls_shift.pdf|Slow Controls]] | ||
| Line 84: | Line 85: | ||
=== New '''MVT LV''' Reboot Procedure === | === New '''MVT LV''' Reboot Procedure === | ||
| − | 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 | + | 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 experts only. |
* Turn '''LV OFF from MVT Overview->Low Voltage->MVT-All'''. LV status indicators should change from green to black; | * Turn '''LV OFF from MVT Overview->Low Voltage->MVT-All'''. LV status indicators should change from green to black; | ||
* '''Wait 20 seconds''', then '''turn LV back from the same menu'''. | * '''Wait 20 seconds''', then '''turn LV back from the same menu'''. | ||
| − | * | + | * An alarm "NActiveCrates" can be created in the alarm handler with a 2-minute delay; the status is also visible on the MVT Overview GUI. This alarm will be cleared 2 minutes after LV is turned back ON. |
* Reboot mvt1, mvt2, and mvt3 ROCS. | * Reboot mvt1, mvt2, and mvt3 ROCS. | ||
* Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go). | * Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go). | ||
| − | * '''If we have beam | + | * '''If we have a beam and a reboot process takes more than 5 minutes, call the DAQ or MVT expert'''. |
=== RICH issues === | === RICH issues === | ||
| − | * The RICH fibers alarm leads to web guidance aka logbook entry [https://logbooks.jlab.org/entry/3562273 3562273 - RICH recovery procedure]. | + | * The RICH fibers alarm leads to web guidance, aka logbook entry [https://logbooks.jlab.org/entry/3562273 3562273 - RICH recovery procedure]. |
* Check the RICH manual for the current guidance: '''https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf''' | * Check the RICH manual for the current guidance: '''https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf''' | ||
* See below for current issues | * See below for current issues | ||
| Line 99: | Line 100: | ||
=== Rapid/Controlled Access to the Hall === | === Rapid/Controlled Access to the Hall === | ||
* 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. | * 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. | ||
| − | * 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. | + | * After a 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. |
=== 24/7 ZOOM connection for Counting House === | === 24/7 ZOOM connection for Counting House === | ||
| − | * Click on [https://jlab-org.zoomgov.com/j/1618614939 https://jlab-org.zoomgov.com/j/1618614939], included in "Remote Shifts" in | + | * Click on [https://jlab-org.zoomgov.com/j/1618614939 https://jlab-org.zoomgov.com/j/1618614939], which is included in "Remote Shifts" in the "{{#switchtablink:Shift_Worker|Shift Worker}}" tab. |
| − | * 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 | + | * 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. |
| − | * Enter the passcode from the logbook entry in | + | * Enter the passcode from the logbook entry in "{{#switchtablink:Shift_Worker|Shift Worker}}" tab. |
== '''Current Issues''' == | == '''Current Issues''' == | ||
=== Lights in the Hall === | === Lights in the Hall === | ||
| − | The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF because of light leaks | + | * The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF because of light leaks from some of the detectors. If these lights are switched on during an access, they '''should be switched off when leaving the Hall'''. |
* Refer to these photos: ON: [https://logbooks.jlab.org/entry/3825712], OFF: [https://logbooks.jlab.org/entry/3825731] | * Refer to these photos: ON: [https://logbooks.jlab.org/entry/3825712], OFF: [https://logbooks.jlab.org/entry/3825731] | ||
| − | * We have a '''new dome light switch outside | + | * We have a '''new dome light switch outside the hall''' in the labyrinth. See logbook entry: https://logbooks.jlab.org/entry/4204460 |
| − | * When the dome lights are switched off, they cannot be turned back on immediately | + | * When the dome lights are switched off, they cannot be turned back on immediately; they require 10-15 min to cool down. |
=== Beamline === | === Beamline === | ||
| − | * Orbit locks are on BPMs '''2C24A and 2H01''' | + | * Orbit locks are on BPMs '''2C24A and 2H01''', which should generally be on ("Running"). |
| − | + | :- Beam positions at 2C24A and 2H01 must be kept within ±0.1 mm at the nominal beam positions listed under "References" at the {{#switchtablink:Short_Term_Schedule|Short Term Schedule}} tab. | |
* 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. | * 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. | ||
** The beam position at 2C21A is important for initial beam tuning (on tagger dump). | ** The beam position at 2C21A is important for initial beam tuning (on tagger dump). | ||
*'''After the HWP change''' | *'''After the HWP change''' | ||
| − | + | :• 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. | |
| − | + | :• Start a new run | |
* '''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. | * '''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. | ||
| Line 129: | Line 130: | ||
* '''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. | * '''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. | ||
* BMT HV S1 L2 STRIP in safe mode (low voltage) by expert - appears blue in MVT overview | * BMT HV S1 L2 STRIP in safe mode (low voltage) by expert - appears blue in MVT overview | ||
| − | * BMT HV S1 L5 STRIP and DRIFT are OFF (Vset= | + | * BMT HV S1 L5 STRIP and DRIFT are OFF (Vset= 0 V) - appears blue in MVT overview |
| − | * BMT HV S2 L6 STRIP and DRIFT are OFF (Vset= | + | * BMT HV S2 L6 STRIP and DRIFT are OFF (Vset= 0 V) - appears blue in MVT overview |
| + | * <font color=red>'''As of 05/10-12/24: BMT HV S2 [L4, L1] & S3 L5 strip frequent trips'''</font>: The HV, Vset, was lowered by 10 V until it calmed down. If the problem persists, reduce the HV VSet value by an increment of 10 V after clicking the '''"Expert" button'''. Then, make a logbook entry and CC MVT/SVT/MM experts on it. | ||
* If FMT gas errors appear, please follow the instructions in [https://logbooks.jlab.org/entry/4286305] | * If FMT gas errors appear, please follow the instructions in [https://logbooks.jlab.org/entry/4286305] | ||
=== CND === | === CND === | ||
* CAMAC crate alarm: | * CAMAC crate alarm: | ||
| − | + | :• CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, which can be done via the alarm handler. | |
| − | + | :• After reboot, the CFD thresholds need to be set by running a script; see page 12 in the CND manual at the "General" tab: https://clasweb.jlab.org/wiki/images/9/97/Ops_manual_cnd.pdf | |
=== DAQ === | === DAQ === | ||
* 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! | * 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! | ||
| − | * <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. | + | * <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. |
| − | * | + | * ROC reboot instructions: |
| − | + | :• To reboot, i.e., adcecal1, or any noted ROC that became busy, type on a clasrun terminal: clasrun> roc_reboot adcecal1 | |
| − | + | :• To check that the crate is back alive, type:clasrun> ping adcecal1 | |
| − | + | :• The ping will start to answer as soon as the crate communicates again, then press Ctrl+C to exit ping. | |
=== DC === | === DC === | ||
| Line 150: | Line 152: | ||
=== ECAL/PCAL === | === ECAL/PCAL === | ||
| − | * | + | * "ECAL_SEC6_UO26 Noisy" https://logbooks.jlab.org/entry/4241957 |
* "PCAL_HV_SEC2_U25 turned off" https://logbooks.jlab.org/entry/4247187, https://logbooks.jlab.org/entry/4247400 | * "PCAL_HV_SEC2_U25 turned off" https://logbooks.jlab.org/entry/4247187, https://logbooks.jlab.org/entry/4247400 | ||
| Line 159: | Line 161: | ||
=== RICH === | === RICH === | ||
* '''Known problematic PMTs and tile''': | * '''Known problematic PMTs and tile''': | ||
| − | + | :- You don't need to report about it. | |
| − | + | :- PMT 2 (sector 1) and PMT 92 (sector 4) are not completely dead and may be visible depending on statistics. | |
| − | + | :- Problematic tiles and PMTs: | |
| − | + | ::• Sector 1 Tile 21 dead (PMT 55,56,57) | |
| − | + | ::• Sector 1 Tile 1 PMT 2 | |
| − | + | ::• Sector 4 Tile 34 PMT 92 | |
== '''Beam Restoration''' == | == '''Beam Restoration''' == | ||
| − | * 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 | + | * 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 doing this alone, contact the Beamline Expert. |
| − | * Find all Reference values on the | + | * Find all Reference values on the CH whiteboard and the {{#switchtablink:Short_Term_Schedule|Short Term Schedule}} tab. |
=== Restoring Beam after Short Downtime === | === Restoring Beam after Short Downtime === | ||
* 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 | * 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 | ||
| − | + | :• beam steering or orbit change | |
| − | + | :• change in beam current, e.g., after a target change | |
| − | + | :• If BPM 2C24A and 2H01 positions are off (not within +/-0.1 mm), ask MCC to bring them to the reference values | |
=== Beam Tuning to Tagger Yoke Dump === | === Beam Tuning to Tagger Yoke Dump === | ||
| − | Study the manual: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam]. | + | * Study the manual: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam]. |
* Contact Eugene Pasyuk if issues arise. | * Contact Eugene Pasyuk if issues arise. | ||
* Ask MCC to energize the tagger magnet | * Ask MCC to energize the tagger magnet | ||
| − | : | + | :• blank collimator |
| − | : | + | :• beam type "Photon" |
* All CLAS12 detectors HV off (BMT HV in safe mode) | * All CLAS12 detectors HV off (BMT HV in safe mode) | ||
| Line 193: | Line 195: | ||
* Ask MCC for 5 nA beam current and make sure the Orbit Locks are OFF; | * Ask MCC for 5 nA beam current and make sure the Orbit Locks are OFF; | ||
* If necessary, ask MCC to bring the 2C21A and 2C24A beam positions to the Reference Values | * If necessary, ask MCC to bring the 2C21A and 2C24A beam positions to the Reference Values | ||
| − | * Take harp scans | + | * Take harp scans: |
| − | : | + | :• at Harp 2C21A (Upstream Right Counter) |
| − | : | + | :• at Tagger Harp 2C24A Upstream Right Counter) |
* 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. | * 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. | ||
* Compare the results with the Harp Scan References | * Compare the results with the Harp Scan References | ||
| Line 204: | Line 206: | ||
=== Møller run === | === Møller run === | ||
| − | Follow the standard procedure as described in the manual [https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf Performing Møller Runs]. | + | * Follow the standard procedure as described in the manual [https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf Performing Møller Runs]. |
* Contact Nathan Baltzell if issues arise | * Contact Nathan Baltzell if issues arise | ||
| − | A few points to note: | + | * A few points to note: |
| − | + | :• '''Request 20 nA''' , Orbit Locks should be off | |
| − | + | :• The BPMs 2C21 and 2C24A may be out of range after the Møller configuration. | |
| − | + | :• Keep running until the polarization uncertainty is < 1.5% | |
=== Beam Tuning to Faraday Cup === | === Beam Tuning to Faraday Cup === | ||
| − | Study the manual | + | * Study the manual [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam] and consider the first steps mentioned therein. |
| − | This is typically done after tuning to the tagger dump (and possibly taking a Moller run). | + | * This is typically done after tuning to the tagger dump (and possibly taking a Moller run). |
| − | * All CLAS12 detectors HV | + | * All CLAS12 detectors HV OFF (MVT HV ON in SAFE Mode) |
* Ask MCC to de-energize the tagger magnet | * Ask MCC to de-energize the tagger magnet | ||
| − | : | + | :• 20 mm collimator |
| − | : | + | :• beam type electron |
| − | : | + | :• beam blocker out |
| − | * If initial beam tune, target should be "Empty" | + | * If initial beam tune, the target should be "Empty" |
* Ask MCC to unmask beam halos | * Ask MCC to unmask beam halos | ||
* Set the halo counter FSD thresholds to 1 MHz and the integration time interval to 50 milliseconds | * Set the halo counter FSD thresholds to 1 MHz and the integration time interval to 50 milliseconds | ||
| Line 235: | Line 237: | ||
* If good, log the new scan results. | * If good, log the new scan results. | ||
| − | Once done and before resuming the production data-taking: | + | * Once done and before resuming the production data-taking: |
| − | + | :• Retract the Downstream Viewer from the beamline | |
| − | + | :• Put the FSDs thresholds and integration time to their reference values | |
| − | + | :• Turn all detector HV ON, for MVT "HV ON - Full Voltage" | |
| − | + | :• MCC might need to adjust the beam positions after going to the production beam current. | |
<!--####################################### Shift Expert ################################################--> | <!--####################################### Shift Expert ################################################--> | ||
= Shift Expert = | = Shift Expert = | ||
| − | + | * Arrive at your shift in time for the '''shift change''', 10-15 minutes before the start of your shift. | |
| − | + | :• 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. | |
| − | Follow the '''Short Term Schedule''' | + | * Follow the '''{{#switchtablink:Short_Term_Schedule|Short Term Schedule}}'''; |
| − | + | :• The RC must be notified before changing run conditions. | |
| − | Operate the '''Data Acquisition''' | + | * Operate the '''Data Acquisition'''. |
| − | Take action on and log '''alarms''' | + | * Take action on and log '''alarms'''. |
| − | + | * '''Communicate''' with your co-shift person: | |
| − | + | :• Remind them to read the tab 'Shift Worker'. | |
| − | + | :• The shift worker should discuss an issue with the shift expert before making extra logbook entries. | |
| − | + | :• During production, not in extended downtime, the shift expert should ensure the shift worker is filling their '''end-of-shift Checklist''' when the beam is ON, not in the period of beam trips. | |
| − | + | :• <font color=red> Use the CS-Studio '''Logbook entry tool''' for all screenshots (but the strip charts)!</font> | |
| − | : | + | :• Note that the Logbook Entry tool defaults the entry in the HBRUN logbook. Other logbooks can be added or selected from the drop-down menu. |
| − | |||
| − | |||
| − | + | * Check for and read any comments made to '''log-book entries''' during your shift. | |
| − | * | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | * Keep your '''shift summary''' up to date in HBLOG. Record all shift activities, issues, if any, and related communications with experts with details and/or reference to any associated logbook entries: | |
| + | :- Refer to relevant logbook entries in the shift summary. | ||
| + | :- Include a list of runs taken during the shift with relevant run information; | ||
| + | ::• See, for instance, this [https://logbooks.jlab.org/entry/4214804 shift summary] where all relevant run info, links, and shift activities are cited. | ||
| − | + | * Ensure that all '''MON12 monitoring plots''' are logged and checked against the reference plots for every single run; see the links under {{#switchtablink:Monitoring|Monitoring}} tab; | |
| − | * | + | :• Both, you and the shift worker should run MON12 and '''reset & check spectra frequently'''. |
| − | |||
| − | |||
| − | Ensure that all '''monitoring plots''' | ||
| − | |||
* If the worker shift is remote, maintain communication over Zoom. | * If the worker shift is remote, maintain communication over Zoom. | ||
| Line 283: | Line 277: | ||
* 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. | ||
| − | + | * 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 | |
| − | + | * '''New MVT LV Reboot Procedure''' can be found in the {{#switchtablink:General_Information|General Information}} tab. | |
| − | ''' | + | * At '''the end of the shift''', submit the '''strip charts''' to the logbook: |
| + | :- If they are not up already: (CS-Studio → Tools → Strip Charts → livePlot) | ||
| + | :- Right-click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters" | ||
| + | :- Choose a '''time-span width of 10 hours''' (right-click below x-axis) | ||
| + | :- <font color=red> To make a logbook entry:</font> | ||
| + | ::• Right-click within the grid of one of the charts, choose "Make Logbook Entry" | ||
| + | ::• The title of the logbook entry can be changed, eg to Strip charts | ||
| + | ::• Un-click ELOG, select HBLOG and click "Make Entry" to submit. | ||
| − | '''[https://ace.jlab.org/btm Fill out BTA]''' hourly; | + | * '''[https://ace.jlab.org/btm Fill out BTA]''' hourly; |
* Accelerator beam time (do not change these values): | * Accelerator beam time (do not change these values): | ||
| − | + | :• ABU: acceptable beam used | |
| − | + | :• BANU: beam acceptable but not used (should be reflected in our PCC and UED) | |
| − | + | :• BNA: beam not acceptable (e.g., tuning, drifting, not focused) | |
| − | + | :• ACC: Accelerator Configuration Change (e.g., pass change) | |
| − | + | :• OFF: Accelerator is down | |
* Experiment beam time (do change these values): | * Experiment beam time (do change these values): | ||
| − | + | :• ER: Experiment ready (should be 60 minutes - PCC - UED) | |
| − | + | :• PCC: Planned configuration change (when the beam is masked while radiators are moved, target change, DAQ (stopping/starting runs, tests, etc.) | |
| − | + | :• UED: Unplanned experiment down (hardware failure, DAQ crashes, our problems, ...) | |
| − | + | :• ''Exception'': ''BANU, due to time spent on beam tuning and BPM checks after beam down, should be counted as ER on our side''. | |
* Enter fields at the "Shift Information" tab. | * Enter fields at the "Shift Information" tab. | ||
| − | * | + | * To send information to MCC, you must save at 7:00, 15:00, and 23:00. To see the save button, click 'edit all' or 'Edit CC Hours.' |
* Acknowledge the popup error message about the last hour not being completed by clicking OK. | * Acknowledge the popup error message about the last hour not being completed by clicking OK. | ||
* Sign, viz log completed 8-hour sheet. | * Sign, viz log completed 8-hour sheet. | ||
* '''Note: we can change the time sheet up to 48 hours after completion.''' | * '''Note: we can change the time sheet up to 48 hours after completion.''' | ||
| + | |||
<!--####################################### Shift Worker ################################################--> | <!--####################################### Shift Worker ################################################--> | ||
= Shift Worker = | = Shift Worker = | ||
| − | Come to your shift in time for the '''shift change''', 10-15 minutes before the start of your shift; | + | * Come to your shift in time for the '''shift change''', 10-15 minutes before the start of your shift; |
| − | + | :• 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. | |
| − | 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. | + | * 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. |
| − | <font color=red> Use the CS-Studio '''Logbook entry tool''' for all screen shots | + | * <font color=red> Use the CS-Studio '''Logbook entry tool''' for all screen shots, except the strip charts! </font> |
=== Frequently === | === Frequently === | ||
| − | Reset and check | + | * Reset and check MON12 histograms frequently, preferably each 1 h, during a run; |
| − | + | :• Note that some plots have radio buttons at the bottom to choose the sector. Remember to cycle through and check all sectors. | |
=== Once per run === | === Once per run === | ||
| − | Note that the CS-Studio | + | * 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. |
| − | Using the Logbook Entry tool, submit EPICS '''screenshots''' to the HBRUN logbook (one logbook entry) '''with beam ON''' | + | * Using the Logbook Entry tool, submit EPICS '''screenshots''' to the HBRUN logbook (one logbook entry) '''with beam ON''': |
# Beamline overview (remote shift: in VNC or [https://hallbopi.jlab.org/webopi3.3/w?opi=beamline/clas12-web.opi Web Browser]) | # Beamline overview (remote shift: in VNC or [https://hallbopi.jlab.org/webopi3.3/w?opi=beamline/clas12-web.opi Web Browser]) | ||
# DAQ status | # DAQ status | ||
# CLAS12 trigger rates | # CLAS12 trigger rates | ||
| − | Upload '''mon12''' monitoring plots to the logbook with sufficient statistics and compare them to the reference and recent uploads (see {{#switchtablink:Monitoring|Monitoring}} tab). | + | * Upload '''mon12''' monitoring plots to the logbook with sufficient statistics and compare them to the reference and recent uploads (see {{#switchtablink:Monitoring|Monitoring}} tab). |
| − | At the '''end of the run''' | + | * At the '''end of the run''': |
| − | + | :- Submit the '''strip charts''' to the logbook: | |
| − | + | ::• If they are not up already: (CS-Studio → Tools → Strip Charts → livePlot) | |
| − | + | ::• Right-click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters" | |
| − | + | ::• Choose a '''time-span width of 4 hours''', compatible with the run duration (right-click below x-axis) | |
| − | :- | + | ::• <font color=red> To make a logbook entry:</font> |
| − | : | + | ::• Right-click within the grid of one of the charts, choose "Make Logbook Entry" |
| − | : | + | ::• The title of the logbook entry can be changed, eg to Strip charts |
| − | + | ::• Un-click ELOG, select HBLOG, and click on "Make Entry" to submit | |
| − | + | :- Upload the '''[https://github.com/JeffersonLab/caos/tree/main#readme clas12online]''' plots to the logbook. | |
| − | + | ::• The program can continue through a standard end/start of a run. However, after a DAQ restart, you must back out and restart clas12online. | |
| − | + | ::• If the DAQ has to be restarted, you can still make the upload before backing out. | |
=== Once per shift === | === Once per shift === | ||
| − | Fill the '''[https://logbooks.jlab.org/checklists/151 shift checklist]'''; | + | * Fill the '''[https://logbooks.jlab.org/checklists/151 shift checklist]'''; |
| − | + | :• During production, get relevant values from the epics screens Beamline Overview, CLAS12 DAQ Status and CLAS12 Trigger; | |
| − | + | :• During extended downtime, get relevant values from the latest EPICS screenshots that you made during production | |
== For Remote Shifts == | == For Remote Shifts == | ||
| − | <font color=red>'''Please inform the PDL that your shifts will be remote.''' </font color=red> | + | * <font color=red>'''Please inform the PDL that your shifts will be remote.''' </font color=red>. Remote shifts are listed [[upcoming-remote-shifts|here]] |
| − | Remote shifts are listed [[upcoming-remote-shifts|here]] | + | * You must test your setup, including ZOOM and VNC connections, at least 24 hours before your first shift! |
| − | + | :♦ ZOOM for 24-7 communication with Counting House: | |
| − | You must test your setup, including | + | ::• In a Web-browser: [https://jlab-org.zoomgov.com/j/1618614939 https://jlab-org.zoomgov.com/j/1618614939]; Or in the ZOOM APP: Enter the meeting #: '''1618614939''', then |
| − | + | :::- The required passcode can be obtained from [https://logbooks.jlab.org/entry/4158818 this log entry] | |
| − | + | * Remind the expert in the counting house to restart their ZOOM, if necessary | |
| − | + | * Remote VNC connection instructions: https://logbooks.jlab.org/entry/3906039: | |
| − | + | :• '''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 web pages. | |
| − | + | :• All necessary applications should be available from the desktop menu (left/right click on the desktop) | |
| − | * Remote VNC connection instructions: | + | :• EPICS GUIs should be accessed '''ONLY''' via the desktop menu or by running <tt>clascss-remote</tt>. |
| − | |||
| − | |||
| − | |||
<!--* [https://userweb.jlab.org/~baltzell/clas12/shift/remote-demo.mp4 Remote Demonstration Video (150 MB)]--> | <!--* [https://userweb.jlab.org/~baltzell/clas12/shift/remote-demo.mp4 Remote Demonstration Video (150 MB)]--> | ||
| − | + | :• 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] | |
| Line 373: | Line 372: | ||
= Run Coordinator = | = Run Coordinator = | ||
| − | Check the '''upcoming shifts''', and if necessary, coordinate with the PDL to contact shift takers about their training and site access status. | + | * Check the '''upcoming shifts''', and if necessary, coordinate with the PDL to contact shift takers about their training and site access status. |
| − | '''Remote shifts''' are listed [[Upcoming-remote-shifts|here]]. | + | * '''Remote shifts''' are listed [[Upcoming-remote-shifts|here]]. |
| − | '''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]. | + | * '''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]. |
| − | '''Meeting ZOOM connections:''' see | + | * '''Meeting ZOOM connections:''' see {{#switchtablink:Important Links|Important Links}} or {{#switchtablink:Short_Term_Schedule|Short Term Schedule}} tab |
=== Daily === | === Daily === | ||
| Line 385: | Line 384: | ||
* '''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. | * '''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. | ||
| − | * Update the run plan in | + | * Update the run plan in the '''{{#switchtablink:Short_Term_Schedule|Short Term Schedule}}''' tab, as well as ''the whiteboard in CH'', in coordination with the RG-E experiment Run Coordinators and communicate it to the shift crew. |
* Log the '''RC Daily summary''' in the HBLOG. | * Log the '''RC Daily summary''' in the HBLOG. | ||
| − | + | * '''[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 the {{#switchtablink:Shift_Expert|Shift Expert}} tab. The BTA information can be modified post-signature. | |
| − | + | :• NOTE: "After 48 hours, you cannot modify a User signed timesheet unless you are the signer, Hall Manager, or Admin". | |
| − | * ''' | ||
| − | |||
* Run the daily '''RC meetings''' in CH Room 200C and on ZOOM | * Run the daily '''RC meetings''' in CH Room 200C and on ZOOM | ||
| − | + | :• Mo-Tu,Th-Fr at 13:00 ET in the Counting House Conference Room | |
| − | + | :• Wednesdays at 3 PM, ZOOM only | |
| − | + | :• Weekends upon agreement | |
| − | + | :• Send a '''daily invitation''' for the RC meeting to mailing lists hallb, clas12_rge, clas_members. | |
| − | |||
* Connect to '''Zoom in CH Room 200C''': | * Connect to '''Zoom in CH Room 200C''': | ||
| − | + | :• 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. | |
| − | + | :• Once logged in, use the recommended Google Chrome to join the ZOOM meeting on the browser or use the ZOOM application. | |
| − | + | :• Since the room doesn't have audio, don't connect with the computer audio, but '''Call the 1-833-xxx-xxxx number shown in the ZOOM session on the small Cisco answering device'''. Once prompted, enter the '''meeting ID''' followed by the '''participant ID''' displayed in the ZOOM session to join the meeting. | |
| − | + | :• The room has a camera, which can be turned on via ZOOM. | |
=== Weekly === | === Weekly === | ||
*'''MCC/OPS planning meeting''', on Wednesdays at 13:30, MCC building. | *'''MCC/OPS planning meeting''', on Wednesdays at 13:30, MCC building. | ||
| − | + | :• 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. | |
| − | + | :• The summary covers the data-taking status '''from 7 a.m. on the previous Wednesday to 7 a.m. on the current Wednesday'''. | |
| − | + | :• '''Beam time accounting''': [https://ace.jlab.org/btm/reports/physics-summary Beam Time Manager; Physics Time Accounting] | |
| − | + | :• The '''total experiment data collected to date''' could be retrieved from the up-to-date Accumulated "Charge" or "Luminosity" depicted on the "RG-E 2024 Progress" plot. See the {{#switchtablink:Monitoring|Monitoring}} tab | |
| − | *'''Hall B meeting''' is on Mondays at 9 AM. Present your summary slides | + | *'''Hall B meeting''' is on Mondays at 9 AM. Present your summary slides, which should be sent beforehand to the Hall B leader, Patrick Achenbach. |
| Line 426: | Line 422: | ||
* [http://hallbcam02.jlab.org Hall Fisheye]; [http://hallbcam00.jlab.org/aca/index.html#view Additional Hall Cams] | * [http://hallbcam02.jlab.org Hall Fisheye]; [http://hallbcam00.jlab.org/aca/index.html#view Additional Hall Cams] | ||
* Faraday Cup beam viewer | * Faraday Cup beam viewer | ||
| − | + | :• To reboot it, run <tt>beam-viewer-reboot</tt> | |
* 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] | * 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] | ||
| Line 438: | Line 434: | ||
| valign=top | | | valign=top | | ||
=== Data Quality === | === Data Quality === | ||
| − | * mon12 histograms: [https://clas12mon.jlab.org/mon12/histograms/?reference= | + | * MON12 histograms: reference and most recent uploads |
| + | :• '''New''': LD2+Al dual-target @ 70 nA: [https://clas12mon.jlab.org/mon12/histograms/?reference=4299824 run #: 20438] | ||
| + | :• '''Old''': LD2+Sn dual-target @ 65 nA: [https://clas12mon.jlab.org/mon12/histograms/?reference=4295017 run #: 20367] | ||
* [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) Google-Chrome ONLY, Not Firefox! | ||
| − | * [https://github.com/JeffersonLab/caos/tree/main#readme clas12mltrack | + | * [https://github.com/JeffersonLab/caos/tree/main#readme clas12mltrack]: real-time reconstructed vertices & various event topologies |
| − | + | * Data CHARGE accumulation timeline [https://clasweb.jlab.org/clas12online/timelines/rg-e/RGE2024_progress_all_charge.html]; LUMINOSITY accumulation timeline [https://clasweb.jlab.org/clas12online/timelines/rg-e/RGE2024_progress_all_lumi.html]. | |
| − | * [https://clasweb.jlab.org/clas12online/timelines/rg-e/RGE2024_progress_all_charge.html] Data CHARGE accumulation timeline [https://clasweb.jlab.org/clas12online/timelines/rg-e/ | + | <!--https://clasweb.jlab.org/clas12online/timelines/rg-e/RGE2024_progress_all_lumi.html] |
| − | + | * [https://clasweb.jlab.org/clas12online/timelines/rg-e/RGE2024_progress_all_charge.html] Data CHARGE accumulation timeline [https://clasweb.jlab.org/clas12online/timelines/rg-e/RGE2024_progress_all_lumi_unzoom.html] LUMINOSITY accumulation timeline--> | |
|} | |} | ||
| Line 469: | Line 467: | ||
===ZOOM Meetings=== | ===ZOOM Meetings=== | ||
* 07:45 [https://jlab-org.zoomgov.com/j/1611740648 RC/PD Morning Meeting], passcode is 933173 | * 07:45 [https://jlab-org.zoomgov.com/j/1611740648 RC/PD Morning Meeting], passcode is 933173 | ||
| − | * 08:00 [https://jlab-org.zoomgov.com/j/1601304841?pwd=Z1RIOVVUdkdXL2R2LzREZUNOUlh1dz09 MCC/OPS | + | * 08:00 [https://jlab-org.zoomgov.com/j/1601304841?pwd=Z1RIOVVUdkdXL2R2LzREZUNOUlh1dz09 MCC/OPS 8:00 M thru F and 13:30 Wednesday Meeting] |
* [https://logbooks.jlab.org/entry/4000274 See also this logbook entry] | * [https://logbooks.jlab.org/entry/4000274 See also this logbook entry] | ||
* Daily Hall B Run Coordinator Meeting: | * Daily Hall B Run Coordinator Meeting: | ||
| − | + | :• [https://jlab-org.zoomgov.com/j/1605705819#success URL Link] (''including Passcode'') | |
| − | + | :• Meeting ID: '''160 570 5819''' | |
| − | + | :• Passcode: ''see emails'' | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | :• | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | : | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
* [https://logbooks.jlab.org/entry/4158818 Hall B Remote Shifts & Counting House] | * [https://logbooks.jlab.org/entry/4158818 Hall B Remote Shifts & Counting House] | ||
|} | |} | ||
Latest revision as of 00:22, 15 May 2024
[edit]
Daily RC Meetings at 13:00 in CH Room 200C, and on ZOOM: URL Link (Meeting ID: 1605705819), except on Wednesdays, which is @ 15:00 in CH Room 200C and at the same ZOOM link.
- General
- Phone Numbers
- Short Term Schedule
- General Information
- Shift Expert
- Shift Worker
- Run Coordinator
- Monitoring
- Important Links
GeneralLogbookShift ScheduleRG-E Run Coordinator ScheduleESAD, COO, RSADShift ChecklistBeam Time AccountingHot Checkout |
ManualsSystemsSoftwareDetectors |
Procedures
Logbooks
|
|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
- Note, all non-JLab numbers must be dialed with an area code. When calling from a counting-house landline, dial "9" first.
- To call JLab phones from outside the lab, all 4-digit numbers must be preceded by 757-269
- Click Here to edit Phone Numbers. Note, you then also have to edit the current page to force a refresh.
Run Coordinator: Sebouh Paul (757) 575-7540
PDL: Nathan Baltzell (757) 876-1789, Office: x5902
Important Notes
- In case of medical or fire emergency, call 911 or 9-911 from a LANDLINE phone in the Counting House and inform the Crew Chief and RC.
- In case of evacuation of the Counting Room (e.g., due to a fire alarm), grab the shift expert phone and leave the room through the "EXIT" door leading to the parking lot. Do not leave through the hallway! Call the RC once outside so the latter can call MCC to turn the beam OFF for Hall B and inform other Hall B staff members.
- If you have symptoms or a positive COVID test, do NOT come to your shift. Instead, inform the PDL, the RC, and JLab medical services immediately to arrange replacements.
- In case of a problem with the HV Slow Controls, EPICS in general, please call the primary expert on-call, Nathan Baltzell, before reaching out to anyone else.
- Please put all essential information on the main Hall B logbook HBLOG. Some important alarms have been documented on HBRUN. Use the pulldown menu to choose where an error is reported.
Current Run Plan: May 8th to May 19th
Lumi Scan for LD2+Pb on May 15th - 16th
Previous Dual-target Configuration Plans- DC firmware test plan (LD2 + Pb)1) Take one run each with 1M events with the trigger files and beam current at 70 nA
2) Take one run with 500k events and beam current at 35nA with trigger file rge_inb_v1.0_200MeV_dcrb17_2.trg 3) Take one run with 500k events and beam current at 35nA with trigger file rge_inb_v1.0_200MeV_dcrb17_4.trg
*** Notes ***
LD2+Pb runs
LD2+Sn runs
LD2+Al runs
Lumi Scan for LD2+Al on May 15th
|
References- BPM Positions
- Harp Scans- FSD Thresholds
- Charge Asymmetry- Upstream Halo counters
|
General Reminders
|
DAQ Operation
|
This tab contains information on
- Recent Changes
- Current Issues
- Beam Restoration
Recent Changes
New MVT LV Reboot Procedure
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 experts only.
- Turn LV OFF from MVT Overview->Low Voltage->MVT-All. LV status indicators should change from green to black;
- Wait 20 seconds, then turn LV back from the same menu.
- An alarm "NActiveCrates" can be created in the alarm handler with a 2-minute delay; the status is also visible on the MVT Overview GUI. This alarm will be cleared 2 minutes after LV is turned back ON.
- Reboot mvt1, mvt2, and mvt3 ROCS.
- Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go).
- If we have a beam and a reboot process takes more than 5 minutes, call the DAQ or MVT expert.
RICH issues
- The RICH fibers alarm leads to web guidance, aka logbook entry 3562273 - RICH recovery procedure.
- Check the RICH manual for the current guidance: https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf
- See below for current issues
Rapid/Controlled Access to the Hall
- 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.
- After a 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.
24/7 ZOOM connection for Counting House
- Click on https://jlab-org.zoomgov.com/j/1618614939, which is included in "Remote Shifts" in the "Shift Worker" tab.
- 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.
- Enter the passcode from the logbook entry in "Shift Worker" tab.
Current Issues
Lights in the Hall
- The main lights in the Hall (dome lights) and the Forward Carriage lights must be OFF because of light leaks from some of the detectors. If these lights are switched on during an access, they should be switched off when leaving the Hall.
- Refer to these photos: ON: [2], OFF: [3]
- We have a new dome light switch outside the hall in the labyrinth. See logbook entry: https://logbooks.jlab.org/entry/4204460
- When the dome lights are switched off, they cannot be turned back on immediately; they require 10-15 min to cool down.
Beamline
- Orbit locks are on BPMs 2C24A and 2H01, which should generally be on ("Running").
- - Beam positions at 2C24A and 2H01 must be kept within ±0.1 mm at the nominal beam positions listed under "References" at the Short Term Schedule tab.
- 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.
- The beam position at 2C21A is important for initial beam tuning (on tagger dump).
- After the HWP change
- • 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.
- • Start a new run
- 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.
BMT / SVT
- If new hot channels appear, call the SVT/MM expert Yuri Gotra (757-541-7539). These channels need to be addressed by the expert.
- 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.
- BMT HV S1 L2 STRIP in safe mode (low voltage) by expert - appears blue in MVT overview
- BMT HV S1 L5 STRIP and DRIFT are OFF (Vset= 0 V) - appears blue in MVT overview
- BMT HV S2 L6 STRIP and DRIFT are OFF (Vset= 0 V) - appears blue in MVT overview
- As of 05/10-12/24: BMT HV S2 [L4, L1] & S3 L5 strip frequent trips: The HV, Vset, was lowered by 10 V until it calmed down. If the problem persists, reduce the HV VSet value by an increment of 10 V after clicking the "Expert" button. Then, make a logbook entry and CC MVT/SVT/MM experts on it.
- If FMT gas errors appear, please follow the instructions in [4]
CND
- CAMAC crate alarm:
- • CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, which can be done via the alarm handler.
- • After reboot, the CFD thresholds need to be set by running a script; see page 12 in the CND manual at the "General" tab: https://clasweb.jlab.org/wiki/images/9/97/Ops_manual_cnd.pdf
DAQ
- Some ROCs keep printing error messages while functioning properly; please see their list in this logbook entry # 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!
- NEW STANDARD end and start of the run: End run, Cancel, Reset, Download, Prestart, Go. This will ensure proper compression of the FADCs and, therefore, a smaller data rate.
- ROC reboot instructions:
- • To reboot, i.e., adcecal1, or any noted ROC that became busy, type on a clasrun terminal: clasrun> roc_reboot adcecal1
- • To check that the crate is back alive, type:clasrun> ping adcecal1
- • The ping will start to answer as soon as the crate communicates again, then press Ctrl+C to exit ping.
DC
- Make sure to log every DC trip in the shift summary. Make sure to list WHERE and why, possibly, the trip occurred.
ECAL/PCAL
- "ECAL_SEC6_UO26 Noisy" https://logbooks.jlab.org/entry/4241957
- "PCAL_HV_SEC2_U25 turned off" https://logbooks.jlab.org/entry/4247187, https://logbooks.jlab.org/entry/4247400
FTOF
- 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.
- "FTOF HV Adjustment - S5 P2 2R" https://logbooks.jlab.org/entry/4249754
RICH
- Known problematic PMTs and tile:
- - You don't need to report about it.
- - PMT 2 (sector 1) and PMT 92 (sector 4) are not completely dead and may be visible depending on statistics.
- - Problematic tiles and PMTs:
- • Sector 1 Tile 21 dead (PMT 55,56,57)
- • Sector 1 Tile 1 PMT 2
- • Sector 4 Tile 34 PMT 92
Beam Restoration
- Study the manual: Establishing Physics-Quality Beam. If you do not feel confident doing this alone, contact the Beamline Expert.
- Find all Reference values on the CH whiteboard and the Short Term Schedule tab.
Restoring Beam after Short Downtime
- 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
- • beam steering or orbit change
- • change in beam current, e.g., after a target change
- • If BPM 2C24A and 2H01 positions are off (not within +/-0.1 mm), ask MCC to bring them to the reference values
Beam Tuning to Tagger Yoke Dump
- Study the manual: Establishing Physics-Quality Beam.
- Contact Eugene Pasyuk if issues arise.
- Ask MCC to energize the tagger magnet
- • blank collimator
- • beam type "Photon"
- All CLAS12 detectors HV off (BMT HV in safe mode)
- Ask MCC to mask the beam halo counters (FSDs: Upstream, Midstream, Downstream, BOM)
- Ask MCC for 5 nA beam current and make sure the Orbit Locks are OFF;
- If necessary, ask MCC to bring the 2C21A and 2C24A beam positions to the Reference Values
- Take harp scans:
- • at Harp 2C21A (Upstream Right Counter)
- • at Tagger Harp 2C24A Upstream Right Counter)
- 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.
- Compare the results with the Harp Scan References
- The fit ranges might need to be adjusted manually to assess the fit results
- If good, log the new scan results.
Møller run
- Follow the standard procedure as described in the manual Performing Møller Runs.
- Contact Nathan Baltzell if issues arise
- A few points to note:
- • Request 20 nA , Orbit Locks should be off
- • The BPMs 2C21 and 2C24A may be out of range after the Møller configuration.
- • Keep running until the polarization uncertainty is < 1.5%
Beam Tuning to Faraday Cup
- Study the manual Establishing Physics-Quality Beam and consider the first steps mentioned therein.
- This is typically done after tuning to the tagger dump (and possibly taking a Moller run).
- All CLAS12 detectors HV OFF (MVT HV ON in SAFE Mode)
- Ask MCC to de-energize the tagger magnet
- • 20 mm collimator
- • beam type electron
- • beam blocker out
- If initial beam tune, the target should be "Empty"
- Ask MCC to unmask beam halos
- Set the halo counter FSD thresholds to 1 MHz and the integration time interval to 50 milliseconds
- Insert the Downstream Viewer, Chromax, in the beamline
- Ask MCC for 5 nA beam current
- If necessary, ask MCC to bring the beam positions at 2C24A and 2H01 to the Reference Values
- Take a harp scan at 2H01 (Midstream Left)
- 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.
- Compare the results with the Harp Scan References
- If good, log the new scan results.
- Once done and before resuming the production data-taking:
- • Retract the Downstream Viewer from the beamline
- • Put the FSDs thresholds and integration time to their reference values
- • Turn all detector HV ON, for MVT "HV ON - Full Voltage"
- • MCC might need to adjust the beam positions after going to the production beam current.
- Arrive at your shift in time for the shift change, 10-15 minutes before the start of your shift.
- • If it is your first shift or a shift after a long pause, do shadow an earlier shift for at least 4 hours to familiarize yourself with all shift duties and technicalities of the ongoing experiment.
- Follow the Short Term Schedule;
- • The RC must be notified before changing run conditions.
- Operate the Data Acquisition.
- Take action on and log alarms.
- Communicate with your co-shift person:
- • Remind them to read the tab 'Shift Worker'.
- • The shift worker should discuss an issue with the shift expert before making extra logbook entries.
- • During production, not in extended downtime, the shift expert should ensure the shift worker is filling their end-of-shift Checklist when the beam is ON, not in the period of beam trips.
- • Use the CS-Studio Logbook entry tool for all screenshots (but the strip charts)!
- • Note that the Logbook Entry tool defaults the entry in the HBRUN logbook. Other logbooks can be added or selected from the drop-down menu.
- Check for and read any comments made to log-book entries during your shift.
- Keep your shift summary up to date in HBLOG. Record all shift activities, issues, if any, and related communications with experts with details and/or reference to any associated logbook entries:
- - Refer to relevant logbook entries in the shift summary.
- - Include a list of runs taken during the shift with relevant run information;
- • See, for instance, this shift summary where all relevant run info, links, and shift activities are cited.
- Ensure that all MON12 monitoring plots are logged and checked against the reference plots for every single run; see the links under Monitoring tab;
- • Both, you and the shift worker should run MON12 and reset & check spectra frequently.
- If the worker shift is remote, maintain communication over Zoom.
- If you have any other questions or uncertainties about what to do, call the RC.
- 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
- New MVT LV Reboot Procedure can be found in the General Information tab.
- At the end of the shift, submit the strip charts to the logbook:
- - If they are not up already: (CS-Studio → Tools → Strip Charts → livePlot)
- - Right-click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters"
- - Choose a time-span width of 10 hours (right-click below x-axis)
- - To make a logbook entry:
- • Right-click within the grid of one of the charts, choose "Make Logbook Entry"
- • The title of the logbook entry can be changed, eg to Strip charts
- • Un-click ELOG, select HBLOG and click "Make Entry" to submit.
- Fill out BTA hourly;
- Accelerator beam time (do not change these values):
- • ABU: acceptable beam used
- • BANU: beam acceptable but not used (should be reflected in our PCC and UED)
- • BNA: beam not acceptable (e.g., tuning, drifting, not focused)
- • ACC: Accelerator Configuration Change (e.g., pass change)
- • OFF: Accelerator is down
- Experiment beam time (do change these values):
- • ER: Experiment ready (should be 60 minutes - PCC - UED)
- • PCC: Planned configuration change (when the beam is masked while radiators are moved, target change, DAQ (stopping/starting runs, tests, etc.)
- • UED: Unplanned experiment down (hardware failure, DAQ crashes, our problems, ...)
- • Exception: BANU, due to time spent on beam tuning and BPM checks after beam down, should be counted as ER on our side.
- Enter fields at the "Shift Information" tab.
- To send information to MCC, you must save at 7:00, 15:00, and 23:00. To see the save button, click 'edit all' or 'Edit CC Hours.'
- 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 time sheet up to 48 hours after completion.
- Come to your shift in time for the shift change, 10-15 minutes before the start of your shift;
- • If it is your first shift or a shift after a long pause, do shadow an earlier shift for at least 4 hours to familiarize yourself with all shift duties and technicalities of the ongoing experiment.
- 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.
- Use the CS-Studio Logbook entry tool for all screen shots, except the strip charts!
Frequently
- Reset and check MON12 histograms frequently, preferably each 1 h, during a run;
- • Note that some plots have radio buttons at the bottom to choose the sector. Remember to cycle through and check all sectors.
Once per run
- 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.
- Using the Logbook Entry tool, submit EPICS screenshots to the HBRUN logbook (one logbook entry) with beam ON:
- Beamline overview (remote shift: in VNC or Web Browser)
- DAQ status
- CLAS12 trigger rates
- Upload mon12 monitoring plots to the logbook with sufficient statistics and compare them to the reference and recent uploads (see Monitoring tab).
- At the end of the run:
- - Submit the strip charts to the logbook:
- • If they are not up already: (CS-Studio → Tools → Strip Charts → livePlot)
- • Right-click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters"
- • Choose a time-span width of 4 hours, compatible with the run duration (right-click below x-axis)
- • To make a logbook entry:
- • Right-click within the grid of one of the charts, choose "Make Logbook Entry"
- • The title of the logbook entry can be changed, eg to Strip charts
- • Un-click ELOG, select HBLOG, and click on "Make Entry" to submit
- - Upload the clas12online plots to the logbook.
- • The program can continue through a standard end/start of a run. However, after a DAQ restart, you must back out and restart clas12online.
- • If the DAQ has to be restarted, you can still make the upload before backing out.
Once per shift
- Fill the shift checklist;
- • During production, get relevant values from the epics screens Beamline Overview, CLAS12 DAQ Status and CLAS12 Trigger;
- • During extended downtime, get relevant values from the latest EPICS screenshots that you made during production
For Remote Shifts
- Please inform the PDL that your shifts will be remote. . Remote shifts are listed here
- You must test your setup, including ZOOM and VNC connections, at least 24 hours before your first shift!
- ♦ ZOOM for 24-7 communication with Counting House:
- • In a Web-browser: https://jlab-org.zoomgov.com/j/1618614939; Or in the ZOOM APP: Enter the meeting #: 1618614939, then
- - The required passcode can be obtained from this log entry
- • In a Web-browser: https://jlab-org.zoomgov.com/j/1618614939; Or in the ZOOM APP: Enter the meeting #: 1618614939, then
- Remind the expert in the counting house to restart their ZOOM, if necessary
- Remote VNC connection instructions: https://logbooks.jlab.org/entry/3906039:
- • 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 web pages.
- • All necessary applications should be available from the desktop menu (left/right click on the desktop)
- • EPICS GUIs should be accessed ONLY via the desktop menu or by running clascss-remote.
- • Some charts are also accessible via web browser: Upstream/Midstream Halo Counters, Downstream Halo Counters, Beam Currents, BPM Positions
- Check the upcoming shifts, and if necessary, coordinate with the PDL to contact shift takers about their training and site access status.
- Remote shifts are listed here.
- Backup shift personnel is listed here.
- Meeting ZOOM connections: see Important Links or Short Term Schedule tab
Daily
- 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.
- Update the run plan in the Short Term Schedule tab, as well as the whiteboard in CH, in coordination with the RG-E experiment Run Coordinators and communicate it to the shift crew.
- Log the RC Daily summary in the HBLOG.
- BTA time sheet: Make sure the "Beam Available Not Used" (BANU) time is accounted for as explained at the Shift Expert tab. The BTA information can be modified post-signature.
- • NOTE: "After 48 hours, you cannot modify a User signed timesheet unless you are the signer, Hall Manager, or Admin".
- Run the daily RC meetings in CH Room 200C and on ZOOM
- • Mo-Tu,Th-Fr at 13:00 ET in the Counting House Conference Room
- • Wednesdays at 3 PM, ZOOM only
- • Weekends upon agreement
- • Send a daily invitation for the RC meeting to mailing lists hallb, clas12_rge, clas_members.
- Connect to Zoom in CH Room 200C:
- • 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.
- • Once logged in, use the recommended Google Chrome to join the ZOOM meeting on the browser or use the ZOOM application.
- • Since the room doesn't have audio, don't connect with the computer audio, but Call the 1-833-xxx-xxxx number shown in the ZOOM session on the small Cisco answering device. Once prompted, enter the meeting ID followed by the participant ID displayed in the ZOOM session to join the meeting.
- • The room has a camera, which can be turned on via ZOOM.
Weekly
- MCC/OPS planning meeting, on Wednesdays at 13:30, MCC building.
- • Submit (save) the online form Run Coordinator Weekly Summary before the meeting and present the contents at the meeting.
- • The summary covers the data-taking status from 7 a.m. on the previous Wednesday to 7 a.m. on the current Wednesday.
- • Beam time accounting: Beam Time Manager; Physics Time Accounting
- • The total experiment data collected to date could be retrieved from the up-to-date Accumulated "Charge" or "Luminosity" depicted on the "RG-E 2024 Progress" plot. See the Monitoring tab
- Hall B meeting is on Mondays at 9 AM. Present your summary slides, which should be sent beforehand to the Hall B leader, Patrick Achenbach.
Webcams
|
EPICS |
Data Quality
|
Hall-B |
Accelerator |
ZOOM Meetings
|
|
|
