[Halld] [New Logentry] RC Summary for past 24 hours (Oct-23)

[aasatury at jlab.org]

Logentry Text:
--
Over the past 24h we continued running on LHe target at 200nA CW beam, collected ~2.8B events at the time, it was pretty smooth day, no major issues either from our side nor from MCC side. 
At around 12:45pm (Saturday) we asked for Rapid Access to replace the broken FCal fADC {Slot 16 of the rocfcal10 (D2-7-TOP)}, which was happened during Saturday Midnight.
Around 5:30-6am we saw some beam instabilities (same from Hall-C), and this came from issues of 1L12 HV, at the moment MCC decided to go with this conditions, unless it will cause more problems.
   
=Sunday, October 23=
=== Past 24 hours ===
*~2.8B triggers collected on He target at 200nA CW since yesterday update (~11am)
*Asked MCC for Rapid Access to change the broken FCal fADC (~1hrs down time)
*Mostly beam was very stabile(Hall-A is not in business), except starting at ~5:30am-6:00am MCC is having some instabilities with 1L12 HV which is causing the instabilities for Halls D and C, but it is not a major issue for now, and MCC will continue beam delivery to halls

=== Shift Summary ===

*[https://logbooks.jlab.org/entry/4066120 Day Oct-22]
*[https://logbooks.jlab.org/entry/4066343 Swing Oct-22]
*[https://logbooks.jlab.org/entry/4066506 Owl Oct-22/23]
*[https://logbooks.jlab.org/entry/4066646 Early Riser Oct-23]
*[https://logbooks.jlab.org/entry/4066750 Day Oct-23]

=== Issues ===
*https://logbooks.jlab.org/entry/4066264 -> FCal fADC replacement 

=== Plan ===
*Continue taking production data at 200nA with FULL TGT.
 

---

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/4066754
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/halld/attachments/20221023/c8d148af/attachment.html>