PhD students and researchers are very welcome to participate in the first day dedicated to the development of Research Software.
The event will take place at ICube (Telecom Physique, Illkirch, amphitheater A301).
Participation is credited for PhD students (formation transversale), signing the participant lists.
Remote access is available at the following link: https://bbb.unistra.fr/b/cob-tz4-bis-fqf
Program:
MORNING
9 am -> 10 am: First Talk
A software developer and a data scientist, in an open science world
University of Ghent, Chaire Gutenberg
These days, programming skills are increasingly useful (if not outright essential) when dealing with substantial amounts of data. As a result, more and more researchers become part-time sofwtare developers, or data scientists, or both. Some enterprising individuals even go all the way, and transition to the keyboard full-time. But all of this is not without its challenges, especially not in an increasingly open science context. Here, we will look at a few relevant aspects, including software development best practices, some useful tools and resources, expectation management, and the dreaded curse of building the actually useful tool.
Talk by Riccardo Hertel is postponed.
An introduction to best practices in code development
Riccardo Hertel
IPCMS, CNRS and Université de Strasbourg
riccardo.hertel[at]ipcms.unistra.fr
When writing code, the main objective is to obtain a numerical tool capable of reliably performing a specific computational task. Beyond this purely functional aim of having software that is operating correctly, the code development process itself should be as fast and efficient as possible. Moreover, writing clearly and well-structured software is desirable as it facilitates code maintenance and allows it to be easily adapted and reused. Several “best practices” to account for these aspects of code development have been reported in the literature. I will discuss some of such best practices and their importance for working on larger software projects and put them into the context of experience I gained over the past few years in developing scientific simulation software (
http://tetmag.readthedocs.io).
10 am -> Noon: Second Talk
Author's rights (in France) and licenses for your Research Software
Teresa Gomez-Diaz
CNRS/LIGM and Université Gustave Eiffel
teresa.gomez-diaz@univ-eiffel.fr
The activities regularly carried out within the framework of research laboratories, in France and abroad, increasingly include software development. These software are frequently developed using forges and are freely accessible there, or they are distributed on personal web pages, laboratory pages, projects, etc.
This software is essential in obtaining scientific results and a key element in their reproducibility.
However, making Research Software visible and accessible requires that it is distributed correctly, within a controlled legal framework, with a license that allows its use, modification and redistribution. But who decides on this license? When should it be put into place? Who are the rights holders of this work? What licenses should be used and under what conditions?
In this presentation we will study the production context of Research Software and the legal questions that arise regarding copyright and licenses [1]. We will propose a diffusion procedure whose steps take these questions into account [2].
We will review the concept of Research Software [1,3] and also propose the CDUR protocol for its evaluation as a scientific production [3] within the framework of Open Science [4].
This work benefits from the experience at the Gaspard-Monge Computer Science Laboratory (LIGM) [5], the PLUME Project (2006-2013) [6] and the work in collaboration with Prof. Tomas Recio (Univ. Nebrija, Madrid) [3,4].
References
[1] Article vs. Logiciel : questions juridiques et de politique scientifique dans la production de logiciels
T. Gomez-Diaz (2015), https://zenodo.org/record/18993
[2] Diffuser un logiciel de laboratoire : recommandations juridiques et administratives
T. Gomez-Diaz (2010), https://zenodo.org/record/7096216
[3] On the evaluation of research software: the CDUR procedure, F1000Research 2019, 8:1353
T. Gomez-Diaz, T. Recio (2019),
https://doi.org/10.12688/f1000research.19994.2
[4] Towards an Open Science definition as a political and legal framework: on the sharing and dissemination of research outputs
T. Gomez-Diaz, T. Recio (2020-21),
(V3, février 2021) https://zenodo.org/record/4577066
(v2, décembre 2020) Publication POLIS, https://doi.org/10.58944/yuro5734
[5] Sur la production de logiciels libres au Laboratoire d'Informatique Gaspard-Monge (LIGM) : ce que nous avons appris
T. Gomez-Diaz (2021),
https://github.com/blue-hats/ateliers/blob/main/details/2021-04-09.org
http://igm.univ-mlv.fr/~teresa/logicielsLIGM/documents/Seminaires/2021avrilBlueHats_TGD.pdf
[6] Thème PLUME Patrimoine logiciel d'un laboratoire
T. Gomez-Diaz (2009-2013),
https://zenodo.org/communities/plume-patrimoine-logiciel-laboratoire/
Program
AFTERNOON
1pm30 -> 3pm30: Coffee Break at the iCube Cafeteria (Telecom Physique, Illkirch),
1pm30->2pm: Coffee Break at the iCube Cafeteria (Telecom Physique, Illkirch)
2pm->3pm30: 2 presentations in amphitheater A301 (Telecom Physique, Illkirch)
First talk:
Maintaining and contributing: open software for astrophysics
Manon Marchand & Matthieu Baumann
CDS/ CNRS and Université de Strasbourg
https://astro.unistra.fr/fr/recherche/cds/
The participation to open software of the Strasbourg Astronomical Data Center (CDS) is twofold: we publish and maintain software, and we contribute to the existing ecosystem of astronomical libraries. In this short intervention, we'll present the libraries of our public forge https://github.com/cds-astro and discuss our interactions -- as contributors and as maintainers -- with the rest of the astronomical developing community.
Second talk:
The Second National Roadmap for Open Science and Research Software
IPHC/CNRS and Université of Strasbourg
After an introduction to the national roadmap for Open Science, its section dedicated to research software will be presented. The presentation of a concrete case will then provide an example of how these recommendations can be applied. Finally, the local application of the roadmap will be detailed.