ABP Computing Working Group
X Buffat, L. Deniau, G. Iadarola, G. Rumolo
Home page:
https://twiki.cern.ch/twiki/bin/view/ABPComputing/WebHome
Composition and mandate:
https://twiki.cern.ch/twiki/bin/view/ABPComputing/Mandate
ABP Information meeting, 01/09/2016
Preamble
In the ABP Group, computational aspects are spread through all sections at different levels and
for diverse applications, with core expertise in
o
o
o
Establishment of models, in-house development and wide use of advanced optics and
beam dynamics simulation codes
•
Optics, lattice design, single particle tracking with nonlinearities, apertures, collimators, etc.
(MAD-X, SixTrack, MapClass, TRAIN)
•
Multi-particle tracking in presence of space charge, impedance sources, electron cloud, ions,
beam-beam, IBS (PyHEADTAIL, COMBI, FASTION, SIRE)
•
Multi-particle tracking suited for linear machines (Placet, PATH)
•
Vlasov solvers for collective effects (DELPHI)
In-house modeling and development, or use, of codes for specific CERN applications
and interfacing them to (our) beam dynamics codes
•
Calculations of beam coupling impedances and wake potentials (e.g. ImpedanceWake2D,
CST Particle Studio, HFSS)
•
Calculation of electron cloud formation (PyECLOUD)
•
Modeling of sources (plasma generation, extraction, IBSimu)
•
Calculation of space charge forces with or without tracking (PyORBIT, PATH)
In-house development of handy tools to enable or facilitate machine data extraction,
treatment, analysis (for all CERN accelerators)
2
Preamble
In the ABP Group, computational aspects are spread through all sections at different levels and
for diverse applications, with core expertise in
o
Establishment of models, in-house development and wide use of advanced optics and
beam dynamics simulation codes
•
o
o
Optics, lattice design, single particle tracking with nonlinearities, apertures, collimators, etc.
• Many
of these
in-house developed codes are used not
(MAD-X,
SixTrack,
MapClass)
•
only tracking
within in
ABP
– butofCERN-wide
and evensources,
world-wide
Multi-particle
presence
space charge, impedance
electron cloud, ions,
beam-beam,
IBS
(PyHEADTAIL,
COMBI,
FASTION,
TRAIN,
SIRE)
(MAD-X, SixTrack, PyHEADTAIL, PyECLOUD,
•
Multi-particle
tracking suited for linear
machines
(Placet)
ImpedanceWake2D,
Placet,
PATH)
•
Vlasov
for collectiveofeffects
(DELPHI)
• solvers
The outcomes
these
codes
are also what ABP often
interfaces itself with the ‘external world’
In-house modeling and development, or use, of codes for specific CERN applications
and interfacing them to (our) beam dynamics codes
•
⇒ Wherefrom
a desire
to ensure
of(e.g.
what
we
Calculations
of beam coupling
impedances
androbustness
wake potentials
ImpedanceWake2D,
CST Particle Studio, HFSS)
•
Calculation of electron cloud formation (PyECLOUD)
•
Modeling of sources (ask D. Küchler, S. Mattei)
•
Calculation of space charge forces with or without tracking (PyORBIT, PATH)
export (codes and results) by providing a dedicated
attention to this ABP core activity
In-house development of handy tools to enable or facilitate machine data extraction,
treatment, analysis (for all CERN accelerators)
3
Some generic goals that would motivate the existence of an
ABP Computing Working Group
o
To guarantee continuity and further development of computing expertise
concerning (directly or indirectly) beam dynamics
o
To help newcomers with
•
Straightforward guidelines to set up their computing environment and get
quickly started into their assignments
•
Complete information on the hardware resources they can rely on
o
To help developers build on existing bricks and avoid typical mistakes,
repetitions and duplications of tasks
o
To facilitate the cross-talk between different activities within beam dynamics
and collect their – separate and common – needs
o
To identify synergies with needs of other groups/departments and liaise to
the management and IT department
4
Possible means of the ABP Computing Working Group
o
o
Common and maintained platform to share information about
•
Existing software used/developed within ABP and responsible people, guidelines
to install and use it
•
Existing hardware resources to both run the above programs and further develop,
guidelines to obtain accounts and configure efficient working environments
•
Existing (planned or ongoing) projects to extend any of the above
Internal forum for an open discussion about
•
Arising computing matters (e.g. reports from ITUM meetings, IT news)
•
Present status and development of the existing codes – fostering
collaborations or combined efforts between different activities
− Physics cases covered and those requiring the extension of any of the existing tools,
leading to their prioritization driven by CERN needs but also in a broader context of
improving our understanding and making our modeling robust
− Identification of needs for upgrades of the software/hardware resources on the
medium and long term
o
Links with IT for feedback/information exchange (ITUM, specific link-person)
and with other groups within ATS sector for collaboration/synergy
5
Mandate of the ABP Computing Working Group
6
Wiki page of the ABP Computing Working Group
7
Wiki page of the ABP Computing Working Group
Beam Physics Software Tools
8
Wiki page of the ABP Computing Working Group
9
Wiki page of the ABP Computing Working Group
Computing Resources
10
Wiki page of the ABP Computing Working Group
11
Indico site the ABP Computing Working Group meetings
12
Indico site the ABP Computing Working Group meetings
13
Summary
o
o
Development of beam dynamics codes is a core activity of ABP in constant
evolution, there is a clear need to
•
Collect information on status quo and make it available
•
Reduce and optimise efforts for developers to make further contributions
•
Identify and prioritise needs for SW/HW upgrades + put forward a medium-long
term strategy in terms of resources
ABP Computing Working Group (ABP-CWG) has the mandate to follow up on
these items. First and next steps
•
Wiki page under development. Structure ready, awaits input from contributors
•
E-groups:
− A restricted one ([email protected]) with core members (mainly large scale
developers), who commit to provide support and ‘expert advice’
− A broad one ([email protected]) with open self-subscription policy for general
announcements, relevant news, invitations to meetings  Please subscribe
•
Bi-weekly meetings (Indico page) kicking off next month to discuss computing
matters + review codes, needs and perspectives
− Expect to take 10-12 months to go through all the codes
− Summer 2017 could be about the time to report in detail the ABP-CWG activity with
outcomes and recommendations – with intermediate/steering reports
14
abp-cwg-exp
LHC 8:30 meeting
15