-
Ideal to look at FESA class readiness
-
Andy presents cavity control, beam control and beam based measurements
-
As HW will be ready close to the startup, we need to created FESA classes with APIs that can already be used in simulation mode so that OP can start integrating
-
Generic components are well advanced; timings, functions, acquisition
-
By end March RF wants to have all devices defined and instantiated so that they can be instantiated in the CCDB and LSA
-
Cavity control close to completion; next task will be a mock beam control interface and classes
-
Next, check FESA functions
-
Assume cavity control by March (including set-points and loops), beam control by April - we can start building Makerules
-
Need to foresee Functions FESA soon
-
VME crates powering up should be checked - (ACTION); Anthony has made sure that all crates are update with CC7 and all FESA classes have been upgraded to FESA3 --> this migration needs to be tested as well (ACTION - Anthony; go offline through list of legacy hardware to be tested)
-
Clock selection will be checked explicitly during clock selection - OP needs to be able to manage the settings - (ACTION - not to forget to manage this correctly, Guilia to follow up; Kevin to check with Fabio on application)
-
Long blow-up will be in a separate FESA class; for the long. blow-up we will have a similar interface as in the past; one continuous function now as we have more memory
-
FESA class forctionsions should be ready ; acquaition ready soon.
-
Giulia stressed to have one general buffer as well as one separate one for the SPSQC (ACTION - Andy to check if FESA classes need permanently allocated buffers to be able to push to post-mortem)
-
Wolfgang comments that all control for legacy beam observation whether this is covered - Guilia is planing to re-install what was installed.