[Alert_collaboration] [Revised Logentry] RC Daily Summary

[sjjooste at jlab.org]

Logentry Text:
--
<div id="content"><h1 id="rc-summary-for-2025-05-08---thu-may-8">RC Summary for 2025-05-08 - Thu May 8</h1>
<p><strong>NOTICE: NO RC Meeting today due to conflict with the Software meeting; status update during ALERT meeting</strong></p>
<h2 id="recap-and-status">Recap and Status</h2>
<ul>
<li>Wed May 7 MCC Meeting<ul>
<li>Unable to deliver high-current beam to Hall A due to optics issues</li>
<li>Optics issues likely due to mistuning in injector causing a mismatch between the injector and NL</li>
<li>Best course of action is to re-tune the injector, and then retune the entire machine. This will take a while (at least a day), but is absolutely required to provide high-current beam to Hall A. This should also address the beam quality issues we have been seeing in B.</li>
<li>Hall C will start powering up on Thursday morning, and will be ready for beam in the weekend</li>
<li>Full retune is meant to prepare machine for proper 4-hall operation</li></ul></li>
<li>Wed DAY<ul>
<li>No beam (maintenance day)</li>
<li>Shift worker relieved from duty</li>
<li>Hall B in Controlled Access<ul>
<li>Misc. minor maintenance tasks, all completed within DAY</li></ul></li>
<li>Issues: N/A</li></ul></li>
<li>Wed SWING<ul>
<li>No beam (maintenance day / machine retune)</li>
<li>Shift worker on standby</li>
<li>Hall B in Controlled Access</li>
<li>Issues:<ul>
<li>Hall B Temperature - temperature shot up to very high values starting 10:30pm. Issue was traced to a problem with chiller water pump #2, which was brought back online. Hall temperatures started dropping again after this fix, and returned to nominal by ~1am.<ul>
<li>Original issue: <a href="https://logbooks.jlab.org/entry/4371132">https://logbooks.jlab.org/entry/4371132</a></li>
<li>Denny & Facilities looking into the issue: <a href="https://logbooks.jlab.org/entry/4371135">https://logbooks.jlab.org/entry/4371135</a> and <a href="https://logbooks.jlab.org/entry/4371138">https://logbooks.jlab.org/entry/4371138</a></li>
<li>Chiller restarted: <a href="https://logbooks.jlab.org/entry/4371158">https://logbooks.jlab.org/entry/4371158</a></li></ul></li>
<li>Torus strain gauge alarm started going off around 11:30pm (B_TORUS:FOR:HB_DS_S1_VS:SG817D1HB4:Force), and engineering-on-call was contacted by the shift crew. The strain gauge values were found to be 100% correlated with the Hall temperature. Once the chiller issues were addressed the strain gauge values also returned to nominal. The one offending gauge was flirting with the alarm threshold for about 1 hour<ul>
<li>Original issue and diagnosis: <a href="https://logbooks.jlab.org/entry/4371159">https://logbooks.jlab.org/entry/4371159</a> and <a href="https://logbooks.jlab.org/entry/4371160">https://logbooks.jlab.org/entry/4371160</a></li>
<li>Strain gauge back down to nominal values: <a href="https://logbooks.jlab.org/entry/4371265">https://logbooks.jlab.org/entry/4371265</a></li></ul></li></ul></li></ul></li>
<li>Thu OWL<ul>
<li>No beam (machine retune)</li>
<li>Shift worker on standby</li>
<li>Hall B in Controlled Access</li>
<li>Issues:<ul>
<li>Resolution of issues from SWING (see above)</li></ul></li></ul></li>
<li>Thu start of DAY:<ul>
<li>MCC Retuned most of the machine smoothly, and was able to match the INJ to the NL.</li>
<li>Retune efforts smoothly reached 9R by late OWL, but backtracked to 7L at start of DAY to fix a small dispersion issue</li>
<li>Folks seemed optimistic machine was back to nominal performance</li>
<li>Expect tune beam to Hall A no earlier than noon.<ul>
<li>This means tune beam to Hall B no earlier than early afternoon<ul>
<li>Shift worker on standby until noon</li></ul></li>
<li>Should prepare for physics beam during SWING</li></ul></li></ul></li>
</ul>
<h2 id="game-plan">Game Plan</h2>
<ul>
<li><a href="https://wiki.jlab.org/clas12-run/index.php/Run_Group_L#tab=Short_Term_Schedule">Short Term Schedule</a></li>
<li>late DAY or early SWING: Earliest possibility to get tune beam in Hall B early afternoon<ul>
<li>DAY worker on standby until 12pm</li>
<li>Execute <a href="https://wiki.jlab.org/clas12-run/index.php/Run_Group_L#Beam_Restoration">full beam restoration procedure</a><ul>
<li>Beam to tagger yolk<ul>
<li>Target expert will empty the target in parallel</li></ul></li>
<li>Moller runs with both Helmholtz polarities</li>
<li>Beam tuning to Faraday Cup</li>
<li>Once done, target expert will fill the target with He-4</li></ul></li>
<li>Production runs with He-4, aim for 100M events</li>
<li>Perform Hall A bleed-through test for ~5minutes during Thu SWING or Fri DAY</li>
<li>Keep running He-4 until Wednesday shutdown</li></ul></li>
</ul>
<h2 id="bta">BTA</h2>
<ul>
<li>318.7 ABU hours since April 5th. 318.7/(68.5 x 24) = 19.4%</li>
<li>We are on day 33 of 137 scheduled days: 33/137 = 24.1%</li>
<li>BANU: 0 (no beam)</li>
</ul>
<h2 id="outstanding-major-tasks">Outstanding Major Tasks</h2>
<ul>
<li>Repairs planned for Wednesday, May 14th:<ul>
<li>ATOF module 7 (Whitney Armstrong)</li>
<li>AHDC wire repair (Raphael Dupre)</li>
<li>Draft of repair plans is available to all relevant people to make sure the repairs follow proper procedures and to ensure smooth execution and minimal downtime.</li></ul></li>
<li>Faraday Cup Vacuum (TBD)</li>
</ul>
<h2 id="run-summary">Run Summary</h2>
<p>N/A (no beam)</p>
<h2 id="links">Links</h2>
<ul>
<li><a href="https://jlab-org.zoomgov.com/j/1605705819#success">RC Meeting Zoom Link</a></li>
<li><a href="https://wiki.jlab.org/clas12-run/index.php/Run_Group_L">ALERT/RG-L Wiki</a></li>
<li><a href="https://wiki.jlab.org/clas12-run/index.php/Run_Group_L#:~:text=General-,Logbook,-Shift%20Schedule">Hall B Logbook</a></li>
<li><a href="https://wiki.jlab.org/clas12-run/index.php/Run_Group_L#tab=Short_Term_Schedule">Short Term Schedule</a></li>
</ul></div>

---

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/4371397
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/alert_collaboration/attachments/20250508/ff2ac9a9/attachment.htm>