larp ps2 budget guidance fy10
play

LARP PS2 Budget Guidance FY10 By Lab: k$ By Task: k$ LBNL 262 - PowerPoint PPT Presentation

LARP PS2 Budget Guidance FY10 By Lab: k$ By Task: k$ LBNL 262 Sp-Ch sim. 173 FNAL 39 Instabilities 130 BNL 133 e-Cloud 199 SLAC 237 feedback 40 Total: 671 IPM: 133 Total 675 By Lab & Project FY10 PersonYear tot SLAC


  1. LARP PS2 Budget Guidance FY10 By Lab: k$ By Task: k$ LBNL 262 Sp-Ch sim. 173 FNAL 39 Instabilities 130 BNL 133 e-Cloud 199 SLAC 237 feedback 40 Total: 671 IPM: 133 Total 675

  2. By Lab & Project FY10 PersonYear tot SLAC LBNL FNAL BNL Travel & M&S Space-charge tracking, collim 0.6 0 0.50 0.13 $ 15 Instability 0.5 0.5 0.0 0 $ 5 e-cloud 0.7 0.25 0.5 $ 15 Feedbacks 0.1 0.125 0.0 $ 5 IPM & Phase-space diagnostic 0.5 0 0.5 $ 8 Total FY10 2.5 0.875 1.0 0.13 0.5 $ 48 Note: Travel in general split evenly between participating labs (with FTE count !" 0)

  3. Scope Where we are today (supposedly): • Space-Charge – Setup model, 1st simulations, compare solvers, est. numerical stability. • Instabilities – 1st estimates single bunch: � wave, TMCI, Res. Wall, s/c impedance, IBS, mb growth rates • E-Cloud simulations – Refine build-up assessment, compare PS2-MI, initiate effect on beam (in dipoles), need to combine s/c & e-cloud simulations? • B-B Feedback Systems – Acquire parameters (esp. rf cavity), initial estimates. • IPM Development – (no activity in FY09)

  4. Scope for FY10 • Space-Charge – Long-term sim. W/ ML/I, Impact & Synergia, iterate as req’d. Begin studying mitigation measures, begin implementing energy ramp. • Instabilities – Build impedance model based on available data. Investigate components (based on ext. designs), s-b growth rates & characteristics of impedance. • E-Cloud simulations – E-Cloud impact on beam w/ uniform-focusing model, instab. Threshold, study parameter space, • B-B Feedback Systems – Acquire parameters (esp. rf cavity), initial estimates, conceptual design of f/b system. • IPM Development – Gather up & analyse specifications, estimate performance for state-of-the-art designs

  5. Project Lead Lead lab FY09 FY10 FY11 FY12 Perform long term simulations with ML/I, Impact, and Synergia to characterize space- Finalize & document charge effects on findings of space- beam shape. charge mitigation Implement PS2 model Comparisons and investigation. Write in ML/I, Impact, and checks between Design Report. Begin Synergia. Validate codes, update/iterate development of model, lattice parameters, necessary perform first space- especially rf as they infrastructure for charge simulations at become available, interface with injection (no ramp), interface with PS2 collimator design investigate design team. Begin Continue to iterate codes; model tests; solver parameters and investigation of space- with PS2 design team comparison between establish numerical charge mitigation on design codes; deliver stability of space- options (as per our parameters. Finalize & prototype with charge model, proposal, begin document findings on interface to at least Space-charge R. Ryne/P. compare results from development for beam-shape (halo) one collimator design Tracking & Collimation Spentzouris LBNL/FNAL different codes: incorporating ramp generation code Build impedance model using best First estimates of available data or from single bunch components of instabilities, existing machines, microwave, transverse numerical calculation Write impedance and mode coupling of impedance instabilities section in instabilities, evaluate components, e.g. rf the PS2 conceptual space charge bellows, kickers, design report. Begin impedance, intrabeam BPM’s, transitions, vacuum system scattering growth estimate single bunch hardware design rates, Resistive wall, growth rates and investigations (if Impedances & multi-bunch characteristics of Refine and iterate with possible/desired by Instabilities K. Bane SLAC transverse instability instabilities PS2 design group SLAC & CERN). Continue assessment of ecloud impact on beam for full ring with Refine assessments uniform-focusing of electron-cloud build- lattice model. up, Compare electron- Estimate threshold of cloud build-up at the e-cloud density. PS2 against MI Explore parameter Refine assessment of upgrade. Initiate space, Secondary impact of e-cloud on assessment of e- emission model, PS2 beam by incorporating cloud effect on beam design parameters a realistic lattice (dipoles only at first). are changing. Assess description. Ongoing Incorporate details of Assess need to ecloud mitigation re-assessments to the vacuum hardware combine space charge mechanisms. Initial continue as needed, into e-cloud with ecloud assessment ready by incl. assessment of assessments. Write e-Cloud Simulations M. Furman/M. Pivi LBNL/SLAC simulations June 2010, mitigation strategies. Design Report Acquire parameters (rf Couple-Bunch stability Conceptual design of cavities), initial studies - Conceptual feedback systems and Bunch-by-Bunch estimates of growth design of feedback kickers. Write Design Feedbacks C. Rivetta SLAC rates systems. Report. Analyze specs. Estimate performance Ionization Profile for state-of-the-art Select subsystems, Monitor R. de Maria BNL/SLAC designs conceptual designs Write Design Report

  6. CM13 Presentations • I’ll be soliciting a PS2 progress report by a CERN person (Riccardo qualifies :-). • I’d like to have progress updates for work done since CM12 for each subtask and updated plans for next 1/2 year. • I will be working with CERN colleagues to start defining the Design Report sections we plan to write & report on that. • I hope for and encourage technical discussions, and I expect to continue refining scope.

  7. PS2 Design Report Commitments • Interest by CERN & LARP for us to write applicable sections of the PS2 DR. • I have asked CERN for an outline – It is still early, so they may not have one yet – Nevertheless, a generic outline is not hard to write down • Agreeing to this is a commitment by LARP to deliver on time (late CY 2011). • Since LARP appears to be providing the required funding, this is a commitment by each of us also, to deliver (with a scope as we developed it last year). • It may be of advantage to codify this in an MOU (LARP-CERN)

  8. • Please review your scope & manpower allotment & make sure you are comfortable with both. Also ensure you are getting the support form your lab.

Recommend


More recommend