[Alert_collaboration] [New Logentry] RC Summary July 17 - July 18 Owl

[hauenst at jlab.org]

Logentry Text:
--
<p>This is the RC summary for Day Shift July 17 to Owl shift July 18.</p><p>Yesterday during Day shift was maintenance day and several repairs in the hall happened. Unfortunately Cole could only replace one ECAL PMT due to obstructions in the way (<a href="https://logbooks.jlab.org/entry/4420145">https://logbooks.jlab.org/entry/4420145</a>). The repairs on the S4 RICH Crio was also not successful (<a href="https://logbooks.jlab.org/entry/4420154">https://logbooks.jlab.org/entry/4420154</a>). Troubleshooting of BAND TDC indicated more issues with might be due to a semi-broken second TDC since the same event which broke the other TDC (<a href="https://logbooks.jlab.org/entry/4420150">https://logbooks.jlab.org/entry/4420150</a>).</p><p>Beam came back around 10pm and we started beam checkout with some issues along the way. First we had troubles with a tagger door open fault (<a href="https://logbooks.jlab.org/entry/4420317">https://logbooks.jlab.org/entry/4420317</a>) which could
  be solv
 ed by Krister together with MCC (<a href="https://logbooks.jlab.org/entry/4420336">https://logbooks.jlab.org/entry/4420336</a>). Thank you to the shift crew which found out the last instances of this problem which allowed us to contact the right persons (<a href="https://logbooks.jlab.org/entry/4420320">https://logbooks.jlab.org/entry/4420320</a>). </p><p>Harp swipes with beam to tagger were good (<a href="https://logbooks.jlab.org/entry/4420355">https://logbooks.jlab.org/entry/4420355</a>, <a href="https://logbooks.jlab.org/entry/4420369">https://logbooks.jlab.org/entry/4420369</a>) and we entered Moller configuration. During Moller run we had to reboot IOC for halo counters, collimator motor and moller target motor.  Afterwards it was not possible to move collimator or moller target to required positions. It needed help from Nathan to reset the motor positions such that we could move back into the positions. Furthermore, there were issues with starting the M
 oller ru
 n. Finally, we could complete the run around 1:15am (<a href="https://logbooks.jlab.org/entry/4420467">https://logbooks.jlab.org/entry/4420467</a>) and obtained -86.38 +/- 1.23%.</p><p>Afterwards we set up beam to FC on empty target which worked pretty well. Harp scans are <a href="https://logbooks.jlab.org/entry/4420511">https://logbooks.jlab.org/entry/4420511</a> and <a href="https://logbooks.jlab.org/entry/4420526">https://logbooks.jlab.org/entry/4420526</a>. We refilled the target and switched on detectors. </p><p>Further issues arose from ALERT1 roc beeing 100% busy at nominal beam current (<a href="https://logbooks.jlab.org/entry/4420581">https://logbooks.jlab.org/entry/4420581</a>) due to either too high data rate from ALERT or too high trigger rate. Raphael took a new pedestal run (<a href="https://logbooks.jlab.org/entry/4420620">https://logbooks.jlab.org/entry/4420620</a>) but it didn't fix the problem since there was not too many differences in
  noise c
 omapred to before. So we went down to 200nA on deuterium to take data since this brought the rates down with a reasonable livetime.</p><p>Due to the decreased beam current, mon12 plots didn't work due to the beam current limits set when histograms are filled. This was fixed by me in the morning by reducing the minimum current requirement to 150nA (down from 250nA).  </p><p>As of writing this entry, we believe we found the culprit for the increased trigger/data rate which hinders to run at 325nA and we hope to fix it in the next hour.</p><p><span style="text-decoration: underline;">ABU for last 24h</span></p><p>- 4h of ABUs ~ 16.7% efficiency,</p><p>- Total ABUs since April 5th: 1081+4=1085 --> 1085 / (75.5 * 24) =  60% </p><p>- Day 103 of 151 scheduled: 104/151= 68.9%</p><p>- BANU: ~3h due to issues with motor movements, Starting Moller DAQ, filling target and general DAQ resets,</p><p><span style="text-decoration: underline;">Plan for today</span></p><ul><
 li>Fixin
 g DAQ rate to run at 325nA</li><li>Continue production data taking</li></ul><p><span style="text-decoration: underline;">RC Meeting:</span></p><p>We will meet as usual today at 11:30 (EST) in CH Room 200C and online via Zoom</p><p>Zoom meeting ID: 160 570 5819</p><p>Zoom Link: <a href="https://jlab-org.zoomgov.com/j/1605705819#success">Link</a></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/4420850
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/alert_collaboration/attachments/20250718/77a840e3/attachment.htm>