[Alert_collaboration] [New Logentry] RC Daily Summary

[sjjooste at jlab.org]

Logentry Text:
--
<div id="content"><h1 id="rc-summary-for-2025-05-11---sun-may-11">RC Summary for 2025-05-11 - Sun May 11</h1>
<p><strong>NOTE: NO RC MEETING TODAY</strong></p>
<h2 id="recap-and-status">Recap and Status</h2>
<h4 id="fri-may-10-dayhttpslogbooksjlaborgentry4372664--swinghttpslogbooksjlaborgentry4372850---sa-may-11-owlhttpslogbooksjlaborgentry4372977">Fri May 10 <a href="https://logbooks.jlab.org/entry/4372664">DAY</a> & <a href="https://logbooks.jlab.org/entry/4372850">SWING</a> - Sa May 11 <a href="https://logbooks.jlab.org/entry/4372977">OWL</a></h4>
<p>Accelerator has been trying to fix the optics/steering issues</p>
<ul>
<li>We put DAY worker on standby</li>
<li>No beam during any of the last 3 shifts</li>
</ul>
<h4 id="current-status">Current Status</h4>
<p>Experiment still in the state from the end of <a href="https://logbooks.jlab.org/entry/4372477">Sa May 9 OWL</a>:</p>
<ul>
<li>Halo FSDs at 1MHz/50ns (from aborted beam restoration)</li>
<li>Tagger energized from final beam restoration attempts</li>
<li>Target filled with He-4 at nominal pressure (needs to be emptied by expert during beam restoration)<br />
Riad suleiman from ACC (injector) asked if we have a faster way of looking at Halo Counter FSD signals as they are looking for a time structure to beam effects we are experiencing of the order of 10-50ms</li>
<li>Contacted Eugene, who suggested contacting Nathan as there is a tool available but it's currently likely not setup. Nathan is looking into it</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><ul>
<li>Do full beam restoration procedure (without Moller) once accelerator is ready to send beam</li>
<li>Monitor BOM scalers closely</li></ul></li>
<li>Production runs with He-4 until Wednesday, aim for 100M events<ul>
<li>Perform Hall A bleed-through test for ~5 minutes once Hall A is in stable running conditions with 20µA beam</li></ul></li>
<li>Wednesday start ALERT repairs during the Maintenance</li>
</ul>
<h2 id="bta">BTA</h2>
<ul>
<li>327.1 ABU hours since April 5th. 327.1/(68.5 x 24) = 19.9%</li>
<li>We are on day 36 of 137 scheduled days: 35/137 = 26.2%</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 to be monitored, to be fixed after end-of-run</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> (no RC meeting Sa-Su)</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/4373099
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/alert_collaboration/attachments/20250511/1a0fe76a/attachment-0001.htm>