1. MPE and BE-CO Collaborations  MPE and BE-CO collaborations Jean-Christophe Garnier 01/12/2015 On behalf of TE-MPE

2. MPE and BE-CO Collaborations Introduction  Overall good collaboration about Software services  Grateful to have the opportunity to  Identify shortcomings  Trigger discussion to target improvements 17/11/20152

3. MPE and BE-CO Collaborations Outline  Going through all the projects where we worked together  Trying to address the various questions brought forward by organizers where applicable 01/12/20153

4. MPE and BE-CO Collaborations WorldFIP for QPS  Very good communication and support for doubling of QPS WorldFIP infrastructure (now 88 segments in total) during LS1  Nice pre-emptive actions and assistance for diagnostics  MPE has strong interest in developments for future radiation tolerant fieldbus 01/12/20154 IP3 IP4

5. MPE and BE-CO Collaborations FECs and Drivers  BIS smoothly migrated to MENA20 with Encore driver  SMP migration to MENA20 currently in progress  FMCM migration to MENA20 or Industrial PCs was more chaotic  New RS422 driver seemed non mature  Blocking calls disappeared…  At first, didn’t support the FMCM baud rate  This triggered a lot of development to put the old FESA class back into an acceptable state of quality  Good support 01/12/20155

6. MPE and BE-CO Collaborations FESA  Ambitious plan:  FESA2 EOL (initially) announced for December 2015  Tentative migrations in summers 2012 and 2013 for BIS, SMP and FMCM classes  FESA3 not mature enough at the time  Postponed for LS2 to focus on other topics 01/12/20156

7. MPE and BE-CO Collaborations FESA  QPS FESA class migrated by 1 engineer (BE-OP) fully dedicated over 2 years  Pre-requisite for Machine Protection QPS Configuration Management in LSA  Difficult to plan/predict the effort required  Once on the way to FESA3, no back-up plan!  Likely helped improving the quality of FESA3 with the user feedback  Quality of the implementations?  Difficult to verify and validate the proper functioning of the QPS system in parallel to the supervision development on FESA3 01/12/20157

8. MPE and BE-CO Collaborations FESA Collaborations  Integration of PM support into FESA framework  Nice 1 st iteration  To be continued  Future pair-programming possibilities between MPE and FESA DEV teams for fast(er) migration of remaining classes 01/12/20158

9. MPE and BE-CO Collaborations CMW  Chronology  June 2013: First release of CMW-RDA3 library  November 2013: First version of PM RDA3 library with RDA2 back-end  February 2014: AccTesting RDA3 API  September 2014 – March 2015: Hardware Commissioning  Required continuous effort  Changes in user requirements  In addition with non backward API/ABI compatibility issues 01/12/20159

10. MPE and BE-CO Collaborations CMW and Post Mortem  CMW RDA2 is a core component of PM  Good reactivity and troubleshooting support for PM communications  Collaboration to prepare the pure RDA3 Post Mortem data collection  Client library and front-end server implementations ready  Validation must be performed for time performance and throughput scaling  Purely upgrade, no new feature  Next Post Mortem steps with added value  Dynamic Load Balancing with CMW-RDA3? 01/12/201510

11. MPE and BE-CO Collaborations Hardware Commissioning  Productive collaboration with Roman and Adam to kick-start analysis framework project  Good collaboration for operational maintenance  HWC Sequencer communication with AccTesting  Post Mortem Analysis Framework 01/12/201511

12. MPE and BE-CO Collaborations Post Mortem  Responsibility distributed  Infrastructure: BE-CO  This year it took way too long delay to get new SPS servers …  Data Collection and Storage: TE-MPE  Analysis Framework: BE-CO / EN-ICE  Good collaboration but system vision is hardly complete for anyone  Impact of changes may be underestimated  XPOC analysis delays  Duplication of all PM files in SDDS, now reduced to FGC and QPS  Improvements to perform  Storage performance at the limit  Horizontal scalability to cover new use cases  Public API and way to work with data 01/12/201512

13. MPE and BE-CO Collaborations Data Analysis  Challenge of CALS and PM data analysis  Numerous Machine Protection/operational use cases (e.g. trends) not fully satisfied due to the limited extraction capabilities  Shift in paradigm on how to process large amount of data efficiently -> no data extraction but processing offloading  Shared research topic with PhD students about data storage, consolidation and analysis 01/12/201513

14. MPE and BE-CO Collaborations DIAMON for BIS and SMP  Change of philosophy between DIAMON1 and 2  No more plugins for user specific monitoring (diamon-agent)  Lot of efforts to put BIS and SMP in DIAMON 2  FESA properties are all encoded  Underestimated the impact on the integration  Still not entirely satisfying  Is it the right tool for (detailed) equipment monitoring?  Future steps  Simplify BIS and SMP JAPC interface – just started  Use DIAMON on top if possible 01/12/201514

15. MPE and BE-CO Collaborations Development Tools  Aim: improve productivity and quality of deliverables  Huge impact on our productivity and our mood  Adopting CBNG (too) early?  Huge improvement with our Continuous Delivery extension  Based on plain Bamboo, plain CBNG and plain Gradle  Automatic user acceptance tests  Semi-Automatic deployments of DBs, services and GUIs  Drawback  Lack of tests for changes in CBNG features and infrastructure  Bamboo CBNG configuration instabilities  Mainly due to lack of communication  Demanding user  More stable and much better nowadays, also thanks to improved communication between teams 01/12/201515

16. MPE and BE-CO Collaborations Development Tools  Very successful collaborations  SonarQube  SDC for Eclipse  What about extending it to other tools?  Providing support to our own equipment group 01/12/201516

17. MPE and BE-CO Collaborations Development from GPN  Is it a priority?  Could help improving machine availability  Non professional image to short term developers  No more development VMs  Numerous blockers  Absence of services: LSA  Or incomplete presence: CCDB, Post Mortem  Cumbersome configuration of certain libraries (JAPC)  Requires numerous test beds from equipment groups  Global effort -> appropriate focus  Reduced but complete infrastructure present on the GPN 01/12/201517

18. MPE and BE-CO Collaborations Outlook  Very well established collaboration and MPE is grateful about the opportunity to share openly about it -> Should continue!  Lessons  Non-backward compatible changes are (resource) intensive and must be avoided  If it cannot be, must be stable before equipment groups start their own developments, i.e. (well) before the shutdown  Better communication on both sides for project plans and planning to evaluate impact  Looking forward for collaboration on  Data Analysis developments  Planning LS2 together  JTech, JCoord 01/12/201518