[Bteam] Notes from today's meeting
Arne Freyberger
freyberg at jlab.org
Wed Nov 17 16:42:05 EST 2010
B-team Meeting Notes
1 2010-11-17 Wed 14:52 Agenda
1.1 Optics-on-Call Report Spata
the 9.6kHz vertical easter egg hunt
* present focus is on the pre-buncher as the source or amplifier of
the problem.
* Is there information to be gained by simulating or trying to
simulating the effect? CASA will look into this.
1.2 Beam Studies Report All
* M_56 issues, diagnostics and training. "The Friday Event"
o what is the design sensitivity of the device? 10mV/degree?
o Injector to north linac match came late in the game, but
match happened without too much issue.
* Two Wien setup
o nice setup, too bad we mucked it up my pulling the Vertical
Wien HV.
o 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.
* TODO form a RAR committee to investigate Thursday/Friday tune time
Krafft Arne
DEADLINE: 2010-11-19 Fri
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.
* TODO write charge to the committee Krafft Arne
DEADLINE: 2010-11-23 Tue
* Plans for Thursday and Tuesday Beam studies
o heat/activate schedule: To be determined by Thursday's QE
scan. (0.5h)
+ if needed to get through Thanksgiving, will do this on
Monday
+ otherwise defer to after Thanksgiving
o Re-instate the Vertical Wien (0.5h)
o Investigate pre-buncher electronics (1h)
o recalibrate the Vertical Wien
o Reestablish high current setup with max gradient of
pre-buncher of 2.0? depends on what they find with the
pre-buncher investigation.
o pre-buncher options
+ network analyze the output of the amplifiers
+ install more supplemental amplifiers
+ run with reduced amplitudes on the pre-buncher
1.3 FY11 Bteam Projects
* 12GeV Pathlength resolution
DEADLINE: 2010-12-20 Mon
finish off the 12GeV pathlength issues and get definitive answer
from 12GeV. Remaining issues:
o TODO Analysis of the Sep. 2010 LCW heatrise test Krafft
DEADLINE: 2010-12-06 Mon
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.
o TODO document Update/table with agreed upon requirements Tiefen
DEADLINE: 2010-12-06 Mon
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)
o TODO Transfer to 12GeV Pilat Arne Krafft
DEADLINE: 2010-12-20 Mon
* Pathlenth adjustment via MO frequency changes
Develop the requirements for this new tool so that
Eng/AHLA/Controls/OPS can work on developing a complete tool for
routine operations.
o TODO Draft of requirements Tiefen
DEADLINE: 2011-08-15 Mon
o TODO Project Charter written and team formed Tiefen
DEADLINE: 2011-09-19 Mon
o TODO Requirements review, reiterated upon and accepted BTEAM
DEADLINE: 2011-10-03 Mon
o TODO Project goals, milestones and work effort established
AHLA ENG OPS
DEADLINE: 2011-10-10 Mon
* raytrace
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.
* Other 12GeV required projects?
o shims on BW to test modeling of dog-leg
The shunts will be installed during the 6-months for
understanding dog-legs? Power supply management issue. Low
impact.
o Synchrotron light ports
Arc9, Arc8, Arc7, Arc10, four in each arcs. Arc8 would be
best to do this summer, at least the vacuum chambers.
+ estimate is about 17k per synchrotron port. Is this
just the vacuum chamber?
+ benefit would be continuous monitoring of the beam
+ perhaps need 80k this year to do Arc8.
+ 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.
o Moving harps around
completing the BSY diagnostic suite. This is funded as the
completion of the AIP BSY.
+ TODO Present final plan Benesch
DEADLINE: 2010-12-01 Wed
Include upgrading quad power supplies to aid
collecting quad scan data through the minimum.
1.4 Optics model update Arne
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.
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)
* Arc1 ala elegant
* 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.
1.5 Anything else?
* Optics-on-call over Thanksgiving? Krafft Hofler
Don't touch anything!
Date: 2010-11-17 16:40:07 EST
HTML generated by org-mode 6.33x in emacs 23
--
Director of Accelerator Operations
Jefferson Lab Office: (757) 269-6268
12000 Jefferson Avenue Cell: (757) 876-6289
Newport News, VA 23606 Email: freyberg at jlab.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/bteam/attachments/20101117/4dcf3f8e/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ARC1.pdf
Type: application/pdf
Size: 767934 bytes
Desc: not available
URL: <https://mailman.jlab.org/pipermail/bteam/attachments/20101117/4dcf3f8e/attachment-0002.pdf>
More information about the BTeam
mailing list