<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-1022576" 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/3949555" rel="bookmark">RC Update -- Wednesday 11/24</a>
</h1>
</header><div class="contextual-links-wrapper"><ul class="contextual-links"><li><a href="https://logbooks.jlab.org/entry/3949555/edit?destination=email/send">Edit</a></li><li><a href="https://logbooks.jlab.org/entry/3949555/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/3949555" class="lognumber" data-lognumber="3949555">3949555</a>. Submitted by <a href="https://logbooks.jlab.org/user/brads">brads</a> on <time datetime="2021-11-24T16:22:33-0500" pubdate="pubdate"><a href="https://logbooks.jlab.org/entries?start_date=1637785353&end_date=1637792553&book=HALOG">Wed, 11/24/2021 - 16:22</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>Configuration change to SBS-11 completed during Tuesday DAY shift<ul><li>LV cable got pulled out during changeover <a class="external autonumber" href="https://logbooks.jlab.org/entry/3949021" rel="nofollow">[1]</a>; fixed, but something to watch/check after next config change</li></ul></li><li>Accelerator worked on the pass change through Swing into Owl, got some beam into the Hall mid-Owl shift<ul><li>Had difficulties completing the Raster and Beam position checkout. Possibly due to optics issues downstream of the raster in the A-line <a class="external autonumber" href="https://logbooks.jlab.org/entry/3949291" rel="nofollow">[2]</a>, <a class="external autonumber" href="https://logbooks.jlab.org/entry/3949328" rel="nofollow">[3]</a>. Under investigation during day shift</li><li>Moller quads had an issue cycling -- now fixed <a class="external autonumber" href="https://logbooks.jlab.org/entry/3949347" rel="nofollow">[4]</a></li></ul></li><li>DAQ latencies noted on the GEMs seem to be global and caused issues with data taking throughout the night<ul><li>It is still unclear why the latency changed <a class="external autonumber" href="https://logbooks.jlab.org/entry/3949149" rel="nofollow">[5]</a>, <a class="external autonumber" href="https://logbooks.jlab.org/entry/3949058" rel="nofollow">[6]</a>, but they are being adjusted based on what we are seeing this morning. See more detailed notes in the DAQ sub-detector discussions</li></ul></li></ul><ul><li>Had some trouble with BBhodo HVs <a class="external autonumber" href="https://logbooks.jlab.org/entry/3949051" rel="nofollow">[7]</a><ul><li>Steve suggests a power cycle of the crate may help -- requires escorted access</li></ul></li></ul><ul><li>Cryo flow to target was found to be constrained last night<ul><li>This did not impact the program and was corrected this morning.</li></ul></li></ul><ul><li>Ran into a few computer related issues during Tuesday swing, now corrected <a class="external autonumber" href="https://logbooks.jlab.org/entry/3948975" rel="nofollow">[8]</a>, <a class="external autonumber" href="https://logbooks.jlab.org/entry/3948958" rel="nofollow">[9]</a></li></ul><ul><li>4th pass separator issue will be worked on today (Wednesday)<ul><li>Original 4th Pass IOT ("IOT3") has been declared unrepairable (for now)</li><li>Plan is to move 2nd Pass IOT up to 4th (then move it back later in the program) <a class="external autonumber" href="https://logbooks.jlab.org/entry/3948986" rel="nofollow">[10]</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><h1><span id="Run_Plan_for_Wednesday--Thursday" class="mw-headline">Run Plan for Wednesday--Thursday</span></h1><pre>This will be updated as we better understand what needs to be redone with corrected readout latencies.
We should be able to complete the 'Initial Beam steer-up', raster and beam position checkout this morning.
</pre><ul><li>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.</li><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><p> </p><ul><li>[Complete] <span style="text-decoration: line-through;"><span style="text-decoration: line-through;"><strong>Beam restoration to the Hall</strong>(MCC driven program to get beam to the dump)</span></span><ul><li>BB Sieve is IN</li><li>Ensure target is OUT</li><li>GEM HVs OFF</li><li>SBS, BB Magnets OFF</li><li>All other systems should be ready to go</li></ul></li></ul><p><span style="text-decoration: line-through;"> </span></p><p> </p><ul><li><strong>After initial steer-up into Hall is complete</strong> (call Don Jones if you have issues during Swing/Owl or David Flay during the Day <a title="Subsystem Expert Contacts" href="https://sbs.jlab.org/wiki/index.php/Subsystem_Expert_Contacts"><strong>Phone Numbers</strong></a>)<ul><li>Verify beam profile with <a title="Harp Scans for Checking Beam Spot Size on Target" href="https://sbs.jlab.org/wiki/index.php/Harp_Scans_for_Checking_Beam_Spot_Size_on_Target"><strong>Harp scans</strong></a></li><li>Determine <a title="SBS spot++ (beam size verification)" href="https://sbs.jlab.org/wiki/index.php/SBS_spot++_(beam_size_verification)#Procedure_to_check_beam_position_and.2For_calibrate_raster_size"> <strong>raster size and position</strong></a>on target<ul><li>When complete be sure to make a halog and update the whiteboard with the new raster and beam position numbers</li></ul></li></ul></li></ul><ul><li><strong>Inform the RC when we get here.</strong> The plan will be to stop beam to Hall A and allow OPS to work on the 4th-pass line and RF separator system. We will stay in Beam Permit and retake the BBCal cosmics runs (below).</li></ul><ul><li>[Complete] <span style="text-decoration: line-through;"><span style="text-decoration: line-through;"><strong>Take BBCal cosmics data <em>with magnets on</em> to get HV settings established when above steering/raster checks are complete. (Call the RC)</strong></span></span><ul><li>Turn on BB (750A) and ask MCC to ramp SBS to 2100A</li><li>Ensure all detector HVs are ON, set BBCal threshold for Cosmics (~200 Hz), take 500k triggers</li><li>Keep beam out of the Hall until this is completed</li></ul></li></ul><p><span style="text-decoration: line-through;"> </span></p><p> </p><ul><li><strong>Call MCC and ask that they complete their procedure to ramp SBS to production currents (2100A pos) and adjust correctors</strong><ul><li>This may require ramping BB to zero (ask them)</li><li>Verify beam position is still where you want it (centered on target)</li></ul></li></ul><ul><li><strong>Ask MCC will to complete Ion Chamber calibrations on LD2</strong><ul><li>'Thin' target ion chamber calibration should be complete Wed OWL (covers carbon foils, dummy)</li></ul></li></ul><ul><li><strong>Prep for GEM/Optics checkout</strong><ul><li>Contact GEM expert (on whiteboard) to support the GEM checkout program</li><li>Contact Holly and Andrew [call numbers on whiteboard] as well, <strong>if this starts before midnight</strong></li><li><strong>Turn GEM HV back ON</strong>; Ensure other detectors are ready to go.</li><li>Initial threshold settings for BBCAL and HCAL<ul><li>BBCAL threshold ~0.5 GeV (<strong>readback</strong> is: -100 mV)</li><li>HCAL threshold ~0.5 GeV (readback: -80 mV)</li></ul></li></ul></li></ul><ul><li><strong>Optics Runs for SBS-11</strong><ul><li><strong>Zero Field Alignment</strong></li><li>SBS OFF, BB OFF, Sieve IN</li><li>single C foil target</li><li>BBCAL threshold 0.5 GeV (-100 mV); adjust threshold/beam to get a ~3 kHz of rate</li><li>I = 5 uA</li><li>30 min of beam on target</li><li><strong>Vertex and Angle Reconstruction 1/2</strong></li><li>SBS ON (2100A pos.), BB ON (750A neg.), Sieve IN</li><li>5-foil Optics target</li><li>BBCAL threshold 0.8 GeV (-160 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 (2100A pos.), BB ON (750A neg.), Sieve IN</li><li>4-foil Optics target</li><li>BBCAL threshold 0.8 GeV (-160 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!)<ul><li>Call RC ~1 hour before you will need to do this (Brad, Bill, _???_ are authorized to move sieve)</li></ul></li></ul><ul><li><strong>Low current GEM runs</strong><ul><li>SBS ON (2100A pos.), BB ON (750A neg.)</li><li>BBCAL threshold set to establish sufficient rate for a GEM efficiency HV scan; Adjust threshold to get to a few kHz of triggers</li><li>1 uA on LH2 target</li><li>Take 7 ~5 min long runs with different GEM HV settings for quick voltage scan<ul><li><strong>GEM expert driven ONLY</strong> (ensure GEM expert on shift; or call RC if not sure)</li><li>Voltages: 3653, 3608, 3564, 3519, 3475, 3430, 3385</li></ul></li></ul></li></ul><pre><strong>Confirm Production Threshold Settings in BBCal and HCal</strong>
</pre><ul><li><strong>GEM Rate Study</strong><ul><li>Ensure GEM HVs are back at standard settings; detectors should be at Production settings</li><li>SBS ON (2100A pos.), BB ON (750A neg.)</li><li>BBCAL threshold 2.0 GeV (-400 mV) -- want a nominal 100k triggers/run</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 (2100A pos.), BB ON (750A neg.)</li><li>BBCAL threshold 2.0 GeV (-400 mV)</li><li>HCAL threshold ~0.5 GeV (-80 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></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 A left side camera not responding (can't switch to it) <a class="external autonumber" href="https://logbooks.jlab.org/entry/3949119" rel="nofollow">[11]</a></li></ul><ul><li>HV Questions/Issues<ul><li>BB hodoscope HV issues <a class="external autonumber" href="https://logbooks.jlab.org/entry/3949051" rel="nofollow">[12]</a> (Steve, Ralph?)</li><li>HCAL HV status display glitch? <a class="external autonumber" href="https://logbooks.jlab.org/entry/3948667" rel="nofollow">[13]</a> -- Cause understood. Due to 'Crate OFF' button being used. Largely cosmetic</li></ul></li></ul><ul><li>HCal:<ul><li>Present data on HCal detector calibrations (timing, energy calibration and uniformity over acceptance, coordinate resolution) at upcoming meeting</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 [Arun] to load these and monitor BBCal performance during beam restart</li></ul></li><li>Cosmics runs in SBS-11 configuration with magnets on: <a class="external autonumber" href="https://logbooks.jlab.org/entry/3949491" rel="nofollow">[14]</a>; significant fringe field gain suppression in PMTs<ul><li>HVs adjusted and uploaded <a class="external autonumber" href="https://logbooks.jlab.org/entry/3949512" rel="nofollow">[15]</a></li></ul></li><li>Parts arrived for PMT dry-air flushing system; needs SSG support</li></ul></li></ul><ul><li>Timing hodoscope:<ul><li>Working on RF alignment<ul><li>Rachel gave a status update online and will post to the halog</li><li>Been working through analysis related issues; making progress; several issues remain in presentation</li><li>Mark suggested he may need to write a new class to handle the RF time and make it easier to work with within the analyzer</li></ul></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 on LED data 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 -- many had bad latency; may not be useful...</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>Still investigating the following: large number of fake tracks; possible issues with pedestal suppression, or perhaps indication of cross-talk; unclear... (this hypothesis is still under test)</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></ul></li><li>DAQ latencies issues noted in the GEMs seem to be global and caused issues with data taking throughout the night<ul><li>It is still unclear why these changed <a class="external autonumber" href="https://logbooks.jlab.org/entry/3949149" rel="nofollow">[16]</a>, <a class="external autonumber" href="https://logbooks.jlab.org/entry/3949058" rel="nofollow">[17]</a>, but latencies are being adjusted based on what we are seeing this morning: <a class="external text" href="https://logbooks.jlab.org/entry/3949316" rel="nofollow">HCAL</a>, <a class="external text" href="https://logbooks.jlab.org/entry/3949314" rel="nofollow">GEM</a>, <a class="external text" href="https://logbooks.jlab.org/entry/3949322" rel="nofollow">UV GEMs</a>, BBCAL, BBHod, BBGrinch seem to be OK now</li></ul></li></ul></li></ul><ul><li>Beamline:<ul><li>David F is looking at scaler sanity checks with Paul</li></ul></li></ul><ul><li>DAQ:<ul><li>Need electronics, timing diagrams that represents 'as-built' system</li><li>Latency shift was discovered to be common to entire DAQ<ul><li>Seems to have changed around the time the ROLs were updated; which was around the time of some library updates</li></ul></li><li>Latency configurations seem to be a mess based on comments in Slack (scattered across many files, interactions between global and 'local' settings, etc)<ul><li>At minimum, this should probably be documented on the wiki?</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.<ul><li>Would be great to summarize total Charge on target, 'good event' statistics, as well as summarizing efficiencies and other QA related parameters?</li><li>Probably most useful for full replays? (Online histo display should cover most/all of what the shift crew need to monitor already?)</li></ul></li><li>Online analysis golden runs -- what do shift crew check run-by-run?<ul><li>Generate a stripped-down set of plots for shift crew monitoring; experts can use a different Panguin config with a full set of plots?</li></ul></li><li>Plan for full analyses on Farm?<ul><li>This seems to be one of the items holding up more complete analyses of prior data</li><li>Sounds like a plan needs to be hammered out and implemented?</li></ul></li></ul></li></ul></div>
<div class="attachment-box">
</div>
</article> </div>
</div>
</body>
</html>