[Halla_running] [New Logentry] RC Report for 24-Jun-2025

covrig at jlab.org covrig at jlab.org
Tue Jun 24 11:30:02 EDT 2025


Logentry Text:
--
Key updates for the past 24h (Mon Day+Swing and Tue Owl):
 - 16.2h actual beam delivery on target. The beam was down for almost 8h with major culprits NL dropping to restricted (https://logbooks.jlab.org/entry/4403924) and cooling water chillers (https://logbooks.jlab.org/entry/4404500)
 - On our side we were down for 3.6h during beam delivery, which accounts for 22.2% of wasted beam time. Most of the downtime happened, again, during Owl, 2.2h, and during the first half of Owl, when beam was available.
 - Tomorrow Day will be beam studies 7-9am, then RF recovery until mid afternoon with beam recovery after. Access to the Hall can be scheduled after 9am tomorrow. We plan to go to CA.
 - Thu Day there are plans for beam studies during beam delivery to test two settings of the Wien filter (for MOLLER). The Halls are "required" to take data during this time, maybe tag it, and report about the effects (if any). MCC will announce when the Wien tests will start and stop, to give Halls time to prepare for daq.
 - DAQ on-call until Jul 10: primary C. H. Leung (217-693-1360), secondary Chandan (757-342-4035).

 - Total Accumulated Charge at Kin3 so far: 31.61 C (Goal: 100 C)
 - Total charge delivered on target since Jun 18 noon: 9.31 C
 - Total Accumulated Charge from the run list at Kin3 since June 18 noon: 6.61 C
 - Charge acquisition efficiency 71% (from the plot attached)

Run plan: Continue production on the 30 cm LH2 target cell (loop 1) at 22 µA and also on wiki: https://sbs.jlab.org/wiki/index.php/RC_meeting_and_Run_Plan,_Tuesday,_June_24th#Current_Issues

Current Issues:
 - DAQ crashes: the last 24h we wasted 3.6h due to them or 22.2% of actual beam delivery.
 - Online zero suppression performance (common-mode min values for online zero suppression were changed to zero for the first iteration of averaging until we are ready to deploy ROI readout and histogramming firmware).
 - HCAL calibration/trigger efficiency, almost complete, still waiting on replays to finish.
 - Andrew pointed out that the sbb magnet current recorded in the run list changed on Jun 13 from 1762 A to 1757 A. There are two epics for the magnet's current, the setpoint (MSUPERBIGBITE) and the readback (MSUPERBIGBITEM). The current in the magnet, according to Ellen, is the readback. Both epics have essentially the same reading during Jun 2025 (see attached plots). And to try to answer Andrew's question about the stability of the current in the magnet, as far as epics recording goes, it seems to be at the level of about 80ppm. I asked the SL to correct the run list to show the readback values for sbb for the entire run list. There was also a correction to make to date, most of the 24h of 14-Jun were recorded as 13-Jun. 

Shift summaries:
23-Jun-2025 D https://logbooks.jlab.org/entry/4403887
23-Jun-2025 S https://logbooks.jlab.org/entry/4404134
24-Jun-2025 O https://logbooks.jlab.org/entry/4404338

Shift BTA:
23-Jun-2025 D https://logbooks.jlab.org/entry/4404116
23-Jun-2025 S https://logbooks.jlab.org/entry/4404327
24-Jun-2025 O https://logbooks.jlab.org/entry/4404543 (this one may be wrong, it seems that the TO recorded BANU as BNA)

We will have our daily RC meeting at 1pm in the conference room on the second floor of the CH and on zoom. It seems that the currently going JLUO has a lunch break until 14:00, so it should not affect our RC meet.
Zoom info:
Join ZoomGov Meeting
https://jlab-org.zoomgov.com/j/1616220064
Meeting ID: 161 622 0064
Passcode: 314159


---

This is a plain text email for clients that cannot display HTML.  The full logentry can be found online at https://logbooks.jlab.org/entry/4404643
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/halla_running/attachments/20250624/c353f9f1/attachment.htm>


More information about the Halla_running mailing list