1 of 10

2 of 10

3 of 10

Schedule & conveners

Introduction statements

Debate

pre-submitted questions

audience questions

audience polls

After the debate#DataHelpDesk, vEGU chat, materials page on website, permanent discussion forum: http://bit.ly/vegu21-software-discuss

Daniel S. Katz�(moderator)

Daniel Nüst

Niels Drost

Lesley Wyborn

David Topping

4 of 10

Housekeeping/announcements

Ask your questions through Zoom Q&A and use the upvoting 👍 button.

We’ll try to transfer questions from the chat on the vEGU website’s stream, but no voting or polls there.

Twitter: #vegu21 #gdb3

5 of 10

Debaters

Carina Haupt

German Aerospace Center (DLR)

Kim Serradell

Barcelona Supercomputing Center, Spain

Patrick Sanan

ETH Zürich, Switzerland

Rolf Hut

MacGyver scientist, TU Delft, The Netherlands

Susanne Buiter

Tectonics and Geodynamics, RWTH Aachen University, Aachen, Germany

6 of 10

Live poll results no. 1 - “the audience”

👍

😞

😞

👍

✍️

7 of 10

Live poll results no. 2 - “the way forward”

‼️

8 of 10

Research software should be like infrastructure. Let RSEs build highways and scientists be pathfinders, don’t force one to be the other.

We need to make sure that work is reproducible, and it has to be open for that. Diversity of geoscience topics and edge cases prohibit mandatory sharing of all code, but foundational ethic of sharing is important.

Context of software matters. A clear scope statement and simple quick start documentation manage expectations and reduce fear of sharing.

If reproducibility is impossible (HPC, months), ensure interpretability and follow ethics of sharing (logs etc.) so that reviewers can inspect, give access to infrastructure, and clearly document the used software stacks.

Journal papers to credit software are a placeholder. We need to find ways to acknowledge software for what it is, e.g., software citation.

Amount of basic training vs. sticking to specialities is an open questions with different opinions.

It is possible for publishers to demand checking of workflows before sent out to review and scientific quality is evaluated.�Reproducible != Reusable != software quality.

Exciting technology exists but communication, community aspects, and broad basic software literacy are crucial.

Culture change is hard and senior scientists must drive it, and all aspects of science are touched (publishers, funders, …)

9 of 10

Thanks

to the 140+ participants in the session!

Stay connected, improve research software: #DataHelpDesk, vEGU chat (few weeks),�materials page on website, permanent discussion forum: http://bit.ly/vegu21-software-discuss

10 of 10