<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<style type="text/css">
<!--
html{color:#555555;}body{line-height:1.5;font-family:'Trebuchet MS','Helvetica Neue',Arial,Helvetica,sans-serif;font-size:87.5%;}h1{font-size:1.6em;}h2.field-label{display:inline-block;font-size:1em;padding-right:5px;min-width:10em;margin:0.3em;}.problem_report{line-height:1.5;max-width:60em;}fieldset.problem_report.resolved
legend{background-image:url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAACXBIWXMAAA7EAAAOxAGVKw4bAAAAy0lEQVQ4jWP8//8/AyWAiZACd3f3/xYWFrht+f//P1a84t3e/0obff4rbfT5D1GGXR0LuoEr3+/7X3W4n2gvwA0gVSOKAcqbfPGGpImJCU45JgYGBoa7fpsZ22wLSbadgYGBgRE9GrF55Vf2BYbHjx8zYjWB0ljAcAGGExkZ/0MtwuoCggmJEBh4AzBS4pMnT/7fuXOH4dKlSwwnT56EiwcGBv43MDBgMDExYdDX12eQkZGBhAlyiC5YsOA/AwMDUXjLli3/iYoFQgAA+pSxZrXofD0AAAAASUVORK5CYII=);background-repeat:no-repeat;padding-left:18px;}fieldset.problem_report.needs_attention
legend{background-image:url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAABmJLR0QA/wD/AP+gvaeTAAAA9ElEQVR42sWTvUoDQRSFv9wMKWxSBVmzdhZJIwTWv9pyLWxTpbE1kBeJPoLxBazzBgGFKNqlHXAhsITUw1y7sMpmjER0YJrDPWcO556BPzhjYPJjlhfT82LUpxcK6Lo5U0JMgcu56tXy7BQajeBDpkAcAEdz1W6uyrLdYieK2DMmKCArcqczpH/ddc0msy+OkyQJC4h3N0ynx+Q5ALtUNs5q5U+8e+R+VPFi4kjk3NZqd++qUK+TZVnYwSfAOyvejeLXt/2qVG/dYoG1dqseBNco27bs/wXKWhIDB8AhcFLAH4Bn4Al4AUqT7RVC++6mv/JVPwDi3VGzomYvyAAAAABJRU5ErkJggg==);background-repeat:no-repeat;padding-left:18px;}.problem_report div.field-items{display:inline-block;}div.date-vitals p{font-size:87.5%;}a{text-decoration:none;}.Readme a:link,.Readme a:visited,.Readme
a:active{color:red;}
-->
</style>
</head>
<body id="mimemail-body" class="elog-logentry-notify">
<div id="center">
<div id="main">
<style>
<!--/*--><![CDATA[/* ><!--*/
div.field-vitals{
margin: 0.5em 0;
}
div.field-vitals .field-type-taxonomy-term-reference {
margin: 0.1em 0;
}
article.comment {
padding-left: 10px;
}
article.comment.odd {
background-color: #EEEEEE;
}
article.comment.even {
background-color: #DDDDDD;
}
div.node-content.logentry table{
width: auto;
border-collapse: collapse;
border-spacing: 0;
border-width: 1px;
}
div.node-content.logentry th{
border: inherit;
}
div.node-content.logentry blockquote{
background-color: #FFFFFF;
}
div.node-content.logentry caption{
font-size: 1em;
font-weight: normal;
}
table.field-vitals{
margin-top: 1em;
margin-bottom: 1em;
font-size: 87.5%;
}
table.field-vitals th{
vertical-align: middle;
text-align: left;
width: 15%;
padding: 0.1em;
}
table.field-vitals td{
vertical-align: middle;
text-align: left;
width: auto;
padding: 0.1em;
}
table.field-vitals td li {
margin-left: 0;
list-style-type: none;
list-style-image: none;
}
table.downtime {
width: 30em;
margin-bottom: 1em;
border: 1px black dotted;
}
table.downtime th {
text-align: center;
}
table.downtime td {
text-align: center;
}
tr.caption th {
border-bottom: none;
}
table.downtime tfoot{
background-color:#EEEEEE;
}
div.field-name-body{
margin: 1em 0;
font-size: 110%;
}
div.date-vitals p{
margin: .1em 0;
}
article div.ctools-collapsible-container{
margin-left: -5px;
clear: both;
}
#comment-form{
margin-left: 5px;
border: graytext outset medium;
-moz-border-radius: 15px;
border-radius: 15px;
padding: 1em;
}
div.comments-form-box {
margin-top: 2em;
margin-bottom: 5em;
}
h3.comment-title {
/* display: none; */
}
p.author-datetime{
font-weight: bold;
}
/*--><!]]>*/
</style><article id="node-1198511" class="node node-logentry contextual-links-region article ia-n clearfix" role="article"><header class="node-header"><h1 class="node-title">
<a href="https://logbooks.jlab.org/entry/4125474" rel="bookmark">RC Report 2-6-23</a>
</h1>
</header><div class="contextual-links-wrapper"><ul class="contextual-links"><li><a href="https://logbooks.jlab.org/entry/4125474/edit?destination=email/send">Edit</a></li><li><a href="https://logbooks.jlab.org/entry/4125474/delete?destination=email/send">Delete</a></li></ul></div>
<div class="date-vitals">
<p class="author-datetime">
Lognumber <a href="https://logbooks.jlab.org/entry/4125474" class="lognumber" data-lognumber="4125474">4125474</a>. Submitted by <a href="https://logbooks.jlab.org/user/rmontgom">rmontgom</a> on <time datetime="2023-02-06T10:52:11-0500" pubdate="pubdate"><a href="https://logbooks.jlab.org/entries?start_date=1675695131&end_date=1675702331&book=HALOG">Mon, 02/06/2023 - 10:52</a></time>. </p>
<table class="field-vitals"><tr><th>Logbooks: </th><td><a href="https://logbooks.jlab.org/book/halog">HALOG</a></td></tr></table></div>
<div class="logentry node-content">
<p>Summary of last 24 hours follows.</p>
<p>Short story:<br />
Unfortunately since sending the RC report yesterday we have had mostly beam down time. The accelerator is currently down to diagnose a magnet issue for Hall D. We won't know how long the down will be today until they set eyes on the magnet and know what the issue is. After this they will try to bring beam up again. But it will go off again tomorrow during the day for RF recovery. Let me know if you want to access the Hall tomorrow during the day.</p>
<p>Long story (for anyone who wants more details):<br />
Shortly after the RC report yesterday the accelerator started having more issues and beam went down. Day shift was spent with ops investigating and trying to restore beam. Several items under investigation were RF instabilities at 1L12-3, BLM sensitivity limiting current to A and C, and BLM trips from steering in spreader/recombiners. Swing shift TO was covered by Provakar in the end (thank you for that!). On swing shift things started to look optimistic and we started beam recovery into the Hall at around 7pm. When we were ready to put beam on polhe3, unfortunately ops could then not ramp Hall A above 15uA, and had problems when trying to send currents to both A and C. The 4th and 5th pass separators then tripped. RF experts came in and solved the issue. Early on in owl shift it started to look optimistic again and we restored beam into the Hall at around 2am, although we were current limited to 25uA. After almost an hour beam went off again (2L23 tripped and 0l04 POFF optimization). Ops tried to restore beam, but we were unable to get beam on target again until we had a very short production run this morning at the start of day shift, before the accelerator came down.</p>
<p>The accelerator is currently down so that the north linac can be accessed to assess what is wrong with a magnet for Hall D as of ~8:30am today. They will not know how long the necessary repair will take. In the meantime optics experts are going to work with ops to discuss what is going on in the accelerator in general. It seems the machine has never fully recovered since a magnet problem early on in the owl shift on Saturday. Ops have been trying very hard to perform many diagnostics and restorations this weekend, and we are grateful for that. They are, however, still unaware of the main problem/solution. For Hall A the limit seems to be ion chamber trips, so it is assumed that somewhere scraping is happening and they need to find out where that is and if it is mechanical/electrical/optical. They are coming up with a plan to systematically address it.</p>
<p>Run Plan:<br />
Let's wait to hear how long the down for the Hall D magnet issue will be. Then ops will start to try beam restoration. If successful, hopefully we could get some beam before the RF recovery day tomorrow. If you need to access the Hall tomorrow during day shift whilst the RF recovery is on-going let me know.</p>
<p>Special requests:<br />
Currently I'm aware of the following requests. Let me know of any other requests for Tuesday day.<br />
- SBS GEM cable fix<br />
- Target oven heater check.</p>
<p>Shift schedule:<br />
We are in very good shape until Feb 16th, except Fri 10th Feb Swing, which needs an SL. There are plenty of chances to sign up after Feb 16th!</p>
<p>Meeting:<br />
Let's meet at 3.30pm today (upstairs in the counting house) or on zoom:<br /><a href="https://jlab-org.zoomgov.com/j/1619032184?pwd=aWhTVWxya1ZZQzA1K2ZPSTd2ZX">https://jlab-org.zoomgov.com/j/1619032184?pwd=aWhTVWxya1ZZQzA1K2ZPSTd2ZX</a>...<br />
Meeting ID: 161 903 2184<br />
Passcode: 260715</p>
</div>
<div class="attachment-box">
</div>
</article> </div>
</div>
</body>
</html>