Description
Broader discussion on the priorities and next objectives for the next years of pyAML collaboration. The aim is to discuss medium (6-12 months) and long-term goals (12-24 months) of pyAML. The outcome/minutes of this discussion will be used as input for the steering committee to define a roadmap for the project. Feedback on the work organisation should be given in this session. Possible points to discuss:
- Missing features/functionality
- Organisation of tests at different facilities
- Degree of integration with other existing tools (pySC, ophyd, etc.)
- Feedbacks (slow).
- Graphical user interfaces. Is this in the scope of pyAML or each facility could write a GUI in their prefered way that runs pyAML under the hood?
- Digital twin What kind of digital twin / virtual accelerator is in the scope of pyAML? We need something to run CI/CD pipelines with and something to assist in the manual testing during the development. Is HZB solution available and generic enough?
- Ecosystem development The idea is to develop the code in a modular way, separate in different repositories etc to allow labs to pick-and-choose what they want to use and be able to integrate with potential lab-specific tools and ways to do things without those things having to go into pyAML affecting all other labs. This is an idea used by other communities and an approach I think could solve many of our issues as well as allowing labs to gradually migrate from their existing tools to pyAML
Other aspects: - Feedback (human) on the development process so far, interactions, meeting organisation, GitHub projects, etc.
- Resources committed to the project
- Promotion of the project in the wider accelerator community
- Next workshop edition (what? where? when?)
- Renew/confirmation of steering committee (June 2026-June 2027)
- Maintainer list and coordinator roles