1. 1 Enabling technologies and constraints for software sharing in large astronomy projects G.Chiozzi – ESO, Germany A.Bridger – UK Astronomy Technology Centre, UK K.Gillies – Space Telescope Science Institute B.Goodrich, S.Wampler - National Solar Observatory, Tucson, AZ J.Johnson, K.McCann – W.M.Keck Observatory, Kamuela, HI G.Schumacher – National Optical Astronomy Observatories, La Serena, Chile

2. 2 Aspects analyzed Why are we now discussing sharing? Why are we now discussing sharing? What do we mean by software sharing? What do we mean by software sharing? Benefits of software sharing Benefits of software sharing Barriers to software sharing Barriers to software sharing Fostering reuse Fostering reuse Opportunities for sharing Opportunities for sharing Conclusion… or just the beginning? Conclusion… or just the beginning?

3. 3 The right time? 1990 2000 2005 2010 2015 2020 1995 VLT/VLTI Gemini N/S Keck ALMA LSST ATST E-ELT TMT

4. Software Sharing: what is it? 4 Reusing software assets Black box or white box Opportunistic or planned Horizontal or vertical

5. Benefits SW Engineers agree that sharing can bring major benefits: Improved productivity and quality while decreasing cost. Improved productivity and quality while decreasing cost. Saving time and money while achieving greater reliability Saving time and money while achieving greater reliability More effective use of domain experts More effective use of domain experts Building an improving knowledge base Building an improving knowledge base Improvements are propagated throughout all systems Improvements are propagated throughout all systems Standards can be developed and deployed Standards can be developed and deployed Reduced maintenance costs (shared maintenance and less code) Reduced maintenance costs (shared maintenance and less code) 5

6. … are they measurable? 6 Lines of code for TCS or ESO telescopes

7. … are they measurable (cont.)? 7 Reduction of lines of code for instruments

8. Barriers Technical: Technical: Functionality, programming language, OS Functionality, programming language, OS “Local” standards and data formats “Local” standards and data formats Sociological/project management: Sociological/project management: Timing between projects Timing between projects “Not invented here”, project culture “Not invented here”, project culture Cost and politics of sharing. Cost and politics of sharing. 8 The astronomical SW community: No significant track record No significant track record No mechanism No mechanism No critical mass No critical mass

9. Fostering reuse Open source practices: Open source practices: Solid core Solid core Process of contributing Process of contributing Connecting the community Connecting the community Understanding collaboration Understanding collaboration Recognition of creative nature Recognition of creative nature Community interest and management sponsorship Community interest and management sponsorship Working groups Working groups 9 Getting people involved: Getting people involved: Involve management, staff and “customers” Involve management, staff and “customers” Conferences and joint papers Conferences and joint papers Meetings in small groups, exchanges, sabbaticals Meetings in small groups, exchanges, sabbaticals Federating with related communities Federating with related communities

10. Opportunities for sharing 10

11. Opportunities for sharing (2) Software Engineering Standards Software Engineering Standards Coding, development, design and process Coding, development, design and process Design, knowledge and experience Design, knowledge and experience Similar architectural designs Similar architectural designs Library of domain patterns? Library of domain patterns? Knowledge base for astronomical control SW engineers? Knowledge base for astronomical control SW engineers? 11

12. Opportunities for sharing (3) Functional Interface Standards Functional Interface Standards Very similar observatory’s SW architecture Very similar observatory’s SW architecture Should be possible to standardize functional interfaces Should be possible to standardize functional interfaces Why is there NO generic and portable TCS? Why is there NO generic and portable TCS? Data Interface Standards Data Interface Standards Data structures are often hidden behind functional IF Data structures are often hidden behind functional IF Is it possible to standardize instrument configuration or the configuration of some subsystems? Is it possible to standardize instrument configuration or the configuration of some subsystems? Project Data Model? User Database? Project Data Model? User Database? The Data Handling community is ahead (FITS)! The Data Handling community is ahead (FITS)! But do we have the requirement? But do we have the requirement? 12

13. Opportunities for sharing (4) Middleware and infrastructure Middleware and infrastructure Common services Common services Hide distribution and heterogeneity Hide distribution and heterogeneity Is a common infrastructure feasible? Is a common infrastructure feasible? Should we put up a working group? Should we put up a working group? Software packages Software packages There are a number of packages in use (sla, cfitsio) There are a number of packages in use (sla, cfitsio) Need tools to collect, review and discuss packages Need tools to collect, review and discuss packages 13

14. 14 Conclusion We do not want to develop yet another infrastructure We do not want to develop yet another infrastructure We want to concentrate on our domain work We want to concentrate on our domain work We have analyzed different means for sharing, depending on the context We have analyzed different means for sharing, depending on the context We have seen that collaborations are now more practical and affordable than ever We have seen that collaborations are now more practical and affordable than ever We aim at: We aim at: Sharing lessons learned Sharing lessons learned Identifying areas for greater cooperation Identifying areas for greater cooperation We dream of broad scale, component based, reuse We dream of broad scale, component based, reuse How do we get there?..... …let’s discuss it all together at the “round table”!……

15. 15 Questions? We represent just a tiny subset of the projects in astronomy. Many more colleagues in the astronomical observatory community have given their ideas and time as we have developed this paper. We want to thank in particular Dave Silva and Anders Wallander for their participation and essential contribution to these discussions in the last year. Contact: gchiozzi@eso.org In the paper you can find an interesting bibliography!

16. 16 OPEN DISCUSSION Creating an open software community for observatory control and operation: Is it possible? Is it worthwhile?

17. What is the right path? Is this a good idea, in practice? Is this a good idea, in practice? What can/should we do? What can/should we do? How? How? Who would like to join in the effort? Who would like to join in the effort? The next steps? The next steps? 17

18. Opportunities for sharing Software Engineering Standards Software Engineering Standards Design, knowledge and experience Design, knowledge and experience Functional Interface Standards Functional Interface Standards Data Interface Standards Data Interface Standards Middleware and infrastructure Middleware and infrastructure Software packages Software packages 18

19. 19 OPEN DISCUSSION Creating an open software community for observatory control and operation: Is it possible? Is it worthwhile? Summary!

20. The discussion Is this a good idea? Yes it is! 20 ~120 people

21. Highlight quotes We DO LIKE to reuse what we do NOT LIKE to do ourselves We DO LIKE to reuse what we do NOT LIKE to do ourselves Analyze first what succeeded Analyze first what succeeded To not get entangled in technology discussions To not get entangled in technology discussions Focus on domain expertise Focus on domain expertise I reuse well documented things I reuse well documented things I do not want to find “The Solution” but I want to see multiple options I do not want to find “The Solution” but I want to see multiple options 21

22. What can/should we do for a start? Mailing list / forum Mailing list / forum Wiki Wiki Who is going to host them? Who is going to host them? Create an initial list of topics Create an initial list of topics Rate them and select the 5 top by priority/interest Rate them and select the 5 top by priority/interest Identify responsible person for each area Identify responsible person for each area Look after 1 year and make a checkpoint Look after 1 year and make a checkpoint 22

23. Periodical Meetings ADASS (once/year): ADASS (once/year): BoF session BoF session Already some more concrete ideas Already some more concrete ideas SPIE (every two years) SPIE (every two years) Some phone meetings to coordinate the activities Some phone meetings to coordinate the activities Sub-groups would decide if/how/when to meet Sub-groups would decide if/how/when to meet 23

24. Some issues Look at similar initiatives for procedures/tools: Look at similar initiatives for procedures/tools: NASA Earth Science Data Systems Software Reuse Working Group (http://www.esdswg.org/softwarereuse)? NASA Earth Science Data Systems Software Reuse Working Group (http://www.esdswg.org/softwarereuse)?http://www.esdswg.org/softwarereuse Opticon? Opticon? Can we directly piggy back on one? Can we directly piggy back on one? Keep it very domain specific? Keep it very domain specific? People should offer their body and soul for: People should offer their body and soul for: Enhancing the original core team Enhancing the original core team Coordinating and keeping alive the topics Coordinating and keeping alive the topics Look for resources: Look for resources: Man power approval inside our organizations Man power approval inside our organizations Funding from agencies (NSF, EU FPx programs?) Funding from agencies (NSF, EU FPx programs?) 24

25. Tomorrow? Think think think: what can YOU do to make it really happen? Think think think: what can YOU do to make it really happen? Get in touch with me (gchiozzi@eso.org) or anybody of the authors of the paper, to offer your collaboration. Get in touch with me (gchiozzi@eso.org) or anybody of the authors of the paper, to offer your collaboration.gchiozzi@eso.org We will quickly setup an initial mailing list//forum and wiki We will quickly setup an initial mailing list//forum and wiki Follow up Follow up Spread the word Spread the word Convince your boss to give you some resources Convince your boss to give you some resources 25

26. 26 Thanks!!!!! Contact: gchiozzi@eso.org gchiozzi@eso.org I will put links and this PPT in my home page: http://www.eso.org/~gchiozzi Will move things as soon as we will have the wiki and redirect from there.