[Halla_running] [New Logentry] RC Daily Report Dec 9th, 2022

Fri Dec 9 10:50:01 EST 2022

Logentry Text:
--
<h1><span id="RC_Meeting_Information" class="mw-headline">RC Meeting Information</span></h1><table><tbody><tr><td style="text-align: right;">Current RC:</td><td> </td><td>Eric King [ericking (@jlab.org or @temple.edu)]</td></tr><tr><td style="text-align: right;">Time:</td><td> </td><td>Daily at 3:30PM</td></tr><tr><td style="text-align: right;">Location:</td><td> </td><td>Counting House Conference Room</td></tr></tbody></table><h4><span id="Remote_Connection_Details" class="mw-headline">Remote Connection Details</span></h4><ul><li>Join ZoomGov Meeting</li><li><a class="external free" href="https://jlab-org.zoomgov.com/j/1619032184?pwd=aWhTVWxya1ZZQzA1K2ZPSTd2ZX" rel="nofollow">https://jlab-org.zoomgov.com/j/1619032184?pwd=aWhTVWxya1ZZQzA1K2ZPSTd2ZX</a>...</li><li>Meeting ID: 161 903 2184</li><li>Passcode: 260715</li><li>Dial by your location</li><li>+1 669 254 5252 US (San Jose)</li><li>+1 646 828 7666 US (New York)</li><li>+1 551 285 1373 US</li><li>+1 669 21!
 6 1590 US (San Jose)</li><li>833 568 8864 US Toll-free</li><li>Find your local number: <a class="external free" href="https://jlab-org.zoomgov.com/u/acj3pTicMx" rel="nofollow">https://jlab-org.zoomgov.com/u/acj3pTicMx</a></li></ul><h1><span id="Shift_Schedule" class="mw-headline">Shift Schedule</span></h1><ul><li><a class="external text" href="https://misportal.jlab.org/mis/physics/shiftSchedule/?experimentRunId=SBS-GEn-2022" rel="nofollow">Link to Schedule</a></li></ul><h4><span id="This_RC_Week" class="mw-headline">This RC Week</span></h4><ul><li>Next empty shift is a <strong><span style="text-decoration: underline;"><span style="color: red;">Target Operator DAY shift on Sunday 12/11</span></span></strong>.</li></ul><h4><span id="Upcoming_RC_Week" class="mw-headline">Upcoming RC Week</span></h4><ul><li>There are two (2) other remaining shifts to be filled before winter shutdown; I'm sure Andrew would like them filled asap so he doesn't have to chase down any shift workers!
 .</li></ul><h1><span id="Accelerator_Status" class="mw-headlin!
 e">Accelerator Status</span></h1><ul><li>Everything appears to be running smoothly at the moment.</li><li>Hall C is down for about a week due to a vacuum break.</li></ul><h1><span id="Current_Status" class="mw-headline">Current Status</span></h1><p>We took data on 3-He during SWING with no huge disruptions. Data taking on OWL was interrupted by DAQ issues at around 2AM and 6AM. Møller measurement cancelled and returning to SBS prodcution. </p><h4><span id="M.C3.B8ller_Measurement" class="mw-headline">Møller Measurement</span></h4><p>Møller measurement was scheduled during Friday DAY. Target holding field magnet was warm and we backed out of the Møller configuration to return to SBS 3-He production.</p><h4><span id="Target_Polarization" class="mw-headline">Target Polarization</span></h4><p>Target polarization has been good. We look to be at the ~41% value suggested by Gordon</p><ul><li>7:20AM → 41.6% <a class="external text" href="https://logbooks.jlab.org/entry/409903!
 6" rel="nofollow">[4099036</a>]</li><li>3:00AM → 42.0% <a class="external text" href="https://logbooks.jlab.org/entry/4098948" rel="nofollow">[4098948</a>]</li><li>23:10PM → 41.4% <a class="external text" href="https://logbooks.jlab.org/entry/4098878" rel="nofollow">[4098878</a>]</li><li>17:10PM → 41.0% <a class="external text" href="https://logbooks.jlab.org/entry/4098761" rel="nofollow">[4098761</a>]</li><li>12:40PM → 40.7% <a class="external text" href="https://logbooks.jlab.org/entry/4098661" rel="nofollow">[4098661</a>]</li></ul><h4><span id="DAQ_ISSUES" class="mw-headline">DAQ ISSUES</span></h4><p>I would estimate that we lost 2.5-3.0 hours of data taking to DAQ issues. Shift crew should make an effort to document these issues clearly.</p><ul><li>(6:00PM) I received a phone call from Anu Thursday afternoon that they were having difficulties with the DAQ. This was ~45 minutes worth of time.<ul><li>I instructed Anu to contact Zeke who was also unable to diagnose!
  and remediate the problem.</li><li>I contacted Alexander who made his !
 way in to the Lab; before he arrived at the Lab the problem resolved itself and the diagnosis remains unclear. <a class="external text" href="https://logbooks.jlab.org/entry/4098814" rel="nofollow">[4098814</a>]</li></ul></li><li>(11:45PM) I talked to Nilanga when I came in for the crew switch around 11:45pm and he said that he had a minor problem with the DAQ around 11:15pm. This may be a more routine issue. He noted it in the shift log that Anu began <a class="external text" href="https://logbooks.jlab.org/entry/4098734" rel="nofollow">[4098734</a>]</li><li>(2:00AM) I received a call from the shift leader that they were having difficulty with the DAQ. There were warnings and errors about ROC1. I restarted the DAQ with no issues. <a class="external text" href="https://logbooks.jlab.org/entry/4098940" rel="nofollow">[4098940</a>]</li><li>(5:30AM) DAQ Problems re-erupted. <a class="external text" href="https://logbooks.jlab.org/entry/4098987" rel="nofollow">[4098987</a>] <a !
 class="external text" href="https://logbooks.jlab.org/entry/4098994" rel="nofollow">[4098994</a>] <a class="external text" href="https://logbooks.jlab.org/entry/4099003" rel="nofollow">[4099003</a>]<ul><li>Alexander was notified and got the DAQ working again with his HALOG entry at 6:20AM. <a class="external text" href="https://logbooks.jlab.org/entry/4099013" rel="nofollow">[4099013</a>] <a class="external text" href="https://logbooks.jlab.org/entry/4099023" rel="nofollow">[4099023</a>]</li></ul></li></ul><h1><span id="Issues_Resolved" class="mw-headline">Issues Resolved</span></h1><h1><span id="Issues_remaining" class="mw-headline">Issues remaining</span></h1><ul><li>BB GEM APV unreachable and cannot be repaired at this time.</li></ul><h1><span id="Short_Term_Run_Plan" class="mw-headline">Short Term Run Plan</span></h1><ul><li>Continue production run on He3 target, 36 uA</li><li>Use GEnII-noSBSGEMs DAQ config</li><li>Use ps3=0, ps5=6, others =-1</li><li>BBCal threshold at!
  -366 mV, HCal threshold at -19 mV</li><li>NMR measurement every 3 - 4 !
 hours, close to 4 hours is better</li></ul><h1><span id="Planned_Accesses_to_the_Hall" class="mw-headline">Planned Accesses to the Hall</span></h1><ul><li>I presume that repairs for the BB GEM APV will wait until shutdown.</li></ul><h1><span id="Special_Requests" class="mw-headline">Special Requests</span></h1><p><em><strong><span style="text-decoration: underline;">Please email me</span></strong></em> ericking (@jlab.org or @temple.edu) if there's something to be added.</p><ul><li>Gordon said that he would like to discuss with the other spokespersons an increase in the current being placed on the target, I informed him to start that discussion and keep me in the loop.</li></ul><h1><span id="Shutdown_Planning" class="mw-headline">Shutdown Planning</span></h1><ul><li>Arun has agreed that he will begin an email chain with RadCon regarding what materials are safe/unsafe in the hall.</li></ul><h1><span id="Notices_in_Effect_for_Shift_Crew" class="mw-headline">Notices in Effect !
 for Shift Crew</span></h1><ul><li>Power down SBS, BB, and Detector HV before making an access to the Hall</li></ul><h1><span id="Data_Collection_Status" class="mw-headline">Data Collection Status</span></h1><ul><li>75 out of 141 days (~53.2%)</li><li>(NEEDS TO BE UPDATED) Total uncorrected accumulated charge on He3: 47.020 C out of 232C (20.26%)<ul><li>2-Pass: 13.467 C</li><li>(NEEDS TO BE UPDATED) 3-Pass: 33.553 C (at end of OWL)</li></ul></li></ul><p> </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/4099117
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/halla_running/attachments/20221209/7ea06990/attachment.html>