Recent Changes and Current Issues

Recent Changes

• NEW: when starting a new run after a successful end, do not go from Prestart, but Abort, Download, Prestart, and Go.
• Run #18740: Trigger bit 30 https://logbooks.jlab.org/entry/4218054

• To make a logbook entry of the strip charts, right-click somewhere on a blank area in any one of the charts. Un-click ELOG and select HBLOG and submit. The title of the logbook entry can be changed.

• Controlled Access to the Hall:

• After 50-60 nA beam current, we ask MCC to stop the beam down, wait for the beacon to stop flashing (15-20 minutes), and then do not need an escort to go in.

• After 95 nA beam current or a Moller run, the beacon will not stop flashing anytime soon, so we need escorted access, viz the ARM. In that case, we can keep the beam until the ARM arrives at the counting house.

• Target Change in the Hall: In case of questions from MCC about the necessary controlled access, refer to the logbook entry #: 4196113 for the access requirements. We do need escorted access after >=90nA (on the CuSn target).

• ZOOM:

• To keep the 24-7 ZOOM session running in the counting house, 1) click on https://jlab-org.zoomgov.com/j/1618614939, included on "Remote Shifts" under Shift Worker tab, 2) choose the option to "join from browser" and ignore all other messages to update the ZOOM APP in the pop-up windows, and 3) enter the passcode from the logbook entry in Shift Worker tab.

Current Issues

• Beamline:

• After the HWP change, check the SLM and FCUP charge asymmetry (Q-Asym on Beamline Overview) as the absolute values should be less than 0.1%. If they are out of range, contact the Beamline Expert.

• The beam position on BPM 2C21A is not essential during production; the beam orbit lock is on BPM 2H01. We want both, 2C24A and 2H01 to have our nominal beam positions.

• Currently, the Faraday Cup can not be used for the beam current or accumulated charge measurements as the vacuum is degraded after the ion pump failure.

• 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/FMT/SVT:

• If new hot channels appear, call the MVT/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 trip and sector/layer in the shift summary. If the same channel trips frequently, ask the expert on call for guidance.

• BMT S1L5 strip is OFF

• Since of 2023-11-15 (maintenance day) BMT S2L5 strip has been turned back on

• DAQ:

• Some ROCs keep printing error messages while functioning properly; please see their list in this logbook entry # 4215299 to avoid unnecessary reboots since the printout in the ROC terminal won't change. The message will appear in the DAQ run control if they get disconnected!

• ECAL/PCAL:

• HV channel SEC3_V_E16 is OFF;

• PCAL HV_SEC3_V_E16 HV instability is reported at https://logbooks.jlab.org/entry/4215851;

• Hot PCAL U strip # 43 is observed in "adcEnergy" S3 spectra; see https://logbooks.jlab.org/entry/4215294.

• ECal S5 L8 PMT occasionally disappears for short periods. This behavior is common for both FADC and TDC; see https://logbooks.jlab.org/entry/4219587.

• 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 Channel Adjustment P2 S5" https://logbooks.jlab.org/entry/4220567

• IOC:

• IOCCLASSC8 is running at a disconnected state, please ignore it as that is a known issue; see a logbook entry 4221995.

• RICH:

• RICH Sector 1 has three missing tiles; this is known, and no action is required from the shifters.

• In case of a RICH issue (e.g, missing tiles), a screenshot of both scalers and temperatures should be logged in the RICH logbook before running the appropriate recovery.