1. ABP Computing Working Group
X Buffat, L. Deniau, G. Iadarola, G. Rumolo
Home page:
Composition and mandate:
ABP Information meeting, 01/09/2016

2. Preamble
In the ABP Group, computational aspects are spread through all sections at different levels and for diverse applications, with core expertise in
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)

3. Preamble
In the ABP Group, computational aspects are spread through all sections at different levels and for diverse applications, with core expertise in
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)
Multi-particle tracking in presence of space charge, impedance sources, electron cloud, ions, beam-beam, IBS (PyHEADTAIL, COMBI, FASTION, TRAIN, SIRE)
Multi-particle tracking suited for linear machines (Placet)
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 (ask D. Küchler, S. Mattei)
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)
Many of these in-house developed codes are used not only within ABP – but CERN-wide and even world-wide (MAD-X, SixTrack, PyHEADTAIL, PyECLOUD, ImpedanceWake2D, Placet, PATH)
The outcomes of these codes are also what ABP often interfaces itself with the ‘external world’
Wherefrom a desire to ensure robustness of what we export (codes and results) by providing a dedicated attention to this ABP core activity
Apart from MAD-X, which has a long history of dedicated maintenance and module developers/keepers, etc. most of the other codes have been born and have grown rather randomly - mainly based on the good will of individuals to develop and disseminate properly
The outcomes of these codes are also what ABP often interfaces itself with the ‘external world’  we usually design, predict, interpret, suggest changes or simply reply to requests concerning beam dynamics aspects based on our simulations, …

4. Some generic goals that would motivate the existence of an ABP Computing Working Group
To guarantee continuity and further development of computing expertise concerning (directly or indirectly) beam dynamics
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
To help developers build on existing bricks and avoid typical mistakes, repetitions and duplications of tasks
To facilitate the cross-talk between different activities within beam dynamics and collect their – separate and common – needs
To identify synergies with needs of other groups/departments and liaise to the management and IT department

5. Possible means of the ABP Computing Working Group
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
Links with IT for feedback/information exchange (ITUM, specific link-person) and with other groups within ATS sector for collaboration/synergy

6. Mandate of the ABP Computing Working Group

7. Wiki page of the ABP Computing Working Group

8. Wiki page of the ABP Computing Working Group Beam Physics Software Tools
Based on Laurent’s survey in 2014, however list might be incomplete, so invite people to add items (if appropriate)
Also code responsibles are required to edit their codes (template available, just need to fill in the different fields). Code responsibles will be invited to present in the dedicated meetings

9. Wiki page of the ABP Computing Working Group

10. Wiki page of the ABP Computing Working Group Computing Resources

11. Wiki page of the ABP Computing Working Group

12. Indico site the ABP Computing Working Group meetings

13. Indico site the ABP Computing Working Group meetings

14. Summary
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 with core members (mainly large scale developers), who commit to provide support and ‘expert advice’
A broad one 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 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

15. abp-cwg-exp
LHC 8:30 meeting