<!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">
<font size="-1"><font face="Helvetica, Arial, sans-serif">FYI, the
Injector Autosteer has a feature to use a "gold" orbit saved by
the Injector experts...as opposed to the relative orbit. <br>
Michele<br>
</font></font><br>
On 4/19/2011 8:05 AM, Jay Benesch wrote:
<blockquote cite="mid:4DAD7A78.1090609@jlab.org" type="cite">
<pre wrap="">Assertions
1. with two high current halls the orbit is the weighted average of the
beam centroids
2. Qweak charge asymmetry is related, for reasons unknown, to the amount
of beam scraped off on A2
3. When Ops does a save with zero position it saves the relative orbit
for all BPMs
4. Injector autosteer relies on the relative orbit
Conjecture
0R04 trips may be related to the relative orbits of the A and C beams.
<a class="moz-txt-link-freetext" href="http://opweb.acc.jlab.org/CSUEApps/elog02/elog_item.php?elog_id=1579572">http://opweb.acc.jlab.org/CSUEApps/elog02/elog_item.php?elog_id=1579572</a>
Suggestions
"Zero position" option in SAVER should be modified from yes/no choice to
three choices:
a. zero position for injector "[0123]I", 0L, 0R
b. zero position for everything else
c. no ZP
Ops could choose any one or the a/b pair.
For restore, there could be a few more templates at the end under a BPM
restore "menu": injector, machine, hall A, hall B, hall C. Or people
could simply be required to continue to grep the needed BPMs when
restoring a relative orbit.
Jay
_______________________________________________
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>
</body>
</html>