Upgrade to Pro — share decks privately, control downloads, hide ads and more …

What is good scientific practice for research software?

What is good scientific practice for research software?

Talk for the 2nd Conference on Non-Textual Information - Software and Services for Science (S3), May 10-11, 2017 in Hannover

Konrad Förstner

May 10, 2017
Tweet

More Decks by Konrad Förstner

Other Decks in Science

Transcript

  1. What is good scientific practice for research software? ... and

    how can we make it part of our research culture? Konrad U. Förstner @konradfoerstner University of Würzburg May 10th, 2017
  2. It is unquestionable that there is a strong and growing

    dependence of research on software.
  3. Software is also a result of the scientific work. Quality,

    accessibility, citability, etc. have to be ensured.
  4. Common problems with research software • Source code not published/available

    or even proprietary • No quality control / automated tests • Missing documentation • Discontinued development (e.g. due to end of contract) • Long-time availability not guaranteed • Missing citability https://commons.wikimedia.org/wiki/File:Paris_Tuileries_Garden_Facepalm_statue.jpg - PD
  5. Potential reasons • Lack of awareness • Lack of skills

    • Lack of time • Lack of incentives • Lack of dedicated long-term funding • No reviewing • To hinder competitors https://commons.wikimedia.org/wiki/File:Paris_Tuileries_Garden_Facepalm_statue.jpg - PD
  6. • Software Carpentry (1998) • Software Sustainability Institute (2008) •

    WSSSPE (Working towards sustainable software for science: practice and experiences) https://unsplash.com/photos/vrbZVyX2k4I - PD
  7. • Software Carpentry (1998) • Software Sustainability Institute (2008) •

    WSSSPE (Working towards sustainable software for science: practice and experiences) • Free Software Foundation Europe published a position paper regarding research software https://unsplash.com/photos/vrbZVyX2k4I - PD
  8. • Software Carpentry (1998) • Software Sustainability Institute (2008) •

    WSSSPE (Working towards sustainable software for science: practice and experiences) • Free Software Foundation Europe published a position paper regarding research software • DANS (Data Archiving and Networked Services (DANS) https://unsplash.com/photos/vrbZVyX2k4I - PD
  9. • Software Carpentry (1998) • Software Sustainability Institute (2008) •

    WSSSPE (Working towards sustainable software for science: practice and experiences) • Free Software Foundation Europe published a position paper regarding research software • DANS (Data Archiving and Networked Services (DANS) • sciforge https://unsplash.com/photos/vrbZVyX2k4I - PD
  10. • Software Carpentry (1998) • Software Sustainability Institute (2008) •

    WSSSPE (Working towards sustainable software for science: practice and experiences) • Free Software Foundation Europe published a position paper regarding research software • DANS (Data Archiving and Networked Services (DANS) • sciforge • DFG program ”Research Software Sustainability” (7M €, 130 applications) https://unsplash.com/photos/vrbZVyX2k4I - PD
  11. • Software Carpentry (1998) • Software Sustainability Institute (2008) •

    WSSSPE (Working towards sustainable software for science: practice and experiences) • Free Software Foundation Europe published a position paper regarding research software • DANS (Data Archiving and Networked Services (DANS) • sciforge • DFG program ”Research Software Sustainability” (7M €, 130 applications) • Helmholtz Association Task Group ”Access to and re-use of research software” formed; organized a workshop about research software https://unsplash.com/photos/vrbZVyX2k4I - PD
  12. • Software Carpentry (1998) • Software Sustainability Institute (2008) •

    WSSSPE (Working towards sustainable software for science: practice and experiences) • Free Software Foundation Europe published a position paper regarding research software • DANS (Data Archiving and Networked Services (DANS) • sciforge • DFG program ”Research Software Sustainability” (7M €, 130 applications) • Helmholtz Association Task Group ”Access to and re-use of research software” formed; organized a workshop about research software • de-RSE founded (de-rse.org) https://unsplash.com/photos/vrbZVyX2k4I - PD
  13. • Software Carpentry (1998) • Software Sustainability Institute (2008) •

    WSSSPE (Working towards sustainable software for science: practice and experiences) • Free Software Foundation Europe published a position paper regarding research software • DANS (Data Archiving and Networked Services (DANS) • sciforge • DFG program ”Research Software Sustainability” (7M €, 130 applications) • Helmholtz Association Task Group ”Access to and re-use of research software” formed; organized a workshop about research software • de-RSE founded (de-rse.org) • Several more ... lot of them here! https://unsplash.com/photos/vrbZVyX2k4I - PD
  14. Since 2008: Priority Initiative ”Digital Information” of the Alliance of

    Science Organisations in Germany The logos in this slide are excluded from the CC-BY license statement
  15. Priority areas of the iniative • Research Data • Virtual

    Research Environments • National Licensing • National Hosting Strategy • Legal Frameworks • Open Access
  16. Priority areas of the iniative • Research Data • Virtual

    Research Environments • National Licensing • National Hosting Strategy • Legal Frameworks • Open Access Some fame due to the recent ”DEAL” negotiations.
  17. Mathias Bornschein Ressortforschung des Bundes Dr. Matthias Katerbow German Research

    Foundation Prof. Dr. Andreas Zeller German Research Foundation Dr. Bernadette Fritzsch Helmholtz Association Dr. Uwe Konrad Helmholtz Association Dr. Georg Feulner Leibniz Association Dr. Jürgen Fuhrmann Leibniz Association Michael Franke Max Planck Society Stephan Janosch Max Planck Society Dr. Michael Erben-Russ Fraunhofer Society Dennis Zielke Fraunhofer Society Prof. Dr. Björn Brembs German Rectors’ Conference Dr. Konrad Förstner German Rectors’ Conference https://www.pexels.com/photo/people-coffee-meeting-team-7096/ - PD
  18. The members have diverse backgrounds - scientist of different fields

    and scientific service / infrastructure providers. https://www.pexels.com/photo/people-coffee-meeting-team-7096/ - PD
  19. Our modus operandi Compile recommendations and carry them back into

    our research organisations. https://www.pexels.com/photo/people-coffee-meeting-team-7096/ - PD
  20. Guiding principle The concept of Good Scientific Practice (GSP) must

    be also applied to research software. https://www.pexels.com/photo/people-coffee-meeting-team-7096/ - PD
  21. But what can Good Scientific Practice mean for research software?

    https://www.pexels.com/photo/people-coffee-meeting-team-7096/ - PD
  22. • Reproducibility • Confirmability • Transparency • Qualility • Re-usability

    https://www.pexels.com/photo/people-coffee-meeting-team-7096/ - PD
  23. Our working model – three types of software 1. Small

    tools written for single purpose 2. Software applications (as research output) 3. Infrastructure and online services https://www.pexels.com/photo/people-coffee-meeting-team-7096/ - PD
  24. All three levels are relevant and have to be addressed.

    https://www.pexels.com/photo/people-coffee-meeting-team-7096/ - PD
  25. Exact needs and possibilities might differ between scientific communities. Discourse

    must also happen inside of these communities. https://www.pexels.com/photo/people-coffee-meeting-team-7096/ - PD
  26. E.g. what exactly means ”reproducibility” (bit-identical compilation?) and how long

    would this needed to be guaranteed? https://www.pexels.com/photo/people-coffee-meeting-team-7096/ - PD
  27. Raise the awareness for the relevance of research software. https://www.flickr.com/photos/ogimogi/2223450729

    https://www.flickr.com/photos/ogimogi/2223450729 - CC-BY Eran Sandler
  28. Include standards for research software into the common Good Scientific

    Practice recommendations. https://www.flickr.com/photos/ogimogi/2223450729 https://www.flickr.com/photos/ogimogi/2223450729 - CC-BY Eran Sandler
  29. Introduce standards and mechanisms for quality control of research software.

    https://www.flickr.com/photos/ogimogi/2223450729 https://www.flickr.com/photos/ogimogi/2223450729 - CC-BY Eran Sandler
  30. Foster the education of computational skills inside of the scientific

    community. https://www.flickr.com/photos/ogimogi/2223450729 https://www.flickr.com/photos/ogimogi/2223450729 - CC-BY Eran Sandler
  31. Develop new carreer paths like Research Software Engineers, Software Librarians,

    Data Scientists. https://www.flickr.com/photos/ogimogi/2223450729 https://www.flickr.com/photos/ogimogi/2223450729 - CC-BY Eran Sandler
  32. Raise awareness about and teach legal aspects (i.e. licensing) of

    software. https://www.flickr.com/photos/ogimogi/2223450729 https://www.flickr.com/photos/ogimogi/2223450729 - CC-BY Eran Sandler
  33. Raise awareness about and teach legal aspects (i.e. licensing) of

    software. Make open source the default. https://www.flickr.com/photos/ogimogi/2223450729 https://www.flickr.com/photos/ogimogi/2223450729 - CC-BY Eran Sandler
  34. Facilitate the transition from single-purpose solutions to application to services.

    https://www.flickr.com/photos/ogimogi/2223450729 https://www.flickr.com/photos/ogimogi/2223450729 - CC-BY Eran Sandler
  35. We represent the German scientific community / research organisation. Ideally

    all these issues are adressed on an international level. http://www.everystockphoto.com/photo.php?imageId=2380666 – The Library of Congress, PD