[clas_members] [New Logentry] RC Daily Summary

[sjjooste at jlab.org]

Logentry Text:
--
<div id="content"><h1 id="rc-summary-for-2025-05-14---wed-may-14">RC Summary for 2025-05-14 - Wed May 14</h1>
<p><strong>We will have the RC meeting at 11:30am EDT in the Counting House. <a href="https://jlab-org.zoomgov.com/j/1605705819#success">Zoom Link</a></strong></p>
<h2 id="recap-and-status">Recap and Status</h2>
<h4 id="tue-may-13-dayhttpslogbooksjlaborgentry4374382-swinghttpslogbooksjlaborgentry4374602-–-wed-may-14-owlhttpslogbooksjlaborgentry4374797">Tue May 13 <a href="https://logbooks.jlab.org/entry/4374382">DAY</a>, <a href="https://logbooks.jlab.org/entry/4374602">SWING</a> – Wed May 14 <a href="https://logbooks.jlab.org/entry/4374797">OWL</a></h4>
<ul>
<li>Collected good data on 4He during DAY using <strong>magnetic extraction</strong> (instead of horizontal separator) until ~10am, when beam was taken for MCC separator studies.<ul>
<li>Completed Hall A bleed-through tests and flushed the target prior to downtime.</li></ul></li>
<li><strong>SWING</strong>: MCC requested around 5pm to send microamp-level tune beam to the tagger dump as part of testing.<ul>
<li>We energized tagger magnet to prepare for this, which likely skewed MCC's halo rate measurements.</li>
<li>MCC claimed horizontal RF separation looked acceptable based on low BOM rates observed.</li></ul></li>
<li><strong>OWL</strong>: MCC attempted full beam restoration using the <strong>horizontal RF separator</strong>.<ul>
<li>Beam profiles were within expectations, but persistent <strong>high BOM rates</strong> prevented transition to physics running.</li>
<li>MCC decided around <strong>6:00am</strong> to switch back to magnetic steering, but aborted due to time constraints ahead of access</li></ul></li>
</ul>
<h2 id="alert-repairs">ALERT Repairs</h2>
<ul>
<li>Entered <strong>Restricted Access at 7:54am</strong>. AHDC gas and target were emptied by 7am.</li>
<li>ALERT experts will determine by ~1:00pm whether the broken wire can be removed from the upstream or downstream side.<ul>
<li><strong>Best case</strong>: reclose Hall by late today or early tomorrow</li>
<li><strong>Worst case</strong>: up to 3–4 days of downtime, possibly into next week</li>
<li>An update will be sent once the repair path is confirmed</li></ul></li>
</ul>
<h2 id="looking-forward">Looking Forward</h2>
<ul>
<li><strong>No tuning progress has been made in the past few days</strong>.</li>
<li>When beam returns, MCC will prioritize Hall D tuning as they can't address the beam quality issue with Hall B down;<ul>
<li><strong>We will likely come back with the same poor beam quality</strong> </li></ul></li>
</ul>
<h2 id="game-plan">Game Plan</h2>
<ul>
<li>Hall is in Restricted Access for ALERT repairs<ul>
<li>Continue monitoring repair progress and will button detector once work finished</li></ul></li>
<li>Use downtime to investigate Moller/EPICS sync and verify reference/FSD settings (Nathan)</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>
<h2 id="bta">BTA</h2>
<ul>
<li>ABU: 341.2 → 341.2 / (68.5 × 24) = 20.1%</li>
<li>Day 39 of 137 scheduled: 39 / 137 = 28.5%</li>
<li>BANU: 0.1 (DAQ)</li>
</ul>
<h2 id="outstanding-major-tasks">Outstanding Major Tasks</h2>
<ul>
<li>ALERT Repairs ongoing (see above</li>
<li>Faraday Cup vacuum remains elevated — to be addressed after run ends</li>
</ul>
<h2 id="run-summary">Run Summary</h2>
<ul>
<li><strong>21807</strong> – 106.3M events – completed during Tue DAY before beam was taken</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/4375102
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/clas_members/attachments/20250514/feea1455/attachment.htm>