<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-1021368" 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/3948347" rel="bookmark">RC Update -- Monday Nov 22</a>
</h1>
</header><div class="contextual-links-wrapper"><ul class="contextual-links"><li><a href="https://logbooks.jlab.org/entry/3948347/edit?destination=email/send">Edit</a></li><li><a href="https://logbooks.jlab.org/entry/3948347/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/3948347" class="lognumber" data-lognumber="3948347">3948347</a>. Submitted by <a href="https://logbooks.jlab.org/user/brads">brads</a> on <time datetime="2021-11-22T20:12:12-0500" pubdate="pubdate"><a href="https://logbooks.jlab.org/entries?start_date=1637626332&end_date=1637633532&book=HALOG">Mon, 11/22/2021 - 20:12</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 is in Restricted Access and the configuration change to SBS-11 is underway -- will continue through Tuesday DAY shift<ul><li>We need to ensure that HVs are off when the Techs are working. They can be turned on for tests during SWING/OWL (check with the RC and make clear Halog entries please!)</li><li><a class="external text" href="https://logbooks.jlab.org/entry/3948208" rel="nofollow">Downstream beamline bled up</a> -- holding well</li><li>Hall A Technical staff has priority during changeover</li></ul></li><li>GEM and Grinch experts plan to continue opportunistic debugging while we're down.</li></ul><ul><li>4th pass separator repairs are ongoing<ul><li><a class="external text" href="https://logbooks.jlab.org/entry/3948246" rel="nofollow">PD Update: 4th Pass IOT</a></li><li>This primarily impacts Hall C at this point, but there will be downtimes associated with reintegration and tuning once repairs are completed.</li></ul></li></ul><ul><li><a class="external text" href="https://logbooks.jlab.org/entry/3948232" rel="nofollow">Heat off in the Hall A Gas Shed - back on</a> (This can cause incorrect readings from the BGA.)</li></ul><h2><span id="Plans_for_the_next_few_days" class="mw-headline">Plans for the next few days</span></h2><ul><li>The pass change has tentatively been moved to Tuesday Swing/OWL (instead of Wed Day) -- assumes reasonable Accelerator uptime Mon/Tuesday<ul><li>Final confirmation of pass change date will be Tuesday morning RC meeting, but we will proceed under the assumption that pass change will occur Tuesday SWING/OWL.</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></ul><p>Additional details in sub-section notes below.</p><h1><span id="Run_Plan_for_When_Beam_Returns_.28Tuesday_Evening_or_Wednesday.29" class="mw-headline">Run Plan for When Beam Returns (Tuesday Evening or Wednesday)</span></h1><pre>The <a class="external text" href="https://sbs.jlab.org/cgi-bin/DocDB/private/ShowDocument?docid=140" rel="nofollow">SBS-11 Runplan (PDF)</a> document is on the DocDB. Please update the file there if needed.
</pre><pre>This runplan is a draft. Stay tuned for changes (and updates to the ??? below.)
</pre><ul><li>Take BBCal cosmics data <em>with magnets on</em> to get HV settings established as soon as Hall can be locked up</li><li>Beam restoration to the Hall<ul><li><strong>Start with Sieve IN</strong></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></ul><ul><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></ul><ul><li><a class="external text" href="https://logbooks.jlab.org/entry/3948082" rel="nofollow">Position + separation of protons and neutrons for SBS11 (Bdl = 1.6 T.m)</a></li></ul><pre>CONFIRM: Production SBS current is 2100A (100%) or 1785A (85%)?
</pre><ul><li>Initial threshold settings for BBCAL and HCAL<ul><li>[FIXME] BBCAL threshold 0.5 GeV (??? mV)</li><li>[FIXME] HCAL threshold ??? (??? mV)</li></ul></li></ul><ul><li>Turn GEM HV back ON; Ensure other detectors are ready to go.</li></ul><ul><li>Optics Runs for SBS-11<ul><li><strong>Zero Field Alignment</strong></li><li>SBS OFF, BB OFF, Sieve IN</li><li>single C foil target</li><li>[FIXME] BBCAL threshold 0.5 GeV (??? mV)</li><li>I = 5--10 uA</li><li>60 min of beam on target</li><li><strong>Vertex and Angle Reconstruction 1/2</strong></li><li>SBS ON (1785A pos.), BB ON (750A neg.), Sieve IN</li><li>5-foil Optics target</li><li>[FIXME] BBCAL threshold 0.8 GeV (??? mV)</li><li>I <= 20 uA</li><li>60 min of beam on target</li><li><strong>Vertex and Angle Reconstruction 2/2</strong></li><li>SBS ON (1785A pos.), BB ON (750A neg.), Sieve IN</li><li>4-foil Optics target</li><li>[FIXME] BBCAL threshold 0.8 GeV (??? mV)</li><li>I <= 20 uA</li><li>60 min of beam on target</li></ul></li></ul><ul><li><strong>Escorted Access to take Sieve OUT</strong> (needs trained personnel!)</li></ul><ul><li><strong>Low current GEM runs</strong><ul><li>SBS ON (1785A pos.), BB ON (750A neg.)</li><li>[FIXME] BBCAL threshold 2.0 GeV (??? mV)</li><li>1 uA on LH2 target</li><li>Take ____ 5 min long runs with different GEM HV settings for quick voltage scan<ul><li>[FIXME] GEM HV Settings TBD for efficiency scan</li></ul></li></ul></li></ul><ul><li><strong>GEM Rate Study</strong><ul><li>Ensure GEM HVs are back at standard settings</li><li>SBS ON (1785A pos.), BB ON (750A neg.)</li><li>[FIXME] BBCAL threshold 2.0 GeV (??? mV)</li><li>LH2 target</li><li>I=1 uA ; take 1 30min run</li><li>I=15 uA ; take 1 30min run</li><li>I=5 uA ; take 1 30min run</li><li>I=1 uA ; take 1 30min run</li></ul></li></ul><ul><li><strong>Move to Production Running cycle</strong><ul><li>SBS ON (1785A pos.), BB ON (750A neg.)</li><li>[FIXME] BBCAL threshold 2.0 GeV (??? mV)</li><li>[FIXME] HCAL threshold ??? (??? mV)</li><li><strong>Goal: HCAL calib</strong><ul><li>LH2 Target; I = 15uA</li><li>10M triggers (nom. 1 hr)</li></ul></li><li><strong>Goal: Production</strong><ul><li>LD2 Target; I = 8uA</li><li>40M triggers (nom. 4 hr)</li></ul></li><li><strong>Goal: HCAL calib</strong><ul><li>LH2 Target; I = 15uA</li><li>10M triggers (nom. 1 hr)</li></ul></li><li><strong>Goal: Production</strong><ul><li>LD2 Target; I = 8uA</li><li>30M triggers (nom. 3 hr)</li></ul></li><li><strong>Goal: Production/Dummy</strong><ul><li>Dummy Target; I = 15uA</li><li>2.5M triggers (nom. 0.5 hr)</li></ul></li></ul></li></ul><ul><li>This nominally takes us to Friday 11/26 in the <a class="external text" href="https://sbs.jlab.org/cgi-bin/DocDB/private/ShowDocument?docid=140" rel="nofollow">SBS-11 Runplan (PDF)</a> document. Progress will be reassessed and subsequent runplan updated as needed.</li></ul><hr /><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 26</strong> (Bill H. picked up shifts on 24,25)</li><li>John Arrington's Tuesday Swing shift is marked 'Trade Requested', but he's been confirmed.</li><li>Shift Leaders have been notified that their shifts are cancelled through Tuesday OWL shift (during config change)</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></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>HCal:<ul><li>HCAL timing plots are being updated/corrected</li><li>Wiki instructions have been updated</li><li>Working on clustering in SBS offline</li><li>Will be using old HVs for SBS-11 startup</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 and monitor BBCal performance during beam restart</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 tonight (Monday)</li><li>Status update to Halog was requested</li></ul></li></ul><ul><li>GEMS:<ul><li>GEM experts will be monitoring the gas bottles over the holidays (should be fine, but extra eyes will help)</li><li><a class="external text" href="https://logbooks.jlab.org/entry/3947765" rel="nofollow">GEM HV Cosmic Scan Status</a><ul><li>No analysis of these runs yet(?)</li></ul></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<ul><li>Andrew reports things seem to be generally working, but some issues still being worked on</li><li>Identified an incorrect guess/assumption for the z-location. When corrected, that significantly improved tracking performance (the steep incident angle for cosmics makes tracking particularly sensitive to the z-location of the layers)</li><li>Still investigating the following: large number of fake tracks; possible issues with pedestal suppression, or perhaps indication of cross-talk; unclear...</li></ul></li><li>GEM "HV-off" cosmics data are on disk -- not clear if it has been looked at (may help disentangle potential cross talk sources)</li><li>Some confusion over an apparent latency shift for the new UV layer?<ul><li>Source of shift is not understood</li><li>New data taken with a shifted latency in DAQ configuration, but still to be looked at</li></ul></li><li>Some confusion over a large latency shift occurred after the 2 APVs in the UV layer were fixed<ul><li>Run 12131 (Friday 1pm) shows this shift, old timing was present in run 12101 (Thursday morning). May have shifted around the time of the pedestal run?</li><li>Alex, Andrew, and other DAQ/GEM experts will try to nail down the timing and cause of this shift</li></ul></li></ul></li></ul><ul><li>Beamline:<ul><li>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> [Resolved]</li><li>L-HRS scaler gate fixes and notes: <a class="external autonumber" href="https://logbooks.jlab.org/entry/3947753" rel="nofollow">[1]</a>, <a class="external autonumber" href="https://logbooks.jlab.org/entry/3947743" rel="nofollow">[2]</a>(Bob. M)<ul><li>Notes that the ET events have not been checked recently</li></ul></li><li>David F is looking at scaler sanity checks with Paul</li></ul></li></ul><ul><li>DAQ:<ul><li><a class="external text" href="https://logbooks.jlab.org/entry/3948142" rel="nofollow">CODA ET library updated</a>Monday afternoon<ul><li>Alex will do some stress tests on DAQ while the Hall is open</li></ul></li><li>General DAQ stability?<ul><li>Frequent crashes at start or end of run</li><li>New runs frequently do not start successfully and require cycles of reset/config/reset</li><li>Could be ET issue, but some failures tied to VTP crate as well</li></ul></li></ul></li></ul><ul><li>Replay analysis:<ul><li>GEM work is ongoing (see above)</li><li>Eric working on end-of-run report file output along with Dave F.</li><li><a class="external text" href="https://logbooks.jlab.org/entry/3948252" rel="nofollow">Updates to BCM Scaler Database Files</a>(David F.)<ul><li>Fixes some duplicate variable names in the TSsbs tree</li></ul></li></ul></li></ul><p> </p><ul><li>Counting House Computer requests [Ole will be looking into a number of these items]<ul><li><a class="external text" href="https://logbooks.jlab.org/entry/3948218" rel="nofollow">analyzer updated on hadesk machines</a></li><li>Streamline access to common tools (halog, go_* scripts, etc)<ul><li>Perhaps get them in a common bin/ directory and added to $PATH?</li></ul></li><li>Firefox configurations differ quite a bit depending on <a href="mailto:user@host">user@host</a><ul><li>Update common configuration to improve useful bookmark toolbar links</li><li>halog, elog, SBS wiki, Shift crew help, etc</li><li>'New' tabs default to something useful, etc</li></ul></li></ul></li></ul></div>
<div class="attachment-box">
</div>
</article> </div>
</div>
</body>
</html>