[Halla_running] [Revised Logentry] RC Update -- Thursday 05/29/25 [Meeting at 1:00pm]
pdbforce at jlab.org
pdbforce at jlab.org
Thu May 29 10:20:02 EDT 2025
Logentry Text:
--
<h2>Accelerator and Hall Status</h2>
<ul>
<li>Acc. beam study was successful and they were ready to send us beam early swing shift. </li>
<li>The spot size was reasonable to begin with (Y:~500um, X:659um). Per Jiwan's suggestion, requested MCC to reduce the X-width. In just first try, they reduced it to 597um! It looked great, so we moved on and rest of the beam checkout went smoothly. <a href="https://logbooks.jlab.org/entry/4385598">https://logbooks.jlab.org/entry/4385598</a></li>
<li>As we were ready to go to production, Don called to request an escorted access to reset the ECAL AC unit on the platform. With Don's instructions, the SL made the access and reset it successfully. The whole thing took about an hour. </li>
<li>Once that was taken care of, the DAQ started crashing for no obvious reason. Asar (GEM expert on call) was informed. He took a look but the GEMs looked fine. Alex was then informed and after some checks he realized the issue is related to HCAL. One FADC module went bad making the entire crate to crash! Around 10pm Alex made an escorted access to remove the faulty module. It fixed the issue with HCAL, but then we started having random issues with the GEM DAQ. After another couple of hours of debugging we could finally start the first production run 4173 around midnight. It is not really clear what fixed the issue but restarting everything from scratch seemed to have worked. Many thanks to Alex, Asar, and Ben! </li>
<li>Run 4173 crashed after a couple of hours and we lost about an hour to recover from that. Otherwise, it has been smooth running since the beginning of the owl shift. The beam has been very stable as well.</li>
<li>Many thanks to Kip and Mahmoud for stepping up to cover the owl shift! :) </li>
</ul>
<h2>Links to Shift Summaries</h2>
<ul>
<li>Day Shift (Wednesday) --- Acc. Beam Studies</li>
<li>Swing Shift (Wednesday) --- <a href="https://logbooks.jlab.org/entry/4385710">https://logbooks.jlab.org/entry/4385710</a> </li>
<li>Owl Shift (Thursday) --- <a href="https://logbooks.jlab.org/entry/4385898">https://logbooks.jlab.org/entry/4385898</a> </li>
</ul>
<h2>Accumulated Charge on LH2</h2>
<ul>
<li>Total Accumulated Charge at Kin3 so far: <b>8.17 C</b> </li>
<li>Total Accumulated Charge at Kin3 since Wednesday May 28 Swing: <b>0.42 C</b> </li>
</ul>
<h2>Run Plan for Today</h2>
<ul>
<li>Continue taking production data @ 18uA</li>
</ul>
<p><b>Let's meet today at the usual time (1:00 pm) to go over recent and future activities.</b><br>
Meeting details:<br>
Time: Daily at 1:00pm<br>
Location: Counting house conference room<br>
Join ZoomGov Meeting<br>
<a href="https://jlab-org.zoomgov.com/j/1616220064">https://jlab-org.zoomgov.com/j/1616220064</a><br>
Meeting ID: 161 622 0064<br>
Passcode: 314159<br>
</p>
---
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/4386051
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/halla_running/attachments/20250529/a54da67c/attachment.htm>
More information about the Halla_running
mailing list