FESA S. Deghaye for the FESA team BE/CO

What happened since April? followed by “Our plans”

What happened since April Quick reminder of the original plan (CO 3 ) What we did: – Release of version – Training – Support – Preparation and release of version – RDA3 integration

FESA strategic planning ’13 (CO 3 approved version) Main goal in LS1: migrate as many FESA 2.10 classes as possible to FESA 3 Major milestones in 2013 – Feb: FESA3 v0.9 for early adopters (~20 classes) – 1 st of July: FESA3 v1.0 released for 32 & 64 bits – Sep: Stop new FESA2 developments – Oct: FESA3 v2.0-RC with RDA3 for early adopters – Dec: FESA3 v2.0 with RDA3 as main release

That was the plan… … and what we actually did was…

Release of version As agreed in C03 – development version for the Delivered on time but known missing features (e.g. timing domain data) => needed Dependencies: RDA2, new timing (TimDT) Support for Linux 32 and 64 bits only

Training Two courses available: – FESA Basics (2 days): basic FESA + dev environment – FESA Advanced (1 day) more advanced FESA features 12 persons per session in the CTC So far: – 5 sessions for Basics (~60 persons) – 3 sessions (4 th mid-Oct) for Advanced (~36 persons)

Support Support organised (rota - 1 week each) 430+ support requests/information requests – Wide range - from design to debug, from simple C++ problem to complex FESA behaviour +/- 16 issues a week!  Takes more than 1 FTE

Version Version released the 12 th of September Impacted all parts (model, DB, code gen, C++, plug-in) Contains many fixes/improvements e.g.: – Timing domain data support – The rolling buffer has been improved and some side-effects have been fixed. – Added C++ methods to ease migration – Improved release procedure (e.g. archi info) – Improved Controls TestBed integration for better overall quality – …

RDA3 integration Close contact with CMW team Involved in all the discussions Involved in the interim reports  Very good collaboration from FESA PoV August – Study how the RDA2 integration is done – First tests and prototypes with RDA3 – Result: running both RDA 2 & 3 in FESA 3 but no connection between RDA 3 and FESA

O UR P LANS for the rest of the year and early next year

Our plans - Main strategic goals Continue migration to FESA 3 – Support & Training – Limit new features RDA 3 integrations – V2.0.0-EA * with missing features ASAP – V2.0.0 before the dry runs Support ACCOR – Installations, dry runs… * Early Adopters

RDA3 Important change Affects: – C++ Framework – Code generation Very different API – more than a simple drop-in replacement – it’s C++ and XSLT…

RDA3 – the plan Integration (since 9 th of September) – Get scalars on simple class (custom code only) – Get scalars on simple class (generated code) – Get other types (array 1D, 2D) – Set scalars, array 1D & 2D (custom and generated code) – Subscription (USER only) – Navigator (RDA3 Java client) – Support for non-user selector (waiting for Timing) – FESA 3 class as a RDA3 client (waiting for CMW) FESA 3 V2.0.0-EA (early adopters) Breaking news !!! Geneva , 14:15 A successful get (actually 10 of them) was done on a FESA 3 class using RDA 3.

RDA3 – the risks Planning risk – We know what and who – We don’t know the technical problems awaiting – E.g. RDA3 namespaces (aliases, migration tool) ?!? – Early-Adopter version ASAP but not before end of October Technical risk – Bugs & sub-optimal impl. of the FESA3-RDA3 glue  Careful validation of the FESA server part (functional & non-functional)

ACCOR – Installations & dry runs Migration of operational devices from GM & FESA 2 to FESA 3 – first tests with Steen & co this week Navigator for operational FECs (S. Jackson) Ensure that FESA 3 can be used in dry runs Expert support to diagnose/fix problems on the fly during the dry runs Move of FESA 3 devices from one class version to another (manual intervention so far)

Major milestones FESA 3 version EA end of October FESA 3 version with latest improvements and fixes before version before the end of the year FESA 3 version early next year – Changelog of version is nothing but RDA3 Version hard deadline is 1 week before the Linac2 dry-run (Steen, Daniel Calcoen, Richard Scrivens) Keep the two branches alive until mid-14 (the longer the more expensive and error-prone)

Operational deployment of RDA3 FESA User guidelines 1.User releases his class with FESA 1.x (a.b.c) 2.User moves to FESA User releases new version (d.e.f) 4.User moves devices from a.b.c to the d.e.f, rebuilds and reboots the FEC. 5.User tests 6.If rollback is needed, reverse point 4

Dry run FESA3/RDA3 fall-back solution FESA 3 V 1.X FESA 3 V 2.X FESA Class A Dates are for illustrative purpose only FEC XYZ 2 RDA3 only Bug-fix release 1 week min deploy 01-Dec01-Feb01-May = release