<!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">
<div align="left">Proposed Agenda for Tomorrow's Bteam meeting.
I'll not be there, but assume someone will lead the effort. <br>
Arne<br>
</div>
<h1 class="title">B-team Meeting<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-11-10
Wed 14:00</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>
Ops-On-Call Report <span class="tag"><span class="Yuhong">Yuhong</span> <span
class="Tiefen">Tiefen</span></span></h3>
<div class="outline-text-3" id="text-1.1">
<ul>
<li id="sec-1.1.1">BPM issues in Hall-C <span
class="tag"><span class="Benesch">Benesch</span></span><br>
Could we have resolved this issues in a more timely
manner?
</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 and Planning </h3>
<div class="outline-text-3" id="text-1.2">
<ul>
<li id="sec-1.2.1">Issues establishing two wien setup <span
class="tag"><span class="Suleiman">Suleiman</span> <span
class="Poelker">Poelker</span></span><br>
</li>
<li id="sec-1.2.2">Plans for Thursday <span class="tag"><span
class="All">All</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>
Optics Model update <span class="tag"><span class="Arne">Arne</span></span></h3>
<div class="outline-text-3" id="text-1.3">
<p>I will be on my way to Chicago at the time of the
meeting. I've
reworked the model plan to prepare for the Jan recovery.
The goals
of this download/recovery will be to have the quad values
in the
machine to be based on the elegant model. The elegant
model is being
used to drive more and more applications and as such
discrepancies
between the high level applications and the machine more
often than
not reflect a small difference between the Optim values
and the
elegant values. This can lead to some confusion.
</p>
<p>
The plan calls for a deck review in mid-December so that
we are ready
to go for Jan restoration.
</p>
</div>
</div>
<div id="outline-container-1.4" class="outline-3">
<h3 id="sec-1.4"><span class="section-number-3">1.4</span>
CASA Projects FY11 and beyond <span class="tag"><span
class="CASA">CASA</span></span></h3>
<div class="outline-text-3" id="text-1.4">
</div>
</div>
<div id="outline-container-1.5" class="outline-3">
<h3 id="sec-1.5"><span class="section-number-3">1.5</span>
6-month recovery plans <span class="tag"><span
class="Spata">Spata</span></span></h3>
<div class="outline-text-3" id="text-1.5">
</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-11-03
Wed 14:00</span></span> Agenda–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 Summary <span class="tag"><span
class="Alex">Alex</span></span></h3>
<div class="outline-text-3" id="text-2.1">
<p>Alex will summaries machine and beam optics issues over
the past seven
days. </p>
<ul>
<li>
Uneventful week
</li>
<li>
Instrumentation issues with HallB
</li>
<li>
HallC valve closed during beam delivery
<ul>
<li>
Valve is now "unmaskable"
</li>
</ul>
</li>
<li id="sec-2.1.1">Discussion <br>
<ul>
<li id="sec-2.1.1.1">pA runs in Hall-B <br>
<ul>
<li>
HallB has been unable to take low current
calibration runs due to
unacceptable backgrounds and unstable current at
these low currents.
</li>
<li>
present slit is at 17.5
</li>
<li>
present attenuator is at 100'ish
</li>
<li>
Presently the attenuator is being used to lower
the current.
Suggestion is to use the slit to lower the
current. So far OPS has
been reluctant to use this approach.
</li>
<li>
Adjust phase appropriately.
</li>
<li>
Do not expect current lock to work with
attenuator below 100.
</li>
</ul>
</li>
<li id="sec-2.1.1.2">M56 in the machine <br>
<ul>
<li>
Pathlength calibration revealed that there was a
small amount of M56
in the machine. Starts in Arc1.
</li>
<li>
Should we fix this? yes!
</li>
<li>
proposal is to tack this on to the end of the
Wien setup/150μ A
injector setup tomorrow.
<ul>
<li>
Spata will lead the effort.
</li>
<li>
This activity will take place if the
Vertical Wien setup goes
exceptionally well tomorrow.
</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
</ul>
</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 </h3>
<div class="outline-text-3" id="text-2.2">
<ul>
<li id="sec-2.2.1">Two wien calibration <span
class="tag"><span class="Poelker">Poelker</span></span><br>
Calibration with 130keV incoming KE. Final setup
tomorrow for QWeak.
<ul>
<li>
when does QWeak really need polarized beam?
</li>
<li>
Two Wien flipper will not work at energies higher
than 130keV.
</li>
<li>
would like a plan from QWeak on spin orientation
configurations for
the upcoming months. </li>
</ul>
</li>
<li id="sec-2.2.2">QWeak Inj. studies <span class="tag"><span
class="Dalton">Dalton</span></span><br>
<ul>
<li>
spent time searching for 60Hz noise in Injector.
Data collected,
analysis is on going. </li>
<li>
Hope to provide some plots soon. Plots will be
posted in the POLOG.
</li>
<li>
Need more in the injector for Cathode scans. Will
request 1/2 shift
every other week. </li>
</ul>
</li>
<li id="sec-2.2.3">BPM R&D Report <span class="tag"><span
class="Spata">Spata</span></span><br>
Summary of previous beam studies and 9am meeting on the
proposed
stripline BPM design.
Meeting on the stripline design for ArcA and Hall-D.
<ul>
<li>
estimates of the impact of synchrotron radiation
appear to be
negligible. 0.1% change in the signal pick up. </li>
<li>
requested a large gap +/- 5mm
</li>
<li>
Still one more design/fab iteration is needed before
submitted
procurement packages.
</li>
<li>
tech-note preparation is in progress. </li>
<li>
develop a plan to install one or two in Arc9 during
the 6-month
down. </li>
</ul>
</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>
AHLA FY11 Projects <span class="tag"><span class="Arne">Arne</span></span></h3>
<div class="outline-text-3" id="text-2.3">
<p>Summary of the AHLA projects for FY11. Below is the table
of all the
projects presently known, planned and unplanned. Some
projects have
"OPS Charters" written and having a charter accommodates
the planning
process. The OPS charter template is attached.
</p>
<ul>
<li id="sec-2.3.1">OPS Project Table <br>
<table border="2" cellpadding="6" cellspacing="0"
frame="hsides" rules="groups">
<caption></caption>
<colgroup><col align="left"><col align="left"><col
align="left"><col align="left"><col align="left">
</colgroup>
<thead>
<tr>
<th scope="col">Owner</th>
<th scope="col">Project</th>
<th scope="col"></th>
<th scope="col">Years</th>
<th scope="col">Resources</th>
</tr>
</thead>
<tbody>
<tr>
<td>AHLA</td>
<td><a>Full<sub>Inj</sub><sub>Energy</sub><sub>Upgrade</sub></a></td>
<td>AIP</td>
<td>FY11/FY12/FY113</td>
<td>AHLA/SRF/Controls/ENG</td>
</tr>
<tr>
<td>AHLA</td>
<td><a>6GeV<sub>model</sub></a></td>
<td></td>
<td>FY11/FY12</td>
<td>AHLA/CASA</td>
</tr>
<tr>
<td>AHLA</td>
<td><a>CDEV<sub>Replacement</sub></a></td>
<td></td>
<td>FY11</td>
<td>AHLA/Controls</td>
</tr>
<tr>
<td>AHLA</td>
<td><a>CED</a></td>
<td></td>
<td>FY11</td>
<td>AHLA/Controls/ENG</td>
</tr>
<tr>
<td>AHLA</td>
<td><a>CED<sub>Conversion</sub></a></td>
<td></td>
<td>FY11/FY12/FY13</td>
<td>AHLA</td>
</tr>
<tr>
<td>AHLA</td>
<td>Optical Diffraction Monitor</td>
<td></td>
<td>FY12/FY13</td>
<td>AHLA/CASA/Eng/Controls</td>
</tr>
<tr>
<td></td>
<td>Krest</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td></td>
<td>Lem Upgrade (heat management)</td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
<tbody>
<tr>
<td>AHLA/Cntrl/Eng</td>
<td>Timing System</td>
<td>AIP</td>
<td>FY14/FY15/FY16</td>
<td></td>
</tr>
</tbody>
<tbody>
<tr>
<td>Controls</td>
<td><a>DisplayWallReplacement</a></td>
<td></td>
<td>FY11</td>
<td>Controls</td>
</tr>
<tr>
<td>Controls</td>
<td><a>ImageManagement</a></td>
<td>AIP</td>
<td>FY11</td>
<td>Controls/ENG?</td>
</tr>
<tr>
<td>Controls</td>
<td><a>InsertionDeviceManager</a></td>
<td></td>
<td>FY11/FY12</td>
<td>Controls/ENG</td>
</tr>
<tr>
<td>Controls</td>
<td><a>NextGenerationIocHardware</a></td>
<td></td>
<td>FY11</td>
<td>Controls</td>
</tr>
<tr>
<td></td>
<td>Capfast Replacement</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td></td>
<td>Low Level Controls CED integration</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td></td>
<td>Low Level Software Management</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td></td>
<td>C25/C50 RF micro-controller
compilation/linking</td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
<tbody>
<tr>
<td>O'bility</td>
<td>MCC conference room technology</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td></td>
<td>Documentation Vision out to 2020</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td></td>
<td>Sing the 8am electric</td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
<tbody>
<tr>
<td>Eng</td>
<td>CAMAC → VME (East Arc)</td>
<td></td>
<td>FY10/FY11</td>
<td>Controls</td>
</tr>
<tr>
<td></td>
<td>New Harp electronics design</td>
<td></td>
<td>FY11</td>
<td>Controls</td>
</tr>
<tr>
<td></td>
<td>BLM HV upgrade</td>
<td></td>
<td>FY10/FY11</td>
<td>Controls</td>
</tr>
<tr>
<td></td>
<td>TRIM-II</td>
<td></td>
<td>FY10</td>
<td></td>
</tr>
<tr>
<td></td>
<td>Analog Blocks</td>
<td></td>
<td>FY10</td>
<td></td>
</tr>
<tr>
<td></td>
<td>Replace existing low-level RF hardware</td>
<td>AIP?</td>
<td></td>
<td>Controls</td>
</tr>
<tr>
<td></td>
<td>PSS Upgrade</td>
<td></td>
<td>FY11/FY12?</td>
<td></td>
</tr>
<tr>
<td></td>
<td>New Klystrons</td>
<td></td>
<td>FY12/FY13</td>
<td></td>
</tr>
</tbody>
<tbody>
<tr>
<td>OPS</td>
<td>training system</td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
<tbody>
<tr>
<td></td>
<td>Status Marquee</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>AIP</td>
<td>Beam Dump Diagnostics</td>
<td>AIP</td>
<td>FY14/FY15</td>
<td></td>
</tr>
<tr>
<td>Source</td>
<td>Positron</td>
<td></td>
<td>FY11</td>
<td>Eng/Controls/Physics</td>
</tr>
<tr>
<td>HallA</td>
<td>g2p</td>
<td></td>
<td>FY11</td>
<td>Eng/Controls</td>
</tr>
</tbody>
</table>
</li>
<li id="sec-2.3.2">Discussion of elegant model <br>
A sequential approach, doing one arc or one pass at a
time with one
week of integration results in the elegant modeling
effort finish just
in time for the May 13 end of the run. See Gantt chart
below:
<img src="cid:part1.06040006.03070102@jlab.org"
alt="data/model_gantt.jpeg">
<p>
Perhaps a more efficient use of beam time would be to
use the first
few days after the winter down to download and tune
the entire
machine. A plan based on this approach will be
developed. The
drawback of this approach is that lessons learned in
Arc1 cannot be
fed into the Arc2 plan. </p>
<p>
A new plan will be developed with the goal of loading
a complete set
of optics based on elegant model after the winter
down.
</p>
</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>
CASA FY11 Projects <span class="tag"><span class="CASA">CASA</span></span></h3>
<div class="outline-text-3" id="text-2.4">
<p>Discussion of CASA FY11 Projects and needs.
</p>
<ul>
<li>
BBU studies
</li>
<li>
Chebyshev multipole extraction
</li>
<li id="sec-2.4.1">No time for discussion. Comments: <br>
Next week CASA should present a list of CEBAF related
projects that
they would like to see action on in FY11 (and FY12).
<p>
Comment: A charter on the development of tools
required to make MO
frequency adjustment for pathlength controls should be
written. </p>
</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>
6-month down restoration discussion and team formation <span
class="tag"><span class="CASA">CASA</span> <span
class="SOURCE">SOURCE</span> <span class="ENG">ENG</span> <span
class="OPS">OPS</span></span></h3>
<div class="outline-text-3" id="text-2.5">
<p>Discussion how to prepare for restoration after the
6-month down and
successful positron experiment. This discussion did not
take place.
It will take place next week.
</p>
</div>
</div>
</div>
<div id="postamble">
<p class="date"> Date: 2010-11-09 16:53:39 EST</p>
<p class="creator">HTML generated by org-mode 6.33x in emacs 23</p>
</div>
</div>
<br>
</body>
</html>