<!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>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<title>Arne's Journal</title>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="generator" content="Org-mode">
<meta name="generated" content="2011-10-12 11:05:48 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; }
.right {margin-left:auto; margin-right:0px; text-align:right;}
.left {margin-left:0px; margin-right:auto; text-align:left;}
.center {margin-left:auto; margin-right:auto; text-align:center;}
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; }
th.right { text-align:center; }
th.left { text-align:center; }
th.center { text-align:center; }
td.right { text-align:right; }
td.left { text-align:left; }
td.center { text-align:center; }
dt { font-weight: bold; }
div.figure { padding: 0.5em; }
div.figure p { text-align: center; }
textarea { overflow-x: auto; }
.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"> Below is an updated version of the Actions Items
that were distilled out of Jay's analysis of Unscheduled Tune
Time. Completed (yeah!) items include the ITV2C23 viewer move
and the Injector fOpt coil move. Items that have a chance (and
would really be disappointed if they are not) of being completed
before resumption of Physics include: Weekly system checks
protocol, IHA2C04 harp scans with B, and aperture check. Items
that have to deferred due to resource limitations include DDA
deployment and FastSEE improvements.<br>
<br>
Please review the notes (especially the recent comments), and
provide feedback updates if you have any.<br>
<br>
Thanks,<br>
Arne<br>
<br>
</div>
<title>Arne's Journal</title>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="generator" content="Org-mode">
<meta name="generated" content="2011-10-12 11:23:10 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; }
.right {margin-left:auto; margin-right:0px; text-align:right;}
.left {margin-left:0px; margin-right:auto; text-align:left;}
.center {margin-left:auto; margin-right:auto; text-align:center;}
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; }
th.right { text-align:center; }
th.left { text-align:center; }
th.center { text-align:center; }
td.right { text-align:right; }
td.left { text-align:left; }
td.center { text-align:center; }
dt { font-weight: bold; }
div.figure { padding: 0.5em; }
div.figure p { text-align: center; }
textarea { overflow-x: auto; }
.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 id="outline-container-1" class="outline-2">
<h2 id="sec-1"><a name="ID-40072377-19cd-4d7a-9418-c5db6d5924ea"
id="ID-40072377-19cd-4d7a-9418-c5db6d5924ea"></a><span
class="section-number-2">1</span> Unscheduled Tune Themes
<span class="tag"><span class="OPS">OPS</span> <span
class="SELECT">SELECT</span> <span class="Benesch">Benesch</span> <span
class="ATTACH">ATTACH</span></span></h2>
<div class="outline-text-2" id="text-1">
<p> <span class="timestamp-wrapper"> <span class="timestamp">2011-04-29
Fri 10:00</span></span><br>
Met with Jay, Steve and Randy to discuss Jay's summary of
two years worth of unscheduled tune time. Jay's notes are
attached. Here are the action items as discussed at the
meeting.
</p>
</div>
<div id="outline-container-1_1" class="outline-3">
<h3 id="sec-1_1"><span class="section-number-3">1.1</span>
Summary </h3>
<div class="outline-text-3" id="text-1_1">
<p> Out of 273 hours over two years of unscheduled tune
time, Jay managed to shoehorn 91% of the lost time into 11
different categories. This represents almost one lost week
per year due to unscheduled tuning. The Table below
summarizes Jay's classification which can be found in his
note (attached)
</p>
<table rules="groups" border="2" cellpadding="6"
cellspacing="0" frame="hsides">
<caption></caption>
<colgroup><col class="left"><col class="right">
</colgroup>
<thead>
<tr>
<th scope="col" class="left">what</th>
<th scope="col" class="right">how much</th>
</tr>
<tr>
<th scope="col" class="left"></th>
<th scope="col" class="right">lost time</th>
</tr>
<tr>
<th scope="col" class="left"></th>
<th scope="col" class="right">(hours)</th>
</tr>
</thead>
<tbody>
<tr>
<td class="left">B Beamsize</td>
<td class="right">83</td>
</tr>
<tr>
<td class="left">Dispersion/optics drift, cycle the
world events</td>
<td class="right">53</td>
</tr>
<tr>
<td class="left">A&C Background, including Compton</td>
<td class="right">47</td>
</tr>
<tr>
<td class="left">Extraction BLM trips/setup</td>
<td class="right">23</td>
</tr>
<tr>
<td class="left">Injector transmission</td>
<td class="right">15</td>
</tr>
<tr>
<td class="left">A&C beamsize</td>
<td class="right">12</td>
</tr>
<tr>
<td class="left">Pathlength maintenance</td>
<td class="right">6</td>
</tr>
<tr>
<td class="left">ILM0R04 trips (does not include Jan
2011 event)</td>
<td class="right">4</td>
</tr>
<tr>
<td class="left">shunt troubles/lambertsen stripes</td>
<td class="right">3</td>
</tr>
<tr>
<td class="left">ep ion chamber trips</td>
<td class="right">2</td>
</tr>
<tr>
<td class="left">Other</td>
<td class="right">25</td>
</tr>
</tbody>
<tbody>
<tr>
<td class="left">Total</td>
<td class="right">273</td>
</tr>
</tbody>
</table>
</div>
</div>
<div id="outline-container-1_2" class="outline-3">
<h3 id="sec-1_2"><span class="section-number-3">1.2</span>
Actionable Items </h3>
<div class="outline-text-3" id="text-1_2">
</div>
<div id="outline-container-1_2_1" class="outline-4">
<h4 id="sec-1_2_1"><span class="section-number-4">1.2.1</span>
<span class="todo TODO"> TODO</span> Extraction Region <span
class="tag"><span class="Todd">Todd</span> <span
class="Spata">Spata</span> <span class="Benesch">Benesch</span></span></h4>
<div class="outline-text-4" id="text-1_2_1">
<p> <span class="timestamp-wrapper"><span
class="timestamp-kwd">DEADLINE: </span> <span
class="timestamp">2011-12-16 Fri</span></span><br>
Evaluate possible improvements to the 12GeV extraction
design. This region results in more than one lost shift
per year of beam availability as OPS try to minimize BLM
trips in the extraction region. Possible improvements to
explore could include:
</p>
<ul>
<li>Larger bore quadrupole magnets </li>
<li>viewer upstream of the YB magnets
</li>
<li>BPM design optimized for the unique geometry that is
the extraction region
</li>
<li>Time of arrival monitor in extraction region? </li>
</ul>
<ul>
<li><span class="timestamp-wrapper"> <span
class="timestamp">2011-10-12 Wed 09:47</span></span>
No action yet. Probably will miss the deadline.
Reluctant to move deadline at this time. Need to
remind Krafft about this item. </li>
</ul>
</div>
</div>
<div id="outline-container-1_2_2" class="outline-4">
<h4 id="sec-1_2_2"><span class="section-number-4">1.2.2</span>
<span class="todo TODO"> TODO</span> FastSEE improvements
<span class="tag"><span class="Controls">Controls</span></span></h4>
<div class="outline-text-4" id="text-1_2_2">
<p> <span class="timestamp-wrapper"><span
class="timestamp-kwd">DEADLINE: </span> <span
class="timestamp">2012-02-06 Mon</span></span><br>
Adjustable display on all FastSEE graphs so that user
can zoom and investigate regions of interest in the
frequency spectrum (0-1000Hz is especially important). </p>
<ul>
<li><span class="timestamp-wrapper"> <span
class="timestamp">2011-10-12 Wed 09:40</span></span>
Due to over utilization of Bevins, this task missed
the initial deadline of <span
class="timestamp-wrapper"> <span class="timestamp">2011-10-03
Mon</span></span>. Adjusted deadline to <span
class="timestamp-wrapper"> <span class="timestamp">2012-02-06
Mon</span></span> so we can try to have this
system in place before the end of the 6GeV operations.
</li>
</ul>
</div>
</div>
<div id="outline-container-1_2_3" class="outline-4">
<h4 id="sec-1_2_3"><span class="section-number-4">1.2.3</span>
<span class="todo TODO"> TODO</span> DDA prototype
permanently installed on 0L03 <span class="tag"><span
class="Controls">Controls</span> <span class="Eng">Eng</span></span></h4>
<div class="outline-text-4" id="text-1_2_3">
<p> <span class="timestamp-wrapper"><span
class="timestamp-kwd">DEADLINE: </span> <span
class="timestamp">2012-01-03 Tue</span></span><br>
Install the prototype DDA on the injector full
cryomodules and train staff (Jay, Freeman, Freyberger?)
on how to extract the data.
</p>
<ul>
<li><span class="timestamp-wrapper"> <span
class="timestamp">2011-06-03 Fri 08:33</span></span>
Eng would probably want to install/deploy the next
generation DDA prototype boards. Can Controls support
this? </li>
<li><span class="timestamp-wrapper"> <span
class="timestamp">2011-10-12 Wed 11:16</span></span>
Due C100/g2p and other work, Trent doesn't have time
to support this. Moved deadline to first week in 2012.
</li>
</ul>
</div>
</div>
<div id="outline-container-1_2_4" class="outline-4">
<h4 id="sec-1_2_4"><span class="section-number-4">1.2.4</span>
<span class="done DONE"> DONE</span> Injector fOpt coils
<span class="tag"><span class="ME">ME</span> <span
class="Eng">Eng</span></span></h4>
<div class="outline-text-4" id="text-1_2_4">
<p> <span class="timestamp-wrapper"><span
class="timestamp-kwd">DEADLINE: </span> <span
class="timestamp">2011-10-03 Mon</span></span><br>
Replace the 60MeV region fOpt coils with MAT dipoles.
</p>
<ul>
<li><span class="timestamp-wrapper"> <span
class="timestamp">2011-10-12 Wed 09:49</span></span>
Work completed. In the process identified hardware
problem with AMS system, which has been resolved.
Decks need to be changed? Call it complete.
</li>
</ul>
</div>
</div>
<div id="outline-container-1_2_5" class="outline-4">
<h4 id="sec-1_2_5"><span class="section-number-4">1.2.5</span>
<span class="todo INPROGRESS"> INPROGRESS</span> Weekly
fOpt/systems check <span class="tag"><span
class="Alicia">Alicia</span> <span class="MikeM">MikeM</span> <span
class="Todd">Todd</span></span></h4>
<div class="outline-text-4" id="text-1_2_5">
<p> <span class="timestamp-wrapper"><span
class="timestamp-kwd">DEADLINE: </span> <span
class="timestamp">2011-11-02 Wed</span></span><br>
Perform a suite of beam/machine health checks at the
start of every beam studies. These studies should result
in data for the Optics-On-Call staff can analyze during
the beam studies period so that if there are issues they
can be addressed during the recovery from beam studies.
CASA/Ops should develop the suite. Such a list might
include: </p>
<ul>
<li>allsave
</li>
<li>fOpt to each hall before terminating beam for beam
studies
</li>
<li>Multiharp at the entrance to each hall?
</li>
<li>Pathlength check, tune mode, capture scope images
and put in log book.
</li>
<li>aperture check
</li>
<li>anything else.
</li>
</ul>
<ul>
<li><span class="timestamp-wrapper"> <span
class="timestamp">2011-10-12 Wed 09:50</span></span>
Todd, Alicia and Mike McC. are developing a plan.
Almost ready for release. Adjust deadline from <span
class="timestamp-wrapper"> <span class="timestamp">2011-10-03
Mon</span></span> to <span
class="timestamp-wrapper"> <span class="timestamp">2011-11-02
Wed</span></span> </li>
</ul>
</div>
</div>
<div id="outline-container-1_2_6" class="outline-4">
<h4 id="sec-1_2_6"><span class="section-number-4">1.2.6</span>
<span class="todo TODO"> TODO</span> Aperture check tool
<span class="tag"><span class="Controls">Controls</span></span></h4>
<div class="outline-text-4" id="text-1_2_6">
<p> <span class="timestamp-wrapper"><span
class="timestamp-kwd">DEADLINE: </span> <span
class="timestamp">2011-10-03 Mon</span></span><br>
Get the aperture check tool to work on RHEL in a manner
that is acceptable to OPS and Bteam. In other words, get
the aperture tool to work native on RHEL. Also make a
survey of what tools are still not ported from HP-UX to
RHEL.
</p>
<ul>
<li><span class="timestamp-wrapper"> <span
class="timestamp">2011-06-03 Fri 08:35</span></span>
Removed AHLA from the owner of this problem. This is
an edm/medm issue that is best resolved by
Carlino/Bevins. </li>
<li><span class="timestamp-wrapper"> <span
class="timestamp">2011-10-12 Wed 09:51</span></span>
No traction on this. </li>
</ul>
</div>
</div>
<div id="outline-container-1_2_7" class="outline-4">
<h4 id="sec-1_2_7"><span class="section-number-4">1.2.7</span>
<span class="todo TODO"> TODO</span> IHA2C04 harp scans
<span class="tag"><span class="Tief">Tief</span> <span
class="Mahoney">Mahoney</span> <span class="Arne">Arne</span></span></h4>
<div class="outline-text-4" id="text-1_2_7">
<p> <span class="timestamp-wrapper"><span
class="timestamp-kwd">DEADLINE: </span> <span
class="timestamp">2011-10-03 Mon</span></span><br>
Work out why tune mode beam cannot be sent to B
dumplette when Halls A/C are receiving CW beam. There is
something unique about Hall-B that forces the slit to be
in a certain range when operated with the dumplettes in.
</p>
<ul>
<li><span class="timestamp-wrapper"> <span
class="timestamp">2011-05-09 Mon 10:26</span></span>
Yan claims this is requirement is due to leakage from
A&C sufficient to trip the PSS. Even with the
dumplette in? This was a one time event? Yan thinks
this requirement came from OPS and is not a MPS/PSS
driven requirement. Follow up with up Yan. </li>
<li><span class="timestamp-wrapper"> <span
class="timestamp">2011-10-12 Wed 09:52</span></span>
This is my issue, need to have a conversation with
Mahoney. No adjustment of deadline.
</li>
</ul>
</div>
</div>
<div id="outline-container-1_2_8" class="outline-4">
<h4 id="sec-1_2_8"><span class="section-number-4">1.2.8</span>
<span class="done DONE"> DONE</span> Yag viewer at 2C23
move <span class="tag"><span class="Controls">Controls</span> <span
class="HallB">HallB</span> <span class="Eng">Eng</span> <span
class="Tief">Tief</span></span></h4>
<div class="outline-text-4" id="text-1_2_8">
<p> <span class="timestamp-wrapper"> <span
class="timestamp">2011-05-02 Mon 15:54</span></span><br>
Jay wants to move 2C23 viewer to 2C24 girder. Not sure
if this really a positive action or not. No stand. the
tagger harp is own stand. Not a quad girder. New stand
for IHA2C24 harp plus the new viewer. Need to see what
the 12GeV design has for this region. Do it now or wait
for 12GeV? Maybe HD-ICE requirements drive getting done
this summer.
</p>
<ul>
<li><span class="timestamp-wrapper"> <span
class="timestamp">2011-10-12 Wed 09:53</span></span>
Viewer has been moved. Since it used the same cabling,
the ITV2C23 is still known to the control system as
2C23 even though it is at the 2C24 location. Need to
touch base with Pam to see how hard it is to "make it
right" Apparently not hard all, already in motion.
</li>
</ul>
<ul>
<li id="sec-1_2_8_1"><span class="done DONE"> DONE</span>
Controls naming <span class="tag"><span
class="Arne">Arne</span> <span class="Controls">Controls</span></span><br>
<span class="timestamp-wrapper"><span
class="timestamp-kwd">DEADLINE: </span> <span
class="timestamp">2011-10-14 Fri</span></span><br>
Come to an agreement with controls for updated the
system to reflect the proper name.
<ul>
<li><span class="timestamp-wrapper"> <span
class="timestamp">2011-10-12 Wed 10:00</span></span>
Mike J. is already working on this. Will be
completed in about one week. </li>
</ul>
</li>
</ul>
<ul>
<li id="sec-1_2_8_2"><span class="done DONE"> DONE</span>
Make decision on 2C24 viewer <span class="tag"><span
class="Arne">Arne</span></span><br>
<span class="timestamp-wrapper"><span
class="timestamp-kwd">DEADLINE: </span> <span
class="timestamp">2011-05-16 Mon 10:36</span></span><br>
Get 12GeV decks to see if any modification made now
will stick through the 12GeV era. Talk to Tiefenback
APEL for Hall-B.
<ul>
<li><span class="timestamp-wrapper"> <span
class="timestamp">2011-06-03 Fri 08:37</span></span>
Decision is to proceed with this idea. Stepan is
in the loop and has agreed to let us redesign the
stick/cross to support a yag viewer that this
location. </li>
</ul>
</li>
</ul>
<ul>
<li id="sec-1_2_8_3">Present location of 2C23 yag viewer
<br>
<table rules="groups" border="2" cellpadding="6"
cellspacing="0" frame="hsides">
<caption></caption>
<colgroup><col class="left"><col class="right"><col
class="left">
</colgroup>
<thead>
<tr>
<th scope="col" class="left">what</th>
<th scope="col" class="right">pixel</th>
<th scope="col" class="left"></th>
</tr>
</thead>
<tbody>
<tr>
<td class="left">ITV2C23</td>
<td class="right">354.5</td>
<td class="left"></td>
</tr>
<tr>
<td class="left">IHA2C24</td>
<td class="right">470.5</td>
<td class="left">116.</td>
</tr>
<tr>
<td class="left">4270 mark</td>
<td class="right">287</td>
<td class="left"></td>
</tr>
<tr>
<td class="left">4280 MARK</td>
<td class="right">380.5</td>
<td class="left">93.5</td>
</tr>
</tbody>
</table>
<p> 9.35 PIXEL/FT, ITV2C23 is 12.4 feet upstream of
IHA2C24
</p>
</li>
</ul>
<ul>
<li id="sec-1_2_8_4">Pictures <br>
<ul>
<li id="sec-1_2_8_4_1">2C24 harp and radiator stick
<br>
<img src="cid:part1.08020103.03080903@jlab.org"
alt="data/2011-05-23_08-59-17_382.jpg">
</li>
</ul>
<ul>
<li id="sec-1_2_8_4_2">2C24 another view <br>
<img src="cid:part2.05060408.05020508@jlab.org"
alt="data/2011-05-23_09-05-07_788-0.jpg">
</li>
</ul>
<ul>
<li id="sec-1_2_8_4_3">ITV2C23 <br>
<img src="cid:part3.09040602.06010609@jlab.org"
alt="data/2011-05-23_09-05-07_788-1.jpg">
</li>
</ul>
<ul>
<li id="sec-1_2_8_4_4">another view <br>
<img src="cid:part4.03070804.05070006@jlab.org"
alt="data/2011-05-23_09-05-07_788-2.jpg">
<p> <span class="timestamp-wrapper"> <span
class="timestamp">2011-10-12 Wed 09:43</span></span><br>
No action on this as the EES FPGA group is
consumed with C100, g2p and other higher
priority tasks. In addition, recent work in
cleaning up the MO system has result in improved
performance of the IF. Hopefully, injector
performs well. But that was only one aspect of
this request. The other goal is to get the DDA
deployed and get some experience (outside of
Trent) in analyzing the data. Moved the deadline
from <span class="timestamp-wrapper"> <span
class="timestamp">2011-10-03 Mon</span></span>
to <span class="timestamp-wrapper"> <span
class="timestamp">2012-01-03 Tue</span></span>
</p>
</li>
</ul>
</li>
</ul>
</div>
</div>
</div>
</div>
<div id="postamble">
<p class="date">Date: 2011-10-12 11:23:10 EDT</p>
<p class="author">Author: Arne Freyberger</p>
<p class="creator">Org version 7.5 with Emacs version 23</p>
<a href="http://validator.w3.org/check?uri=referer">Validate
XHTML 1.0</a>
</div>
</div>
<pre class="moz-signature" cols="72">--
Arne Freyberger
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>
<br>
</body>
</html>