|
|
| Line 134: |
Line 134: |
| | | | |
| | |} | | |} |
| − |
| |
| − | <!--####################################### GENERAL INFORMATION #############################################-->
| |
| − | = General Information =
| |
| − |
| |
| − | 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 expert 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'''.
| |
| − | * 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.
| |
| − | * Reboot mvt1, mvt2, and mvt3 ROCS.
| |
| − | * Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go).
| |
| − | * '''If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert'''.
| |
| − |
| |
| − | === RICH issues ===
| |
| − | * 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'''
| |
| − | * 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 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 https://jlab-org.zoomgov.com/j/1618614939], included in "Remote Shifts" in tab "Shift Worker"
| |
| − | * 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 tab "Shift Worker"
| |
| − |
| |
| − | == '''Current Issues''' ==
| |
| − |
| |
| − | === 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 of 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]
| |
| − | * We have a '''new dome light switch outside of 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''' and the locks should generally be on ("Running").
| |
| − | ** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").
| |
| − | * 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=0V) - appears blue in MVT overview
| |
| − | * BMT HV S2 L6 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview
| |
| − |
| |
| − | === CND ===
| |
| − | * CAMAC crate alarm:
| |
| − | ** CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, 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 tab "General", 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 # [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.
| |
| − | * roc reboot instructions:
| |
| − | ** To reboot i.e. adcecal1, 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.
| |
| − |
| |
| − | === 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: [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.
| |
| − |
| |
| − | * Find all Reference values on the white board at tab Short_Term_Schedule
| |
| − |
| |
| − | === 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: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf 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 [https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf 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: [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.
| |
| − |
| |
| − | This is typically done after tuning to the tagger dump (and possibly taking a Moller run).
| |
| − |
| |
| − | * All CLAS12 detectors HV off (BMT HV in safe mode)
| |
| − |
| |
| − | * 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"
| |
| − | * 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.
| |
| − |
| |
| − |
| |
| − |
| |
| − | <!--####################################### GENERAL INFORMATION #############################################-->
| |
| − | = General Information =
| |
| − |
| |
| − | 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 expert 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'''.
| |
| − | * 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.
| |
| − | * Reboot mvt1, mvt2, and mvt3 ROCS.
| |
| − | * Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go).
| |
| − | * '''If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert'''.
| |
| − |
| |
| − | === RICH issues ===
| |
| − | * 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'''
| |
| − | * 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 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 https://jlab-org.zoomgov.com/j/1618614939], included in "Remote Shifts" in tab "Shift Worker"
| |
| − | * 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 tab "Shift Worker"
| |
| − |
| |
| − | == '''Current Issues''' ==
| |
| − |
| |
| − | === 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 of 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]
| |
| − | * We have a '''new dome light switch outside of 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''' and the locks should generally be on ("Running").
| |
| − | ** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").
| |
| − | * 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=0V) - appears blue in MVT overview
| |
| − | * BMT HV S2 L6 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview
| |
| − |
| |
| − | === CND ===
| |
| − | * CAMAC crate alarm:
| |
| − | ** CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, 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 tab "General", 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 # [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.
| |
| − | * roc reboot instructions:
| |
| − | ** To reboot i.e. adcecal1, 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.
| |
| − |
| |
| − | === 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: [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.
| |
| − |
| |
| − | * Find all Reference values on the white board at tab Short_Term_Schedule
| |
| − |
| |
| − | === 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: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf 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 [https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf 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: [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.
| |
| − |
| |
| − | This is typically done after tuning to the tagger dump (and possibly taking a Moller run).
| |
| − |
| |
| − | * All CLAS12 detectors HV off (BMT HV in safe mode)
| |
| − |
| |
| − | * 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"
| |
| − | * 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.
| |
| − |
| |
| − |
| |
| − |
| |
| − | <!--####################################### GENERAL INFORMATION #############################################-->
| |
| − | = General Information =
| |
| − |
| |
| − | 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 expert 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'''.
| |
| − | * 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.
| |
| − | * Reboot mvt1, mvt2, and mvt3 ROCS.
| |
| − | * Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go).
| |
| − | * '''If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert'''.
| |
| − |
| |
| − | === RICH issues ===
| |
| − | * 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'''
| |
| − | * 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 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 https://jlab-org.zoomgov.com/j/1618614939], included in "Remote Shifts" in tab "Shift Worker"
| |
| − | * 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 tab "Shift Worker"
| |
| − |
| |
| − | == '''Current Issues''' ==
| |
| − |
| |
| − | === 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 of 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]
| |
| − | * We have a '''new dome light switch outside of 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''' and the locks should generally be on ("Running").
| |
| − | ** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").
| |
| − | * 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=0V) - appears blue in MVT overview
| |
| − | * BMT HV S2 L6 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview
| |
| − |
| |
| − | === CND ===
| |
| − | * CAMAC crate alarm:
| |
| − | ** CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, 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 tab "General", 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 # [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.
| |
| − | * roc reboot instructions:
| |
| − | ** To reboot i.e. adcecal1, 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.
| |
| − |
| |
| − | === 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: [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.
| |
| − |
| |
| − | * Find all Reference values on the white board at tab Short_Term_Schedule
| |
| − |
| |
| − | === 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: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf 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 [https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf 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: [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.
| |
| − |
| |
| − | This is typically done after tuning to the tagger dump (and possibly taking a Moller run).
| |
| − |
| |
| − | * All CLAS12 detectors HV off (BMT HV in safe mode)
| |
| − |
| |
| − | * 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"
| |
| − | * 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.
| |
| − |
| |
| − |
| |
| − |
| |
| − | <!--####################################### GENERAL INFORMATION #############################################-->
| |
| − | = General Information =
| |
| − |
| |
| − | 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 expert 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'''.
| |
| − | * 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.
| |
| − | * Reboot mvt1, mvt2, and mvt3 ROCS.
| |
| − | * Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go).
| |
| − | * '''If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert'''.
| |
| − |
| |
| − | === RICH issues ===
| |
| − | * 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'''
| |
| − | * 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 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 https://jlab-org.zoomgov.com/j/1618614939], included in "Remote Shifts" in tab "Shift Worker"
| |
| − | * 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 tab "Shift Worker"
| |
| − |
| |
| − | == '''Current Issues''' ==
| |
| − |
| |
| − | === 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 of 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]
| |
| − | * We have a '''new dome light switch outside of 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''' and the locks should generally be on ("Running").
| |
| − | ** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").
| |
| − | * 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=0V) - appears blue in MVT overview
| |
| − | * BMT HV S2 L6 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview
| |
| − |
| |
| − | === CND ===
| |
| − | * CAMAC crate alarm:
| |
| − | ** CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, 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 tab "General", 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 # [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.
| |
| − | * roc reboot instructions:
| |
| − | ** To reboot i.e. adcecal1, 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.
| |
| − |
| |
| − | === 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: [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.
| |
| − |
| |
| − | * Find all Reference values on the white board at tab Short_Term_Schedule
| |
| − |
| |
| − | === 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: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf 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 [https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf 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: [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.
| |
| − |
| |
| − | This is typically done after tuning to the tagger dump (and possibly taking a Moller run).
| |
| − |
| |
| − | * All CLAS12 detectors HV off (BMT HV in safe mode)
| |
| − |
| |
| − | * 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"
| |
| − | * 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.
| |
| − |
| |
| − |
| |
| − |
| |
| − | <!--####################################### GENERAL INFORMATION #############################################-->
| |
| − | = General Information =
| |
| − |
| |
| − | 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 expert 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'''.
| |
| − | * 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.
| |
| − | * Reboot mvt1, mvt2, and mvt3 ROCS.
| |
| − | * Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go).
| |
| − | * '''If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert'''.
| |
| − |
| |
| − | === RICH issues ===
| |
| − | * 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'''
| |
| − | * 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 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 https://jlab-org.zoomgov.com/j/1618614939], included in "Remote Shifts" in tab "Shift Worker"
| |
| − | * 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 tab "Shift Worker"
| |
| − |
| |
| − | == '''Current Issues''' ==
| |
| − |
| |
| − | === 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 of 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]
| |
| − | * We have a '''new dome light switch outside of 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''' and the locks should generally be on ("Running").
| |
| − | ** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").
| |
| − | * 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=0V) - appears blue in MVT overview
| |
| − | * BMT HV S2 L6 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview
| |
| − |
| |
| − | === CND ===
| |
| − | * CAMAC crate alarm:
| |
| − | ** CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, 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 tab "General", 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 # [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.
| |
| − | * roc reboot instructions:
| |
| − | ** To reboot i.e. adcecal1, 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.
| |
| − |
| |
| − | === 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: [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.
| |
| − |
| |
| − | * Find all Reference values on the white board at tab Short_Term_Schedule
| |
| − |
| |
| − | === 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: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf 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 [https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf 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: [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.
| |
| − |
| |
| − | This is typically done after tuning to the tagger dump (and possibly taking a Moller run).
| |
| − |
| |
| − | * All CLAS12 detectors HV off (BMT HV in safe mode)
| |
| − |
| |
| − | * 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"
| |
| − | * 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.
| |
| − |
| |
| − |
| |
| − |
| |
| − | <!--####################################### GENERAL INFORMATION #############################################-->
| |
| − | = General Information =
| |
| − |
| |
| − | 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 expert 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'''.
| |
| − | * 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.
| |
| − | * Reboot mvt1, mvt2, and mvt3 ROCS.
| |
| − | * Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go).
| |
| − | * '''If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert'''.
| |
| − |
| |
| − | === RICH issues ===
| |
| − | * 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'''
| |
| − | * 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 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 https://jlab-org.zoomgov.com/j/1618614939], included in "Remote Shifts" in tab "Shift Worker"
| |
| − | * 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 tab "Shift Worker"
| |
| − |
| |
| − | == '''Current Issues''' ==
| |
| − |
| |
| − | === 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 of 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]
| |
| − | * We have a '''new dome light switch outside of 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''' and the locks should generally be on ("Running").
| |
| − | ** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").
| |
| − | * 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=0V) - appears blue in MVT overview
| |
| − | * BMT HV S2 L6 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview
| |
| − |
| |
| − | === CND ===
| |
| − | * CAMAC crate alarm:
| |
| − | ** CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, 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 tab "General", 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 # [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.
| |
| − | * roc reboot instructions:
| |
| − | ** To reboot i.e. adcecal1, 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.
| |
| − |
| |
| − | === 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: [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.
| |
| − |
| |
| − | * Find all Reference values on the white board at tab Short_Term_Schedule
| |
| − |
| |
| − | === 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: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf 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 [https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf 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: [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.
| |
| − |
| |
| − | This is typically done after tuning to the tagger dump (and possibly taking a Moller run).
| |
| − |
| |
| − | * All CLAS12 detectors HV off (BMT HV in safe mode)
| |
| − |
| |
| − | * 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"
| |
| − | * 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.
| |
| − |
| |
| − |
| |
| − |
| |
| − | <!--####################################### GENERAL INFORMATION #############################################-->
| |
| − | = General Information =
| |
| − |
| |
| − | 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 expert 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'''.
| |
| − | * 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.
| |
| − | * Reboot mvt1, mvt2, and mvt3 ROCS.
| |
| − | * Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go).
| |
| − | * '''If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert'''.
| |
| − |
| |
| − | === RICH issues ===
| |
| − | * 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'''
| |
| − | * 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 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 https://jlab-org.zoomgov.com/j/1618614939], included in "Remote Shifts" in tab "Shift Worker"
| |
| − | * 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 tab "Shift Worker"
| |
| − |
| |
| − | == '''Current Issues''' ==
| |
| − |
| |
| − | === 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 of 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]
| |
| − | * We have a '''new dome light switch outside of 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''' and the locks should generally be on ("Running").
| |
| − | ** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").
| |
| − | * 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=0V) - appears blue in MVT overview
| |
| − | * BMT HV S2 L6 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview
| |
| − |
| |
| − | === CND ===
| |
| − | * CAMAC crate alarm:
| |
| − | ** CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, 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 tab "General", 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 # [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.
| |
| − | * roc reboot instructions:
| |
| − | ** To reboot i.e. adcecal1, 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.
| |
| − |
| |
| − | === 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: [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.
| |
| − |
| |
| − | * Find all Reference values on the white board at tab Short_Term_Schedule
| |
| − |
| |
| − | === 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: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf 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 [https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf 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: [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.
| |
| − |
| |
| − | This is typically done after tuning to the tagger dump (and possibly taking a Moller run).
| |
| − |
| |
| − | * All CLAS12 detectors HV off (BMT HV in safe mode)
| |
| − |
| |
| − | * 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"
| |
| − | * 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.
| |
| − |
| |
| − |
| |
| − |
| |
| − | <!--####################################### GENERAL INFORMATION #############################################-->
| |
| − | = General Information =
| |
| − |
| |
| − | 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 expert 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'''.
| |
| − | * 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.
| |
| − | * Reboot mvt1, mvt2, and mvt3 ROCS.
| |
| − | * Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go).
| |
| − | * '''If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert'''.
| |
| − |
| |
| − | === RICH issues ===
| |
| − | * 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'''
| |
| − | * 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 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 https://jlab-org.zoomgov.com/j/1618614939], included in "Remote Shifts" in tab "Shift Worker"
| |
| − | * 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 tab "Shift Worker"
| |
| − |
| |
| − | == '''Current Issues''' ==
| |
| − |
| |
| − | === 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 of 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]
| |
| − | * We have a '''new dome light switch outside of 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''' and the locks should generally be on ("Running").
| |
| − | ** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").
| |
| − | * 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=0V) - appears blue in MVT overview
| |
| − | * BMT HV S2 L6 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview
| |
| − |
| |
| − | === CND ===
| |
| − | * CAMAC crate alarm:
| |
| − | ** CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, 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 tab "General", 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 # [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.
| |
| − | * roc reboot instructions:
| |
| − | ** To reboot i.e. adcecal1, 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.
| |
| − |
| |
| − | === 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: [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.
| |
| − |
| |
| − | * Find all Reference values on the white board at tab Short_Term_Schedule
| |
| − |
| |
| − | === 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: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf 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 [https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf 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: [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.
| |
| − |
| |
| − | This is typically done after tuning to the tagger dump (and possibly taking a Moller run).
| |
| − |
| |
| − | * All CLAS12 detectors HV off (BMT HV in safe mode)
| |
| − |
| |
| − | * 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"
| |
| − | * 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.
| |
| − |
| |
| − |
| |
| − |
| |
| − | <!--####################################### GENERAL INFORMATION #############################################-->
| |
| − | = General Information =
| |
| − |
| |
| − | 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 expert 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'''.
| |
| − | * 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.
| |
| − | * Reboot mvt1, mvt2, and mvt3 ROCS.
| |
| − | * Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go).
| |
| − | * '''If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert'''.
| |
| − |
| |
| − | === RICH issues ===
| |
| − | * 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'''
| |
| − | * 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 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 https://jlab-org.zoomgov.com/j/1618614939], included in "Remote Shifts" in tab "Shift Worker"
| |
| − | * 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 tab "Shift Worker"
| |
| − |
| |
| − | == '''Current Issues''' ==
| |
| − |
| |
| − | === 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 of 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]
| |
| − | * We have a '''new dome light switch outside of 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''' and the locks should generally be on ("Running").
| |
| − | ** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").
| |
| − | * 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=0V) - appears blue in MVT overview
| |
| − | * BMT HV S2 L6 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview
| |
| − |
| |
| − | === CND ===
| |
| − | * CAMAC crate alarm:
| |
| − | ** CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, 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 tab "General", 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 # [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.
| |
| − | * roc reboot instructions:
| |
| − | ** To reboot i.e. adcecal1, 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.
| |
| − |
| |
| − | === 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: [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.
| |
| − |
| |
| − | * Find all Reference values on the white board at tab Short_Term_Schedule
| |
| − |
| |
| − | === 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: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf 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 [https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf 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: [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.
| |
| − |
| |
| − | This is typically done after tuning to the tagger dump (and possibly taking a Moller run).
| |
| − |
| |
| − | * All CLAS12 detectors HV off (BMT HV in safe mode)
| |
| − |
| |
| − | * 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"
| |
| − | * 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.
| |
| − |
| |
| − |
| |
| − |
| |
| − | <!--####################################### GENERAL INFORMATION #############################################-->
| |
| − | = General Information =
| |
| − |
| |
| − | 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 expert 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'''.
| |
| − | * 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.
| |
| − | * Reboot mvt1, mvt2, and mvt3 ROCS.
| |
| − | * Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go).
| |
| − | * '''If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert'''.
| |
| − |
| |
| − | === RICH issues ===
| |
| − | * 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'''
| |
| − | * 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 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 https://jlab-org.zoomgov.com/j/1618614939], included in "Remote Shifts" in tab "Shift Worker"
| |
| − | * 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 tab "Shift Worker"
| |
| − |
| |
| − | == '''Current Issues''' ==
| |
| − |
| |
| − | === 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 of 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]
| |
| − | * We have a '''new dome light switch outside of 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''' and the locks should generally be on ("Running").
| |
| − | ** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").
| |
| − | * 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=0V) - appears blue in MVT overview
| |
| − | * BMT HV S2 L6 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview
| |
| − |
| |
| − | === CND ===
| |
| − | * CAMAC crate alarm:
| |
| − | ** CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, 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 tab "General", 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 # [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.
| |
| − | * roc reboot instructions:
| |
| − | ** To reboot i.e. adcecal1, 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.
| |
| − |
| |
| − | === 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: [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.
| |
| − |
| |
| − | * Find all Reference values on the white board at tab Short_Term_Schedule
| |
| − |
| |
| − | === 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: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf 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 [https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf 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: [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.
| |
| − |
| |
| − | This is typically done after tuning to the tagger dump (and possibly taking a Moller run).
| |
| − |
| |
| − | * All CLAS12 detectors HV off (BMT HV in safe mode)
| |
| − |
| |
| − | * 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"
| |
| − | * 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.
| |
| − |
| |
| − |
| |
| − |
| |
| − | = Phone Numbers =
| |
| − | <!--####################################### PHONE NUMBERS #############################################-->
| |
| − | {{PhoneNumbers}}
| |
| − | <!--- JUST MODIFY AND SAVE ANYTHING IN THIS COMMENT BLOCK TO FORCE A REFRESH OF THE PHONE NUMBERS TEMPLATE! -->
| |
| − |
| |
| − | <!--####################################### Short Term Schedule #############################################-->
| |
| − | = Short Term Schedule =
| |
| − |
| |
| − | '''[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>
| |
| − |
| |
| − | {{ShortTermSchedule-RGK}}
| |
| | | | |
| | <!--####################################### GENERAL INFORMATION #############################################--> | | <!--####################################### GENERAL INFORMATION #############################################--> |
