<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-866866" 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/3793897" rel="bookmark">RC Update Friday Feb 28</a>
</h1>
</header><div class="contextual-links-wrapper"><ul class="contextual-links"><li><a href="https://logbooks.jlab.org/entry/3793897/edit?destination=email/send">Edit</a></li><li><a href="https://logbooks.jlab.org/entry/3793897/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/3793897" class="lognumber" data-lognumber="3793897">3793897</a>. Submitted by <a href="https://logbooks.jlab.org/user/brads">brads</a> on <time datetime="2020-02-28T13:26:50-0500" pubdate="pubdate"><a href="https://logbooks.jlab.org/entries?start_date=1582910810&end_date=1582918010&book=HCLOG">Fri, 02/28/2020 - 13:26</a></time>. </p>
<table class="field-vitals"><tr><th>Logbooks: </th><td><a href="https://logbooks.jlab.org/book/hclog">HCLOG</a></td></tr></table></div>
<div class="logentry node-content">
<p><strong><a class="new" title="RC Meeting and Run Plan, Friday, February 28th 2020 (page does not exist)" href="https://hallcweb.jlab.org/wiki/index.php?title=RC_Meeting_and_Run_Plan,_Friday,_February_28th_2020&action=edit&redlink=1">RC Meeting and Run Plan, Friday, February 28th 2020</a></strong></p><p><strong>RC Daily Meetings are at 4:15 PM, 2nd floor Counting House Meeting Room </strong> <a class="external text" href="https://bluejeans.com/861439920" rel="nofollow">Bluejeans Connection</a></p><p><strong> Friday 28th Feb. 2020. </strong></p><h1><span id="General_updates" class="mw-headline">General updates</span></h1><ul><li>Problems with 1L07, 1L17 throughout day shift (trippy beam, made Moller difficult, etc)</li><li>Lost beam mid-Swing and had extended down through OWL (issues in the NL, same cavities)<ul><li><a class="external free" href="https://cebaf.jlab.org/dtm/open-events?event_id=6195" rel="nofollow">https://cebaf.jlab.org/dtm/open-events?event_id=6195</a></li><li>Found that 1L20 had been misconfigured a day or two ago and was 145deg out of phase, now corrected</li><li>Issues with 1L07-7 and 1L07-8 looked pretty grim in late swing, but seem to have been recoverable(?)</li></ul></li><li>Hall C target ion chamber tripped with no beam in the machine <a class="external autonumber" href="https://logbooks.jlab.org/entry/3793622" rel="nofollow">[1]</a></li><li>Moller results from Thursday (85.0%) <a class="external autonumber" href="https://logbooks.jlab.org/entry/3793398" rel="nofollow">[2]</a></li><li>MCC took a few hours this morning to install an 'Easy Button' software patch and to chase some of the issues from overnight<ul><li>We took an opportunistic access to take a look at a few items:<ul><li>Swap USB-ethernet bridge with our spare -- Done (an attempt to address the coil current readback issues w/ LabView)</li><li>Looked at NMR and EPR hardware connections/settings (<a class="external free" href="https://logbooks.jlab.org/entry/3793821" rel="nofollow">https://logbooks.jlab.org/entry/3793821</a>)<ul><li>Found and corrected an internal vs. external trigger source setting switch with the EPR setup</li><li>This will also help (maybe solve?) the issue with the transverse NMR readback issues <a class="external autonumber" href="https://logbooks.jlab.org/entry/3793881" rel="nofollow">[3]</a></li><li>No 'smoking gun' found that could explain the large polarization drop on 2/24 though</li></ul></li></ul></li></ul></li></ul><h2><span id="Notes_for_the_Future" class="mw-headline">Notes for the Future</span></h2><ul><li>Beam studies to understand what is going on with the machine are planned for Tuesday DAY shift<ul><li>Details being worked out, but it'll be a full 7--8 hour down (for us)</li><li>EPR and pNMR measurements/work are planned during this downtime</li><li>There are portions of the Beam Studies program that would involve beam delivery into Hall C (no target), so limited opportunity for Access only</li></ul></li><li>Injector spot move has been pushed off for at least another week (2--3 hour down)<ul><li>Not much beam over the last several days...</li><li>Hope is to push it off to the Hall C down that starts March 13, and then just do a reactivation that would carry us through May 6<ul><li>Not sure how it will work out, but goal will be to minimized downs and maximize integrated current to Hall(s)</li></ul></li></ul></li></ul><ul><li>1 hour run with target out for measure of the background just from the beryllium windows (<em>Filler</em> for next spin-up)</li></ul><ul><li><strong>Target coil rotation planned for March 13--20</strong><ul><li>Nominal 1-week downtime in Hall C to rotate target coils, install new cell, and transition to d2n program</li><li>Status Update for target cell <em>Austin</em>:<ul><li>Wall and window thicknesses done</li><li>Only 'Reduced set' of density measurements available now, will continue measurements this week (issues with laser at UVa?)</li><li>It would be best for it to arrive at JLab on March 10 (at the latest) to allow locals to mount cell in oven plate before they get involved with target work in Hall.</li></ul></li><li>Lots of preplanning to be completed (RadCon, Techs, S&A, Target group, etc)</li><li>RW-II training for JP, Arun, Brad (Complete the training documentation and take the RW-II test if you haven't already done so)</li></ul></li></ul><h2><span id="Pending_problems" class="mw-headline">Pending problems</span></h2><ul><li>Beam energy shifts between ARC1:p and INJ:p impacted beam polarization to B/C? (Started 2/18 through 2/28) <a class="external autonumber" href="https://logbooks.jlab.org/entry/3793295" rel="nofollow">[4]</a><ul><li><strong>Resolved</strong> <a class="external autonumber" href="https://logbooks.jlab.org/entry/3793800" rel="nofollow">[5]</a></li></ul></li><li>3C20 BPM noise issue <a class="external free" href="https://logbooks.jlab.org/entry/3793274" rel="nofollow">https://logbooks.jlab.org/entry/3793274</a><ul><li><strong>Resolved</strong>: BPMs found to be in FFB mode, now back in normal mode (Jay)</li></ul></li><li>Persistent BLM & ion chamber trips<ul><li>General activation, weird BLM issues (<a class="external free" href="https://logbooks.jlab.org/entry/3792326" rel="nofollow">https://logbooks.jlab.org/entry/3792326</a>), Ad-hoc ion chamber threshold adjustments (<a class="external free" href="https://logbooks.jlab.org/entry/3792095" rel="nofollow">https://logbooks.jlab.org/entry/3792095</a>)</li><li><strong>NOTE</strong>: Shift crew should <em>NOT</em> give authorization to MCC change ion chamber thresholds. If they ask, tell Operator to contact an appropriate expert. Make a log entry if trips persist, or call the RC if it becomes severe (for example, >20 trips/hour is getting intolerable)</li></ul></li></ul><h2><span id="Fixed_problems" class="mw-headline"><br /></span></h2> </div>
<div class="attachment-box">
</div>
</article> </div>
</div>
</body>
</html>