ATF2 Software Review LAL June SHORT SUMMARY - Philip Bambade ATF2 weekly meeting July

Overall objectives Review requirements for ATF2 control & tuning software  Status ? Prioritise & organise software work as tasks within ATF2 collaboration Main sessions Introduction of project, commissioning plan and software requirements Review of on-going beam tuning simulation work Review of on-going control software development Planning of tuning software & controls interface Review of Flight Simulator project development  detailed & prioritised software task list to be shared broadly within ATF2 collaboration Flight Simulator teach-in session  demo + installation environments Organisation / management of software tasks & continued discussion Participants LAL & LAPP : Bambade, Bai, Brossard, Renier, Rimbault, White, Bolzon, Jérémie KEK : Kuroda, Okugi, Tauchi MAN + RHUL + UCL : Boogert, Gournaris + Webex (Oxford, CI, SLAC, CERN, KEK… )

Talks presented Introduction and aims of this meeting Overview of ATF2 goals and current construction status Expected hardware status + priority commissioning tasks Brief description of software task list being constructed A proposal to share & organise software work in ATF2 Overview of SAD tuning software and applications for ATF / ATF2 Organisation of ATF2 commissioning team Aspects of shift organisation in multi-partner team context Experimental procedure for IP beta-tuning / transport at 3 IP waists Tuning ATF2 at lower IP betas, goals and troubles FFS tuning with pre-calculated optical multi-knobs FFS trajectory correction algorithm & plans Experience with ATF EXT beta matching Fast feedback & FONT Integrated EXT+FFS dynamic & static BBA, feedback and tuning EXT dispersion and coupling correction update & V.4 ATF2 Optics (main new ATF2 EXT + FFS features) Laserwire & Cavity BPMs (s-band and c-band) High-availability power supplies for FFS IP Diagnostics & Summary of ATF controls infrastructure and KEK plans for ATF2 Link between ATF (VSYSTEM) and EPICS + further developments FFS Magnet mover system AML code development ATF2 Flight Simulator project & Description of software task list being constructed A user's first-time Flight Simulator experience at ATF in May Software Management issues and next steps P. Bambade, LAL T. Tauchi, KEK T. Okugi, KEK G. White, LAL & SLAC P. Bambade, LAL S. Kuroda, KEK T. Okugi, KEK P. Bambade, LAL S. Bai, LAL & IHEP R. Tomas, CERN Y. Renier, LAL T. Scarfe, Daresbury R. Appleby, Daresbury J. Resta Lopez, Oxford G. White, LAL & SLAC M. Woodley, SLAC S. Boogert, RHUL G. White, LAL & SLAC T. Okugi, KEK G. White, LAL & SLAC J. Nelson, SLAC S. Molloy, SLAC G. White, LAL & SLAC Y. Renier, LAL G. White, LAL & SLAC

A proposal to share & organise software work in ATF2 Define software task for given tuning / control goal as :  simulation study of concept & feasibility  application + control software specification and preparation  practical implementation in control room  update and improvement Team-driven responsibilities assigned throughout ATF2 collaboration by means of expressions of interest of institutes & individuals (supported by their institutes), including for the leader Task leader charged with coordinating the team and with reporting, later also prepare publication Large overlap with commissioning activity  reporting and management of software tasks within commissioning team led by Okugi Discuss completeness & appropriateness of task list, individual & group interests, possible assignments, overlap and commonalities among tasks In most cases, an individual can work on several tasks but should only lead one Taking on a task is both an individual & institute responsibility Ideal profile for task leader  PhD, post-doc or junior staff

General comments & what next ? Expressions of interest for software tasks  expected contributions to ATF2 from all or most collaborating institutes Some EoIs already made during meeting  more are being made now Software project list itself will also evolve as we progress EoI not just off-line simulation study  deliberate linkup to software tool for testing and implementation in the control room, by all collaborators EoIs strongly coupled to commissioning tasks, including also some hardware control software A main responsible or coordinator + convener per task will be named Agreement to pursue both “Flight Simulator” and traditional ATF control environment based on V-system  harmonious co-existence of dual scheme with common data base  aim to integrate into FS in future Tuning & control via FS shown feasible for (helped) first-time user ! EoIs for software & commissioning tasks will be discussed at next commissioning team meeting July 9, 2 pm KEK, 7 am CET  formation of some of the teams, led by the coordinators to be named