<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-1020357" 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/3947336" rel="bookmark">RC Update -- Saturday Nov 20</a>
</h1>
</header><div class="contextual-links-wrapper"><ul class="contextual-links"><li><a href="https://logbooks.jlab.org/entry/3947336/edit?destination=email/send">Edit</a></li><li><a href="https://logbooks.jlab.org/entry/3947336/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/3947336" class="lognumber" data-lognumber="3947336">3947336</a>. Submitted by <a href="https://logbooks.jlab.org/user/brads">brads</a> on <time datetime="2021-11-20T18:03:18-0500" pubdate="pubdate"><a href="https://logbooks.jlab.org/entries?start_date=1637445798&end_date=1637452998&book=HALOG">Sat, 11/20/2021 - 18:03</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">
<h1><span id="Accelerator_and_Hall_Status" class="mw-headline">Accelerator and Hall Status</span></h1><ul><li>Hall A remains in Controlled Access, but is ready for beam (see 4th pass separator comments below).</li><li>GEM and Grinch experts have made a few short accesses for opportunistic debugging while we're down.</li></ul><ul><li>4th pass separator has prevented beam to Hall A since Wed afternoon.<ul><li>RF Separator work was unsuccessful as of 3pm Friday. <a class="external text" href="https://logbooks.jlab.org/entry/3946742" rel="nofollow">PD Update: 4th Pass IOT</a></li><li>Work on the 4th pass IOT has continued over the weekend. However, latest word is that no solution will be available until at least late-day shift on Monday (and that is still a little unclear). So, stay tuned...</li><li>There should expect an interruption to all Halls when OPs is ready to try bringing the 4th pass separator back online.</li></ul></li></ul><h2><span id="Plans_for_the_next_few_days" class="mw-headline">Plans for the next few days</span></h2><ul><li>Hall A will <em>not</em>be receiving beam this weekend.<ul><li>TOs must come in as planned to monitor the target and provide a point of contact in the Counting House</li><li>Shift Leaders have been notified that their shifts are cancelled through Tuesday OWL shift.</li><li>Tuesday DAY shift personnel should come in as planned. The Tuesday DAY shift leader is free to arrive at noon if he would prefer.</li></ul></li><li>We <strong>will</strong>continue with the BB and SBS configuration change first thing Monday morning.<ul><li>Since we are in Controlled Access already, and have not received beam since the last survey, we will be able to drop to Restricted quickly that morning.</li><li>We will still need to ensure that HVs are off and that it is safe for Techs to work on BB and SBS.</li></ul></li><li>The configuration change to SBS-11 is expected to be complete by the end of Day shift on Tuesday.</li><li>Depending on how stable the beam is to Hall C over the weekend, we are hoping to shift the pass change to Tuesday Swing (instead of Wed Day).<ul><li>We plan to nail the pass change details down on Sunday (tomorrow).</li></ul></li></ul><p><br /> Additional details in sub-section notes below.</p><p> </p><h1><span id="Run_Plan_for_When_Beam_Returns_.28Tuesday_OWL_or_Wednesday.29" class="mw-headline">Run Plan for When Beam Returns (Tuesday OWL or Wednesday)</span></h1><ul><li>Beam restoration to the Hall<ul><li><em>Start with Sieve IN or OUT?</em></li><li>Ensure target is OUT</li><li>GEM HVs OFF</li><li>SBS, BB OFF</li><li>All other systems should be ready to go</li></ul></li><li>After initial steer-up into Hall is complete<ul><li>Verify beam profile with Harp scans</li><li>Ramp BB and SBS to production currents</li><li>Determine raster size and position on target</li></ul></li><li>Low current GEM runs<ul><li>1 uA on LH2</li><li>Take ____ 5 min long runs with different GEM HV settings for quick voltage scan (needs details)</li><li>Take 1 30 min long run with the all GEMs at standard voltages to support track reconstruction checkout</li></ul></li><li>Move to Production Running cycle<ul><li>[UPDATE ME]</li></ul></li></ul><ul><li>Upcoming shift schedule issues <a class="external free" href="https://misportal.jlab.org/mis/physics/shiftSchedule/?experimentRunId=GMn-2021" rel="nofollow">https://misportal.jlab.org/mis/physics/shiftSchedule/?experimentRunId=GMn-2021</a><ul><li><strong>Several open TO positions starting Nov 24</strong></li><li>Configuration change on Monday-Tuesday (still the plan, but watch for updates!)<ul><li>Will plan to cancel SL shifts starting Monday DAY -- Tuesday DAY; Tuesday SWING shifts will proceed as planned for now (but stay tuned)</li><li>(Missing SL on Monday, but that is OK due to configuration change)</li></ul></li></ul></li></ul><h1><span id="Reminders_.2F_Notes" class="mw-headline">Reminders / Notes</span></h1><ul><li>Role sharing between SL and TO was discussed<ul><li>TO should support the SL wherever possible while still keeping primary focus on the target<ul><li>Beam Time accounting; Shift Checklist tasks are low-hanging fruit</li><li>Suggestion is to have TO start/stop runs and maintain the Run Log spreadsheet?</li></ul></li></ul></li></ul><ul><li>Run plan communication / documentation will be 'officially' documented on the <a title="Daily Meetings" href="https://sbs.jlab.org/wiki/index.php/Daily_Meetings#RC_Meetings">Daily_Meetings#RC_Meetings</a>page<ul><li>Don has made the Run Coordinator 'Run Plan / Report' page more visible on the wiki (and nicely formatted it)</li></ul></li></ul><h1><span id="Subsystem_Updates" class="mw-headline">Subsystem Updates</span></h1><ul><li>Hall Status:<ul><li>Presently in Controlled Access. We will stay in this mode until Monday morning.</li></ul></li></ul><ul><li>HCal:<ul><li>HCAL timing plots are being updated/corrected</li></ul></li></ul><ul><li>BBCal:<ul><li>New HV settings made for upcoming BB/SBS on/off settings<ul><li>Contact BBCal experts to load these if/when needed</li></ul></li><li>Corrected BBCal - HCal timing plots (histogram definition errors in prior plots, now fixed)<ul><li>plots make more sense, but more clean-up cuts would likely help -- work continues</li></ul></li><li>working on cluster optimization (algorithm modifications in analyzer)</li><li>Provokar will be out of town in the near future (will be posted on the wiki)<ul><li>Has been working on a number of 'how-to' scripts for experts (Arun, Sebastian, etc)</li></ul></li></ul></li></ul><ul><li>Timing hodoscope:<ul><li>working on RF alignment</li><li>HV instructions for hodoscope are in the wiki (and also re-posted to halog)</li></ul></li></ul><ul><li>Grinch:<ul><li>Study of LED data taken under different BB+SBS conditions underway</li><li>Maria/Todd/Bradley will be taking some more opportunistic LED pulser data through the weekend</li></ul></li></ul><ul><li>GEMS:<ul><li>GEM HV scan using cosmics will be worked on over the weekend</li><li>Likely still a good idea to do a (quick) 'voltage scan' with beam as well. Details TBD<ul><li>This will be a GEM-expert driven program.</li></ul></li><li>Work continues on calibrating/understanding the new GEM layer</li></ul></li></ul><ul><li>Beamline:<ul><li>indications that the 'clock' rate used to compute rates from scaler data in each scaler crate (SBS, LHRS) need to be checked<ul><li>clock value in analyzer likely off by a little in at least one arm</li><li>David F will go down into the Hall and explicitly measure the rates</li><li>Resolved: Clock signal rates measured here: <a class="external free" href="https://logbooks.jlab.org/entry/3946822" rel="nofollow">https://logbooks.jlab.org/entry/3946822</a></li></ul></li></ul></li></ul><ul><li><ul><li>David F is looking at scaler sanity checks with Paul</li></ul></li></ul><ul><li>DAQ:<ul><li>Alex reports that the LHRS scalers are not gated by the Trigger Supervisor -- will look into it<ul><li>Bob M. and David F. have responded and will be taking care of this</li></ul></li></ul></li></ul><ul><li>Replay analysis:<ul><li>GEM work is ongoing</li><li>Eric working on end-of-run report file output along with Dave F.</li></ul></li></ul></div>
<div class="attachment-box">
</div>
</article> </div>
</div>
</body>
</html>