1. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 1 VLT Control Software …and beyond

2. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 2 Agenda This presentation will give: An introduction to the structure of the VLT control SW from the perspective of teams developing an instrument We will see an overview of: The Where, the What and the Why The big picture and the philosophy. The main elements of the VLT Common Software and Instrumentation Software frameworks. What are the basic services provided? How can you find information, examples and help?

3. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 3 Where is the VLTSW used? VLT Unit Telescopes VLTI facilities VLT Auxiliary Telescopes VISTA VST 3.6 NTT……. All ESO optical telescopes and their instruments are based on the VLT Common Software and on the VLT Instrumentation Software

4. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 4 What is the VLTSW? The VLTSW is the implementation of a common infrastructure for the development of control applications. It consists of several layers: On the lower levels are APIs for the communication infrastructure and common general services At the higher level we have complete software frameworks Purpose of a framework is to: provide a programming model provide common paradigm abstractions mask heterogeneity satisfy performance, reliability and security requirements

5. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 5 Why the VLTSW? An infrastructure framework is the key to the separation between Functional and Technical Architecture Application developers care for the Functional Architecture: Responsibilities, interfaces and primary relationships and interactions between subsystems Physics and algorithms Hardware deployment and distribution The Technical Architecture is provided by the infrastructure team: Communication mechanisms, networking, general services Software deployment and activation Programming model

6. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 6 What are the advantages? If everybody uses a common framework: The architecture, design and implementation are uniform across systems This: Allows centralizing support Makes maintenance easier Ensure compatibility of technical interfaces Allows to reuse resources and skills on different projects Allows to propagate improvements automatically by distributing centralized changes.

7. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 7 Can we quantifying the advantages Can we measure the impact of adopting the VLTSW as a common infrastructure? Very difficult: all numbers are debatable But we have some good examples

8. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 8 Size of Instrumentation code reduced A.Longinotti, M.Kiekebush – 2008

9. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 9 Instrumentation Sw development time A.Longinotti – 2002

10. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 10 Size of Telescope Control Software reduced UT  VISTA: 2/3 less

11. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 11 WSF code generation A state machine model driven toolkit based on ESO VLT Software ProjectApplications based on WSF Average states per applications Average transitions per application Average lines of code per application % Hand-crafted code per application PRIMA1221722400421.24 APE12361053502025.08 NGC417341602117.31 DL126682439118.55 L.Andolfato, 2008 L.Andolfato – 2008

12. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 12 VLTSW Architecture Basic control architecture: Real Time on VME LCUs Coordination on Linux workstations Middleware with almost identical APIs: CCS on the workstation LCC on the LCUs

13. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 13 Middleware services CCS and LCC both provide: On-line database Message system Scan system Time System Logging System Error and Alarm System CCS provides: Event handling framework (EVH) Portable user interface toolkit Engineering User Interfaces LCC provides: Motor control Drivers (LCC) CCD support

14. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 14 Application frameworks LCU Server Framework (LSF) Allows implementing object oriented LCU applications with a standardized architecture based on C code templates. Workstation Software Framework (WSF) Allows implementing C++ workstation applications based on a finite state machine model INS Common Software The core topic of this workshop. Allows implementing a complete Instrumentation Control Software (both LCU and Workstation sides) configuring code templates.

15. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 15 Building blocks The VLTSW includes other essential building blocks: Telescope Control Software (TCS) The basic Telescope Control Software implementation, used as starting point from which all concrete instances of TCS inherit. Interferometer Supervisory Software (ISS) The Interferometer Supervisor Software is the central control instance of the VLTI facility. It forms the central interface of VLTI to the instruments and users High-level Operation Software (HOS) General purpose tools, allowing both technical and scientific staff to ease the definition and execution of sequences of commands, intended to control the telescopes and instruments. Software Engineering tools

16. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 16 Current core technologies Platforms: Workstation: PC with Linux OS LCU (real time): VME with VxWorks OS IO typically on the LCU backplane Languages: C for real time applications (LCU) C++ for high level coordination (WS) Tcl/Tk for scripting and GUIs Middleware: CCS and LCC based on HP RTAP, further developed in- house

17. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 17 History and evolution Development started ~15 years ago 1 new release per year Now the interfaces are extremely stable Workstation part migrated from Solaris to HP UX to Linux Middleware initially based on RTAP (HP commercial SCADA system) later on re-implemented in-house High level frameworks introduced in steps (EVH, LSF, WSF, INS) New standard devices introduced in steps (controllers, CCDs, sensors) Some components in 2008 and 2009: WSF, NGS, NTTCD, CanRMC, CLIP

18. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 18 Future developments The VLT/VLTI is going to be in operation probably for another 20 years Many instruments are still being implemented or are in the conceptual or design phase Software for the VLT will then be developed still for many years to come, as demonstrated by your interest in this workshop. At the same time, ESO is involved in other projects: ALMA and the E-ELT How will the VLTSW evolve in this context?

19. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 19 The VLTSW roadmap Giving an answer to this question is extremely difficult. There are very many parameters to take into account and advantages and disadvantages of each option need to be carefully weighted Here at ESO we have started a couple of months ago a process of analysis of these parameters It will still take some months before we will have been able to reach a concrete result: A VLTSW Roadmap in the era of ALMA and E-ELT

20. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 20 Some of the parameters in the game The current VLTSW can satisfy the requirements for new instruments (as far as we know and with few exceptions) Some software and hardware technologies are becoming obsolete and will have to be replaced. Some recent technologies promise to make new development more efficient and of higher quality Replacing what works has a cost and a risk to be weighted Refactoring based on the past experience should allow to simplify and improve the current architecture and design Sharing new developments with other projects (E-ELT) should allow early testing and sharing of resources

21. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 21 Examples of technologies Some examples of technologies that will be discussed: Devices and IO in the field: field busses vs. LCUs? Programming languages (Java? LabVIEW?) Model driven development and code generation? More extensive usage of PLCs (for example safety PLCs)? We will have a chance of discussing more these and other aspects in the final open session of this workshop. Think about these issues during the workshop and provide you feedback

22. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 22 Where to find information? This workshop will provide you with links and references The documentation for the exercise is a concise but complete tutorial for self- training The documentation for all VLTSW packages is available online: http://www.eso.org/projects/vlt/sw-dev/wwwdoc/VLT2008/dockit.html http://www.eso.org/projects/vlt/sw-dev/wwwdoc/VLT2008/dockit.html Read the first document in the first binder! The “Overview” provides a general view on the process of writing software for the VLT project. Read the documents in the INS section Read the “Guidelines for the Development of VLT Application Software” : ftp://ftp.eso.org/pub/vlt/vlt/pub/add-doc/JAN2006/VLT-MAN-ESO-17210-0667.pdf ftp://ftp.eso.org/pub/vlt/vlt/pub/add-doc/JAN2006/VLT-MAN-ESO-17210-0667.pdf Forums, discussions and FAQs: Forums: http://www.eso.org/phorum/index.php?9http://www.eso.org/phorum/index.php?9 Ask your contact person for support!!!

23. ESO - G.Chiozzi ESO Instrumentation Software Workshop 2008 - 23 Questions (& Answers)