<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body>
<style type="text/css">html { font-family: Times,serif; font-size: 12pt; }.title { text-align: center; }.todo { color: red; }.done { color: green; }.tag { background-color: rgb(173, 216, 230); font-weight: normal; }.target { }.timestamp { color: rgb(190, 190, 190); }.timestamp-kwd { color: rgb(95, 158, 160); }p.verse { margin-left: 3%; }pre { border: 1pt solid rgb(174, 189, 204); background-color: rgb(243, 245, 247); 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: rgb(255, 255, 0); }.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: rgb(255, 255, 0); color: rgb(0, 0, 0); font-weight
: bold; }</style>
<div id="content">
<h1 class="title">B-team Meeting Notes</h1>
<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">2010-11-17
Wed 14:52</span></span> Agenda </h2>
<div class="outline-text-2" id="text-1">
</div>
<div id="outline-container-1.1" class="outline-3">
<h3 id="sec-1.1"><span class="section-number-3">1.1</span>
Optics-on-Call Report <span class="tag"><span
class="Spata">Spata</span></span></h3>
<div class="outline-text-3" id="text-1.1">
<p>the 9.6kHz vertical easter egg hunt
</p>
<ul>
<li>
present focus is on the pre-buncher as the source or
amplifier of
the problem.
</li>
<li>
Is there information to be gained by simulating or
trying to
simulating the effect? CASA will look into this.
</li>
</ul>
</div>
</div>
<div id="outline-container-1.2" class="outline-3">
<h3 id="sec-1.2"><span class="section-number-3">1.2</span>
Beam Studies Report <span class="tag"><span class="All">All</span></span></h3>
<div class="outline-text-3" id="text-1.2">
<ul>
<li>
M<sub>56</sub> issues, diagnostics and training. "The
Friday Event"
<ul>
<li>
what is the design sensitivity of the device?
10mV/degree? </li>
<li>
Injector to north linac match came late in the game,
but match
happened without too much issue.
</li>
</ul>
</li>
<li>
Two Wien setup
<ul>
<li>
nice setup, too bad we mucked it up my pulling the
Vertical Wien
HV.
</li>
<li>
made more complicated then it needs to be by having
the
pre-buncher scrunched between the two Wiens. No
action, but Reza
should take note of this comment and incorporate it
into the 12GeV
injector design. In other words, we are going to
live with this
situation at least to the end of the 6GeV program.
</li>
</ul>
</li>
<li id="sec-1.2.1"><span class="todo TODO"> TODO</span>
form a RAR committee to investigate Thursday/Friday tune
time <span class="tag"><span class="Krafft">Krafft</span> <span
class="Arne">Arne</span></span><br>
<span class="timestamp-wrapper"><span
class="timestamp-kwd">DEADLINE: </span> <span
class="timestamp">2010-11-19 Fri</span></span><br>
More than 8 hours of downtime is associated with the
last Thursday and
Friday activities. There is room for improvement and
this event
provides an opportunity to review how Optics tuning is
performed,
tools are calibrated/documented and any other
operational aspects of
achieving efficient deterministic beam tuning exercises.
</li>
<li id="sec-1.2.2"><span class="todo TODO"> TODO</span>
write charge to the committee <span class="tag"><span
class="Krafft">Krafft</span> <span class="Arne">Arne</span></span><br>
<span class="timestamp-wrapper"><span
class="timestamp-kwd">DEADLINE: </span> <span
class="timestamp">2010-11-23 Tue</span></span><br>
</li>
<li id="sec-1.2.3">Plans for Thursday and Tuesday Beam
studies <br>
<ul>
<li>
heat/activate schedule: To be determined by
Thursday's QE
scan. (0.5h)
<ul>
<li>
if needed to get through Thanksgiving, will do
this on Monday
</li>
<li>
otherwise defer to after Thanksgiving
</li>
</ul>
</li>
<li>
Re-instate the Vertical Wien (0.5h)
</li>
<li>
Investigate pre-buncher electronics (1h)
</li>
<li>
recalibrate the Vertical Wien
</li>
<li>
Reestablish high current setup with max gradient of
pre-buncher of
2.0? depends on what they find with the pre-buncher
investigation.
</li>
<li id="sec-1.2.3.1">pre-buncher options <br>
<ul>
<li>
network analyze the output of the amplifiers
</li>
<li>
install more supplemental amplifiers
</li>
<li>
run with reduced amplitudes on the pre-buncher
</li>
</ul>
</li>
</ul>
</li>
</ul>
</div>
</div>
<div id="outline-container-1.3" class="outline-3">
<h3 id="sec-1.3"><span class="section-number-3">1.3</span>
FY11 Bteam Projects </h3>
<div class="outline-text-3" id="text-1.3">
<ul>
<li id="sec-1.3.1">12GeV Pathlength resolution <br>
<span class="timestamp-wrapper"><span
class="timestamp-kwd">DEADLINE: </span> <span
class="timestamp">2010-12-20 Mon</span></span><br>
finish off the 12GeV pathlength issues and get
definitive answer from
12GeV. Remaining issues:
<ul>
<li id="sec-1.3.1.1"><span class="todo TODO"> TODO</span>
Analysis of the Sep. 2010 LCW heatrise test <span
class="tag"><span class="Krafft">Krafft</span></span><br>
<span class="timestamp-wrapper"><span
class="timestamp-kwd">DEADLINE: </span> <span
class="timestamp">2010-12-06 Mon</span></span><br>
Write a tech-note summarizing the data and results.
No interpretation
required, that goes in the next document.
Jay is the contact point on the data. Casa will
supply the words and
analysis. The basic goal is to take all the pictures
in the Elog of
the pathlength scopes and from that calculate the
pathlength change as
a function of time. Overly or correlate the
temperature data (in a
separate file/format) with the pathlength data. From
this we should
be able to get some information on pathlength vs
tunnel temperature.
</li>
<li id="sec-1.3.1.2"><span class="todo TODO"> TODO</span>
document Update/table with agreed upon requirements
<span class="tag"><span class="Tiefen">Tiefen</span></span><br>
<span class="timestamp-wrapper"><span
class="timestamp-kwd">DEADLINE: </span> <span
class="timestamp">2010-12-06 Mon</span></span><br>
Finish/polish off Tief's tech-note on pathlength.
Include reference
of the Sept. LCW heat test to cap the maximum
excursion expected.
This is a requirements document, not a design
document.(just a reminder)
</li>
<li id="sec-1.3.1.3"><span class="todo TODO"> TODO</span>
Transfer to 12GeV <span class="tag"><span
class="Pilat">Pilat</span> <span class="Arne">Arne</span> <span
class="Krafft">Krafft</span></span><br>
<span class="timestamp-wrapper"><span
class="timestamp-kwd">DEADLINE: </span> <span
class="timestamp">2010-12-20 Mon</span></span><br>
</li>
</ul>
</li>
<li id="sec-1.3.2">Pathlenth adjustment via MO frequency
changes <br>
Develop the requirements for this new tool so that
Eng/AHLA/Controls/OPS can work on developing a complete
tool for
routine operations.
<ul>
<li id="sec-1.3.2.1"><span class="todo TODO"> TODO</span>
Draft of requirements <span class="tag"><span
class="Tiefen">Tiefen</span></span><br>
<span class="timestamp-wrapper"><span
class="timestamp-kwd">DEADLINE: </span> <span
class="timestamp">2011-08-15 Mon</span></span><br>
</li>
<li id="sec-1.3.2.2"><span class="todo TODO"> TODO</span>
Project Charter written and team formed <span
class="tag"><span class="Tiefen">Tiefen</span></span><br>
<span class="timestamp-wrapper"><span
class="timestamp-kwd">DEADLINE: </span> <span
class="timestamp">2011-09-19 Mon</span></span><br>
</li>
<li id="sec-1.3.2.3"><span class="todo TODO"> TODO</span>
Requirements review, reiterated upon and accepted
<span class="tag"><span class="BTEAM">BTEAM</span></span><br>
<span class="timestamp-wrapper"><span
class="timestamp-kwd">DEADLINE: </span> <span
class="timestamp">2011-10-03 Mon</span></span><br>
</li>
<li id="sec-1.3.2.4"><span class="todo TODO"> TODO</span>
Project goals, milestones and work effort
established <span class="tag"><span class="AHLA">AHLA</span> <span
class="ENG">ENG</span> <span class="OPS">OPS</span></span><br>
<span class="timestamp-wrapper"><span
class="timestamp-kwd">DEADLINE: </span> <span
class="timestamp">2011-10-10 Mon</span></span><br>
</li>
</ul>
</li>
<li id="sec-1.3.3">raytrace <br>
If this is to be a part of the 12GeV tool chest, would
like to see
prototyping and requirements of what this tool is and
how AHLA can
help. LOCO techniques might be more applicable. Future
talk to
B-team from Yves on the path forward.
</li>
<li id="sec-1.3.4">Other 12GeV required projects? <br>
<ul>
<li id="sec-1.3.4.1">shims on BW to test modeling of
dog-leg <br>
The shunts will be installed during the 6-months for
understanding
dog-legs? Power supply management issue. Low impact.
</li>
<li id="sec-1.3.4.2">Synchrotron light ports <br>
Arc9, Arc8, Arc7, Arc10, four in each arcs.
Arc8 would be best to do this summer, at least the
vacuum chambers.
<ul>
<li>
estimate is about 17k per synchrotron port. Is
this just the vacuum
chamber? </li>
<li>
benefit would be continuous monitoring of the
beam </li>
<li>
perhaps need 80k this year to do Arc8. </li>
<li>
Need to enter project into the AWP system.
Initially as an unfunded
priority and then we will see if it fits within
future AIP or
general RSR funding profiles.
</li>
</ul>
</li>
<li id="sec-1.3.4.3">Moving harps around <br>
completing the BSY diagnostic suite. This is funded
as the completion
of the AIP BSY.
<ul>
<li id="sec-1.3.4.3.1"><span class="todo TODO">
TODO</span> Present final plan <span
class="tag"><span class="Benesch">Benesch</span></span><br>
<span class="timestamp-wrapper"><span
class="timestamp-kwd">DEADLINE: </span> <span
class="timestamp">2010-12-01 Wed</span></span><br>
Include upgrading quad power supplies to aid
collecting quad scan data
through the minimum.
</li>
</ul>
</li>
</ul>
</li>
</ul>
</div>
</div>
<div id="outline-container-1.4" class="outline-3">
<h3 id="sec-1.4"><span class="section-number-3">1.4</span>
Optics model update <span class="tag"><span class="Arne">Arne</span></span></h3>
<div class="outline-text-3" id="text-1.4">
<p>This is a modest change/correction to the present design
optics. The
goal is to correct some errors that crept into the system,
mostly in
Arc1 and Arc2. My working notes are attached, these notes
represent
where I was on this project in April of this year.
Basically Arc1 is
in reasonable shape. I need to move onto Arc2 and then
complete the
process.
</p>
<p>
For the Jan2011 download, no changes to the element
definitions other
than quad design strength will be made. Subsequent studies
in the first
half of 2011 will tell us if we need to change any dipole
body
gradients or RF modeling parameters. In other words this
is a small
change (see the table in the attached document)
</p>
<ul>
<li>
Arc1 ala elegant
</li>
<li>
realtime CS tool? Geoff brought up the fact that if the
elegant
model is used to define the design, than the CS tool
should
reference the elegant model. Unfortunately upgraded CS
tool to use
the elegant infrastructure is not on the FY11 plan
(probably
hopefully FY12). Michael T. pointed out that the BPM
noise is probably larger than
the design noise. Looking over the table in the document
there is
one quad that has a 10% change between optim and
elegant. Perhaps
this quad will be noise. We will have to make note of
these special
quads. We can also think about converting from elegant
to optim so
that the CS tool will pick up these changes in the
interim. No
action other than a discussion with AHLA to see if there
are any
mitigating efforts that can/should be made.
</li>
</ul>
</div>
</div>
<div id="outline-container-1.5" class="outline-3">
<h3 id="sec-1.5"><span class="section-number-3">1.5</span>
Anything else? </h3>
<div class="outline-text-3" id="text-1.5">
<ul>
<li id="sec-1.5.1">Optics-on-call over Thanksgiving? <span
class="tag"><span class="Krafft">Krafft</span> <span
class="Hofler">Hofler</span></span><br>
Don't touch anything!
</li>
</ul>
</div>
</div>
</div>
<div id="postamble">
<p class="date"> Date: 2010-11-17 16:40:07 EST</p>
<p class="creator">HTML generated by org-mode 6.33x in emacs 23</p>
</div>
</div>
<br>
<pre class="moz-signature" cols="72">--
Director of Accelerator Operations
Jefferson Lab Office: (757) 269-6268
12000 Jefferson Avenue Cell: (757) 876-6289
Newport News, VA 23606 Email: <a class="moz-txt-link-abbreviated" href="mailto:freyberg@jlab.org">freyberg@jlab.org</a>
</pre>
</body>
</html>