<!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>
<title>B-team Meeting Notes</title>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="generator" content="Org-mode">
<meta name="generated" content="2010-12-07 12:15:45 EST">
<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">
<div align="left">
</div>
Colleagues,<br>
Todd is on travel, I'll be leading tomorrow's B-Team.
Tomorrow's agenda and past meeting notes are below. Please come
prepared to talk to any items marked as TODO, INPROGRESS in the
notes of previous meetings.<br>
<br>
Also, it would be great to hear from QWeak (Paul can you identify
someone to come to the B-team meeting and make this presentation?)
about the beam's parity quality and any other remaining beam
issues. <br>
<br>
Thanks,<br>
Arne<br>
<h1 class="title">B-team Agenda<br>
</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-12-08
Wed 14:00</span></span> BTeam 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="Kazimi">Kazimi</span> <span class="Hofler">Hofler</span></span></h3>
<div class="outline-text-3" id="text-1.1">
</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 </h3>
<div class="outline-text-3" id="text-1.2">
<ul>
<li id="sec-1.2.1">Summary of Heat-Activate <br>
</li>
<li id="sec-1.2.2">Parity Quality Beam Status Report <span
class="tag"><span class="Qweak">Qweak</span></span><br>
</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>
Beam Studies Planning </h3>
<div class="outline-text-3" id="text-1.3">
</div>
</div>
<div id="outline-container-1.4" class="outline-3">
<h3 id="sec-1.4"><span class="section-number-3">1.4</span> BSY
Diagnostics <span class="tag"><span class="Benesch">Benesch</span></span></h3>
<div class="outline-text-3" id="text-1.4">
<p>Present updated table. B-team to prioritize the list
based on
desirability and known resource limits. The outcome of
this
discussion will be the plan that is executed.
</p>
</div>
</div>
<div id="outline-container-1.5" class="outline-3">
<h3 id="sec-1.5"><span class="section-number-3">1.5</span>
12GeV Pathlength Requirements Status <span class="tag"><span
class="Tiefenback">Tiefenback</span></span></h3>
<div class="outline-text-3" id="text-1.5">
<p>Update on requirements table and overall documentation
preparation.
</p>
</div>
</div>
<div id="outline-container-1.6" class="outline-3">
<h3 id="sec-1.6"><span class="section-number-3">1.6</span>
ARC1 model <span class="tag"><span class="Arne">Arne</span></span></h3>
<div class="outline-text-3" id="text-1.6">
<p>Results of the latest round of Arc1 modeling. </p>
</div>
</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">2010-12-01
Wed 14:00</span></span> BTeam Meeting–Notes </h2>
<div class="outline-text-2" id="text-2">
</div>
<div id="outline-container-2.1" class="outline-3">
<h3 id="sec-2.1"><span class="section-number-3">2.1</span>
Optics-on-Call Report: Hofler </h3>
<div class="outline-text-3" id="text-2.1">
<p>Summary of the thankful week
</p>
<p>
Fri: Hall C Compton scan – done.
</p>
<p>
Weekend: Energy stability problems, gang phase lock still
a problem? A power cycle may be required; readback may
be invalid; also an observed current dependence in
tracking.
</p>
<p>
Wed: Hall C Compton backed out, halo counts up, fixed by
rephasing. Need to get back through Compton. Still an open
issue, should revisit after spot move on Thursday 12-02.
</p>
</div>
</div>
<div id="outline-container-2.2" class="outline-3">
<h3 id="sec-2.2"><span class="section-number-3">2.2</span>
Beam Studies Report: All </h3>
<div class="outline-text-3" id="text-2.2">
<ul>
<li id="sec-2.2.1">Pathlength Analysis: Yunn <br>
Status of the analysis effort of the tunnel
heating/pathlength
five-pass test in September, final report due next week.
Byung's
draft report is attached. Fig 1 shows slower cooling
than warming.
12 GeV conditions will likely give RF shift of 2-3
degrees/arc.
15F LCW rise was half of 12 GeV conditions; concrete
temp did not
asymptote. Should we reperform this study with a longer
test and/or
higher temperature? Is this enough data to draw
conclusions?
<p>
Should we get a baseline to separate out baseline
pathlength
changes vs temperature-driven changes? This is small
compared
to expected effect. Estimate that these are acceptable
but more
numbers on air/wall temp and air conditioning
required. Should
pull sensors for data and compare, and plan to deliver
conclusions
before winter break (Tief).
</p>
</li>
<li id="sec-2.2.2">Arc9 model calibration test: Roblin <br>
<a
href="http://opsweb.acc.jlab.org/CSUEApps/atlis/task/10511">ATLiS
entry 10511</a>. Multiple RF FSD trips, ran fopt three
times, not
necessarily complete, requires data quality review by
Yves.
</li>
<li id="sec-2.2.3">Hall C double peak source
found/resolved? Suleiman <br>
<a
href="http://opweb.acc.jlab.org/CSUEApps/elog/entry/1555706?PHPSESSID=eba0eb97d22d5f6c7ee0b57e9c387545">See
this elog entry</a>. Can we get a
troubleshooting/diagnostic?
Or have we lost some troubleshooting for low current by
turning
off the beam scraping monitor? It is a useful archived
diagnostic
and should evaluate whether we can turn it back on in
future.
We should ensure that it stays off until we want it back
on.
Was also used as low-level transfer function monitor,
monitoring
for changes in lattice. We will return to this in the
future to
see if it can be acceptably turned back on. We'll modify
app and
send signals to Qweak for monitoring in the meantime.
</li>
</ul>
</div>
</div>
<div id="outline-container-2.3" class="outline-3">
<h3 id="sec-2.3"><span class="section-number-3">2.3</span>
Beam Studies Planning: All </h3>
<div class="outline-text-3" id="text-2.3">
<ul>
<li id="sec-2.3.1">Thursday 2010-12-02 and Tuesday
2010-12-07 Plans: Suggested <br>
<ul>
<li id="sec-2.3.1.1">Tuesday 2010-12-07 <br>
CHL power switch uncertainties, injector cathode
activation (~12h).
TPE also scheduled to start operations at start of
evening shift.
</li>
<li id="sec-2.3.1.2">Compton backgrounds (hall A) <br>
</li>
<li id="sec-2.3.1.3">Injector development for Hall
C/Qweak (Dalton, Benesch), ~4h (to 12h?) <br>
<a
href="http://opsweb.acc.jlab.org/CSUEApps/atlis/task/10271">ATLiS
entry 10271</a>, Rebalance systematics, RHWP
scans/PC translation scans.
Was done before but with IHWP in wrong orientation.
Oops! May require
some time both days.
<p>
Estimate 4h Thu 12-02, 8h Tue 12-07 (laser table
in conjunction with
Cathode activation, total time 12h)
</p>
</li>
<li id="sec-2.3.1.4">One pass stripline BPM test, ~1h
<br>
<a
href="http://opsweb.acc.jlab.org/CSUEApps/atlis/task/10445">ATLiS
entry 10445</a>, Large dynamic range of currents
(100uA to >=100 nA CW)
for BPM linearity test. Access required, not time
critical; can wait
for next access.
</li>
<li id="sec-2.3.1.5">Repeat of Arc9 model calibration
test?, ~2h <br>
<a
href="http://opsweb.acc.jlab.org/CSUEApps/atlis/task/10511">ATLiS
entry 10511,</a> should wait for Yves evaluation
of existing data to see
if its enough for his analysis.
</li>
<li id="sec-2.3.1.6">Cryomodule JT valve test?, ~10h <br>
<a
href="http://opsweb.acc.jlab.org/CSUEApps/atlis/task/7874">ATLiS
entry 7874</a>, Has been lingering since June.
Requires beam off.
Also requires Jonathan Creel's availability.
</li>
</ul>
</li>
<li id="sec-2.3.2">Thursday 2010-12-02 Plans: Decided <br>
<ul>
<li id="sec-2.3.2.1">Move spot (0.5h) <br>
</li>
<li id="sec-2.3.2.2">Injector development for QWeak
(4h) <br>
</li>
<li id="sec-2.3.2.3">Compton background tuning
(0.5-1h) <br>
</li>
</ul>
</li>
<li id="sec-2.3.3">Tuesday 2010-12-07 Plans: Decided <br>
<ul>
<li id="sec-2.3.3.1">Injector development for QWeak,
laser table, cathode activation (8-12h) <br>
</li>
</ul>
</li>
</ul>
</div>
</div>
<div id="outline-container-2.4" class="outline-3">
<h3 id="sec-2.4"><span class="section-number-3">2.4</span>
FY11 BTeam Projects </h3>
<div class="outline-text-3" id="text-2.4">
<ul>
<li id="sec-2.4.1">BSY Diagnostics: Benesch <br>
Details of the FY11 BSY diagnostics effort: showed list
of 5 diagnostics
suggestions on overhead (FY11 diagnostic suggestions).
Discussions of
whether to relocate harps back to E03 crosses, or
install new crosses
in front of S10 girders for optics matching after each
recombiner for
12 GeV upgrade commissioning development.
<ul>
<li id="sec-2.4.1.1"><span class="todo TODO"> TODO</span>
ATLiS to test optics measurements at 1E03/2S10
(before Jan 2011 optics) <br>
</li>
<li id="sec-2.4.1.2"><span class="todo TODO"> TODO</span>
Work up detailed tabular strawman, cost/resource
estimates (Benesch) <br>
</li>
<li id="sec-2.4.1.3"><span class="todo TODO"> TODO</span>
Cross-check injector harp optics match measurement
consistency <br>
</li>
</ul>
</li>
</ul>
</div>
</div>
<div id="outline-container-2.5" class="outline-3">
<h3 id="sec-2.5"><span class="section-number-3">2.5</span>
Anything else? </h3>
<div class="outline-text-3" id="text-2.5">
<ul>
<li id="sec-2.5.1">Optics: Hofler, Kazimi <br>
</li>
</ul>
</div>
</div>
</div>
<div id="outline-container-3" class="outline-2">
<h2 id="sec-3"><span class="section-number-2">3</span> <span
class="timestamp-wrapper"> <span class="timestamp">2010-11-17
Wed 14:52</span></span> Agenda–Notes </h2>
<div class="outline-text-2" id="text-3">
</div>
<div id="outline-container-3.1" class="outline-3">
<h3 id="sec-3.1"><span class="section-number-3">3.1</span>
Optics-on-Call Report <span class="tag"><span
class="Spata">Spata</span></span></h3>
<div class="outline-text-3" id="text-3.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-3.2" class="outline-3">
<h3 id="sec-3.2"><span class="section-number-3">3.2</span>
Beam Studies Report <span class="tag"><span class="All">All</span></span></h3>
<div class="outline-text-3" id="text-3.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-3.2.1"><span class="done DONE"> DONE</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-3.2.2"><span class="done DONE"> DONE</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-3.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-3.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-3.3" class="outline-3">
<h3 id="sec-3.3"><span class="section-number-3">3.3</span>
FY11 Bteam Projects </h3>
<div class="outline-text-3" id="text-3.3">
<ul>
<li id="sec-3.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-3.3.1.1"><span class="done DONE"> DONE</span>
Analysis of the Sep. 2010 LCW heatrise test <span
class="tag"><span class="Krafft">Krafft</span> <span
class="ATTACH">ATTACH</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.
<p>
<span class="timestamp-wrapper"> <span
class="timestamp">2010-12-01 Wed</span></span><br>
Byung has analyzed the data and the results were
presented at the
B-team meeting. For Arc1 he observed about a
1degree of RF pathlength
increase for 1degree C in temperature rise. See
attached document.
Mark as done, although there are some suggested
improvements.
</p>
</li>
<li id="sec-3.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-3.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-3.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-3.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-3.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-3.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-3.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-3.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-3.3.4">Other 12GeV required projects? <br>
<ul>
<li id="sec-3.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-3.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-3.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-3.3.4.3.1"><span class="todo
INPROGRESS"> INPROGRESS</span> Present final
plan <span class="tag"><span class="Benesch">Benesch</span> <span
class="ATTACH">ATTACH</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.
<span class="timestamp-wrapper"> <span
class="timestamp">2010-12-01 Wed</span></span><br>
Jay present a table, see attached document.
Requested that he fill it
in a bit more and add priority.
</li>
</ul>
</li>
</ul>
</li>
</ul>
</div>
</div>
<div id="outline-container-3.4" class="outline-3">
<h3 id="sec-3.4"><span class="section-number-3">3.4</span>
Optics model update <span class="tag"><span class="Arne">Arne</span></span></h3>
<div class="outline-text-3" id="text-3.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-3.5" class="outline-3">
<h3 id="sec-3.5"><span class="section-number-3">3.5</span>
Anything else? </h3>
<div class="outline-text-3" id="text-3.5">
<ul>
<li id="sec-3.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-12-07 12:15:45 EST</p>
<p class="creator">HTML generated by org-mode 6.33x in emacs 23</p>
</div>
</div>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<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>