[Alert_collaboration] [New Logentry] RC Daily Summary

Tue May 13 11:10:02 EDT 2025

Logentry Text:
--
<div id="content"><h1 id="rc-summary-for-2025-05-13---tue-may-13">RC Summary for 2025-05-13 - Tue May 13</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="mon-may-12-dayhttpslogbooksjlaborgentry4373678-swinghttpslogbooksjlaborgentry4373938-–-tue-may-13-owlhttpslogbooksjlaborgentry4374188-day-ongoinghttpslogbooksjlaborgentry4374382">Mon May 12 <a href="https://logbooks.jlab.org/entry/4373678">DAY</a>, <a href="https://logbooks.jlab.org/entry/4373938">SWING</a> – Tue May 13 <a href="https://logbooks.jlab.org/entry/4374188">OWL</a>, <a href="https://logbooks.jlab.org/entry/4374382">DAY (ongoing)</a></h4>
<ul>
<li><strong>DAY</strong>: After initial DAQ issues, resumed stable <strong>production running on 4He</strong>, collecting good data.</li>
<li>Around 1pm yesterday, MCC took beam to perform RF separator bleed-through studies. These were part of ongoing efforts to resolve beam delivery issues when the horizontal RF separator is active. MCC isolated the problem to cavity 4, with no bleed-through observed when running cavities 1–3 only (supplemented with magnetic steering).</li>
<li>Beam delivery resumed using horizontal magnetic extraction (horizontal RF separator off).</li>
<li><strong>SWING & OWL</strong>: Continued production on 4He. Multiple DAQ and detector alarms (trigger bit, ATOF, RICH, DC dark current).<ul>
<li><strong>Lost contact with RCDB during the night</strong> - is this something we should be concerned about? Is there a fallback when this happens?</li></ul></li>
<li>Today during DAY, we conducted our own bleed-through studies (switched off Hall B laser):<ul>
<li>With Hall A at 10 µA and Hall B laser off, <strong>we observed 10–15 Hz (peaking up to 25Hz) in the BOM</strong> (mostly top right quadrant), compared to ~200 Hz during 325 nA production running.</li>
<li>Other halo counters showed minimal activity. See <a href="https://logbooks.jlab.org/entry/4374446">4374446</a>, <a href="https://logbooks.jlab.org/entry/4374449">4374449</a>, and <a href="https://logbooks.jlab.org/entry/4374468">4374468</a> for results.</li></ul></li>
<li>Beam went down around 10:00am for further studies on horizontal separator by MCC, should return late DAY or early SWING.</li>
<li><strong>Accelerator Plans:</strong> Tomorrow ~7am, beam will go down for Arc-A magnet flush, will take couple of hours. They will also do additional checks on the horizontal separator, but NOT a full maintenance day.</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>Beam is currently down to study issues with horizontal separator, should come back during DAY or early SWING.<ul>
<li>We will continue production on 4He until <strong>7:00am Wednesday</strong>.</li></ul></li>
<li>ALERT repairs: <strong>RadCon sweep and pre-job briefing at 7:00am.</strong></li>
<li>Begin ALERT repairs (ATOF, AHDC) immediately afterwards</li>
<li>Can use beam downtime to address Moller/EPICS and any additional checks</li>
</ul>
<h2 id="bta">BTA</h2>
<ul>
<li>341.2 ABU hours since April 5 → 341.2 / (68.5 × 24) = 20.1%</li>
<li>Day 38 of 137 scheduled: 38 / 137 = 27.7%</li>
<li>BANU: 1.8 (DAQ issues)</li>
</ul>
<h2 id="outstanding-major-tasks">Outstanding Major Tasks</h2>
<ul>
<li><strong>ALERT Repairs</strong> – Start Wednesday May 14:<ul>
<li>ATOF Module 7 (Whitney Armstrong)</li>
<li>AHDC wire repair (Raphael Dupre)</li>
<li>RadCon sweep and pre-job at 7:00am</li></ul></li>
<li>Investigate Moller/EPICS sync issues during downtime (Nathan?)</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>21792</strong> – 30.3M events – ended due to DAQ busy (DC11)</li>
<li><strong>21793</strong> – 77.0M events – stopped due to low trigger bit 1</li>
<li><del><strong>21794</strong></del> – ended early, no event count recorded – MCC took beam away</li>
<li><strong>21795</strong> – 15.6M events – ended due to beam instability</li>
<li><strong>21796</strong> – 3.7M events – ended due to ATOF trip</li>
<li><strong>21797</strong> – 60.9M events – ended due to trigger bit alarm</li>
<li><strong>21799</strong> – 14.0M events – ended due to recurring trigger bit alarms</li>
<li><strong>21800</strong> – 11.8M events – ended due to persistent DAQ issues</li>
<li><strong>21801</strong> – <strong>100.0M</strong> <strong>events</strong> – clean run, one DC dark current alarm resolved during run</li>
<li><strong>21803</strong> – 6.4M events – ended due to rich4 ROC busy (100%)</li>
<li><strong>21804</strong> – 31.6M events – ended due to DAQ trigger bit alarm</li>
<li><strong>21805</strong> – 10.2M events – ended due to RCDB/Hydra disconnect</li>
<li><strong><del>21806</del></strong> – event count not reported – ended during OWL due to system instability</li>
<li><strong>21807</strong> – <strong>106.3M</strong> <strong>events</strong> – completed during DAY shift, clean run</li>
</ul>
<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://logbooks.jlab.org/book/hblog">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/4374500
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/alert_collaboration/attachments/20250513/a0871d10/attachment.htm>