<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I wasn't at this meeting but I want to comment on the suggestion to
start RECO earlier. One has to understand that RECO cannot start until
systems are stable at some level. Starting too early is counter
productive if reboots are ongoing, installation still happening,
software is not ready, manpower not available, etc. Starting too early
usually ends up with systems having to be checked multiple times. We
try to schedule the start time to give it our best shot at being
efficient and getting the job done on time. I should also add that a
small amount of HCO does occur prior to the official start date of RECO.<br>
Ron<br>
<br>
Arne Freyberger wrote:
<blockquote cite="mid4A9BD080.8020407@jlab.org" type="cite">
<meta http-equiv="content-type" content="text/html; ">
<title>B-team Meeting Agenda (2:00pm Wednesday MCC conf. room)</title>
<meta http-equiv="Content-Type"
content="text/html; charset=ISO-8859-1">
<meta name="generator" content="Org-mode">
<meta name="generated" content="2009-08-31 09:29:18 EDT">
<meta name="author" content="Arne Freyberger">
<meta name="description" content="">
<meta name="keywords" content="">
<style type="text/css">
<!--/*--><![CDATA[/*><!--*/
html { font-family: Times, serif; font-size: 12pt; }
.title { text-align: center; }
.todo { color: red; }
.done { color: green; }
.tag { background-color: #add8e6; font-weight:normal }
.target { }
.timestamp { color: #bebebe; }
.timestamp-kwd { color: #5f9ea0; }
p.verse { margin-left: 3% }
pre {
border: 1pt solid #AEBDCC;
background-color: #F3F5F7;
padding: 5pt;
font-family: courier, monospace;
font-size: 90%;
overflow:auto;
}
table { border-collapse: collapse; }
td, th { vertical-align: top; }
dt { font-weight: bold; }
div.figure { padding: 0.5em; }
div.figure p { text-align: center; }
.linenr { font-size:smaller }
.code-highlighted {background-color:#ffff00;}
.org-info-js_info-navigation { border-style:none; }
#org-info-js_console-label { font-size:10px; font-weight:bold;
white-space:nowrap; }
.org-info-js_search-highlight {background-color:#ffff00; color:#000000;
font-weight:bold; }
/*]]>*/-->
</style>
<script type="text/javascript">
<!--/*--><![CDATA[/*><!--*/
function CodeHighlightOn(elem, id)
{
var target = document.getElementById(id);
if(null != target) {
elem.cacheClassElem = elem.className;
elem.cacheClassTarget = target.className;
target.className = "code-highlighted";
elem.className = "code-highlighted";
}
}
function CodeHighlightOff(elem, id)
{
var target = document.getElementById(id);
if(elem.cacheClassElem)
elem.className = elem.cacheClassElem;
if(elem.cacheClassTarget)
target.className = elem.cacheClassTarget;
}
/*]]>*///-->
</script>
<div id="content">Notes from last Wednesday meeting. This week I'd
like to spend some time going over possible action items from this
list. An agenda will be distributed tomorrow. Arne<br>
<div id="outline-container-1" class="outline-2">
<h2 id="sec-1"><span class="section-number-2">1</span> <span
class="timestamp-wrapper"> <span class="timestamp">2009-08-26 Wed
14:00</span></span> Agenda–Notes </h2>
<div class="outline-text-2" id="text-1">
<ul>
<li id="sec-1.1">lessons learned from startup <br>
<ul>
<li id="sec-1.1.1">PD summary <br>
<ul>
<li id="sec-1.1.1.1">Report form Yan and Reza from the PDs
perspective <br>
<ul>
<li id="sec-1.1.1.1.1">Issues <br>
<ul>
<li>Staggered start would be better when we have
challenging new
experiments. </li>
<li>Hall A&C not ready for collaborative
checks. </li>
<li>three magnet setting issues
– injector quads :: CMPQ found this problem
– Arc dipoles :: CMPQ is typically ignored for these issues
– sextupoles :: Not on CMPQ, need to add </li>
<li>Join together MST, CMPQ, BURT for magnet
setting
integrity?? </li>
<li>Dogleg vacuum event – Are there improvements of
the dogleg tools.
– Why did it download a value of 0?
– RER team formed to investigate
– Alarm when value is out of range </li>
<li>MST improvements? AHLA has placed migrating MST
to elegant modeling
high on its priority list. Should the requirements be revisited? </li>
<li>8S, 9S skewed quads, how should they be set at
the beginning of the
run? Should they be set to zero? and adjusted at the end of the
ORFP to deal with coupling? </li>
<li>Injector 30Hz is not working. Need to fix this.
</li>
<li>Need to differentiate between standard
transport
equipment and new
experimental equipment (sextupoles). </li>
<li>Many Chiefs. Did we follow the optics-on-call
protocol?
– Need clear identification who is driving the bus.
– Did the operators know who to listen to. </li>
<li>pathlength and non-standard setting of MO. Back
to differentiating
between standard tools and new experimental methods. </li>
<li>Review of the scaled 7.5% file failed to miss
the
energy mishap
– Why are we manually scaling the file? </li>
<li>Viewer limited permissive. Need a procedure for
check that viewers
are clearing the FSD. Poelker has a method to check this. Need to
work getting this procedure as part of HCO. </li>
</ul>
</li>
<li id="sec-1.1.1.1.2">Things that went well <br>
<ul>
<li>Wien change went very smoothly, even to 90<sup>ˆ</sup>
</li>
<li>Inverted gun is great!!! All hail the gun
group!!!! </li>
<li>Injector-NL match !!! </li>
<li>BSY harps are not working, matching has not
been
attempted. – will have to debugged in the heat of the battle. </li>
<li>Parity beam setup went smoothly, Happex-II
value
has been achieved.
– Second round of improvements to come next week </li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
<li id="sec-1.1.2">Optics-on-Call <br>
<ul>
<li id="sec-1.1.2.1">Report from Byunn <br>
<ul>
<li>Did not expect to participate in setup, startup
period was much
more intensive than he thought. </li>
<li>New tools compared to 4 GeV commissioning are
impressive and really
improve the machine setup </li>
<li>Courrant-Snyder tool is a significant improvement </li>
<li>Tools should be complete and be a accurate
reflection
of the machine
(and elegant decks). </li>
</ul>
</li>
<li id="sec-1.1.2.2">General OOC issues during startup <br>
<ul>
<li>Would assigning shift coverage during the start up
help? </li>
</ul>
</li>
</ul>
</li>
<li id="sec-1.1.3">Operations <br>
<ul>
<li id="sec-1.1.3.1">Summary from Yan <br>
<ul>
<li>Start the RECO check out a few days earlier. </li>
<li>Conflict between Hall HCO and accelerator steerup
– MPS issues
– competition for EES resources
– Many viewers, need better procedures? </li>
</ul>
</li>
</ul>
</li>
<li id="sec-1.1.4">HKS, new line commissioning <br>
<ul>
<li id="sec-1.1.4.1">Report from Spata <br>
</li>
</ul>
</li>
<li id="sec-1.1.5">What worked? <br>
</li>
<li id="sec-1.1.6">What failed? <br>
</li>
</ul>
</li>
</ul>
</div>
</div>
<div id="outline-container-2" class="outline-2">
<h2 id="sec-2"><span class="section-number-2">2</span> <span
class="timestamp-wrapper"> <span class="timestamp">2009-08-12 Wed</span></span>
Agenda–Notes </h2>
<div class="outline-text-2" id="text-2">
<ul>
<li id="sec-2.1">Parity Quality Beam/Injector Setup <br>
<ul>
<li id="sec-2.1.1">Pockel Cell Alignment <span class="tag"><span
class="Physics">Physics</span></span><br>
</li>
<li id="sec-2.1.2">Injector setup <span class="tag"><span
class="Kazimi">Kazimi</span></span><br>
Status and future plans </li>
<li id="sec-2.1.3">Remaining Beam studies/injector work before
physics <br>
<ul>
<li>Yves PQB optimization
Status and schedule </li>
<li>Matching into NL
Schedule </li>
</ul>
</li>
</ul>
</li>
<li id="sec-2.2">August Configuration <br>
Hopefully I'll know what physics wants by tomorrow…. <span
class="timestamp-wrapper"> <span class="timestamp">2009-08-11
Tue 14:41</span></span><br>
Just heard from Physics, they would like a 7.5% unbalanced setup.
During the Hall-A one-pass running the θ<sub>Wien</sub> set such that B
get 100% alignment.
<p>Tuesday Aug. 25th Hall-A goes to 3-pass and θ<sub>Wien</sub>
set
such
that A get 100% alignment. </p>
<ul>
<li id="sec-2.2.1">Startup plans <span class="tag"><span
class="Yan">Yan</span></span><br>
Details of the startup presented for review. </li>
</ul>
</li>
<li id="sec-2.3">Fall beam studies <br>
Discuss overall goals for Beam studies this fall. In terms of
support for the future program, a major chunk of beam studies will
be used for commissioning the C50-9 module. We will discuss other
major efforts for the fall as well to help prioritize the beam
studies scheduling. </li>
</ul>
</div>
</div>
<div id="postamble">
<p class="date"> Date: 2009-08-31 09:29:18 EDT</p>
<p class="creator">HTML generated by org-mode 6.29trans in emacs 23</p>
</div>
</div>
<meta http-equiv="content-type"
content="text/html; charset=ISO-8859-1">
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Bteam mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bteam@jlab.org">Bteam@jlab.org</a>
<a class="moz-txt-link-freetext" href="https://mailman.jlab.org/mailman/listinfo/bteam">https://mailman.jlab.org/mailman/listinfo/bteam</a></pre>
</blockquote>
<br>
</body>
</html>