On 25 November 2025, more than 200 people attended the National Research Software Day in Delft. There were parallel sessions on training materials, demo sessions, and unconference tables about community building. Many of the contributions were related to reproducible research software. This is a short list of topics and themes that came up during the day.

Unconference session on CODECHECK and reproducibility checks
During the unconference in the afternoon, Joao Guimaraes (TU Delft) and Aleksandra Wilczynska (4 TU Research Data) presented their work on reproducibility checks. Submitters to the Data repository can now request a reproducibility check by an engineer or software steward at their institution. If the reproducibility check (a very low bar CODECHECK verifying that the main graphs or tables can be reproduced with the shared materials) is successful, the entry will receives a badge.
Participants at the unconference session attempted to re-run a reproducibility check within the short allocated time and thought about implementation strategies to make such checks a normal addition to research pipelines.
Find out more about reproducibility checks/ CODECHECK at 4TU Research Data here:
CODECHECK in Practice: How TU Delft and 4TU.ResearchData Are Making Reproducibility Happen
Training materials to make compendia pre-producible
In his talk “Reproducible research through reusable code in 1 day”, Eduard Klapwijk from SURF presented his work on training materials to help researchers make their research compendia reproducible.
He mentioned that one big step for many researchers was to make their code openly available on a platform like github. And that some workshop participants decided to close their repositories again after the workshop.
The training materials can be found here: Lesson material for Reproducible research through reusable code workshop
And this is the material website: Reproducible research through reusable code
Streamlining Labtechnology
During the unconference session, Ana Caballo for Radboud University pitched her project ConDAQtor to help physicists streamline their lab technology. The problem many experimental phycisist face is that the commonly used lab software “labview” can do quite a bit of automation but it is tedious and few people invest the time to master it. As a consequence many experiments are not fully automated. Ana suggested to bring people together in a hackathon to create templates and tutorials.

Interestingly, in the same week, Code for Thought published an episode about Sébastien Webers work on PyMoDAQ, a python package and project to help researchers build plugins for their experimental setup.
[EN] PyMoDAQ: No more reinventing the wheel – with Sébastien Weber
Making research software FAIR
Roadmap for FAIR software skills: The team behind the Research Software Roadmap present their work from the tDCC-NES retreat. They developed a toxonomy to link researcher skills to programming and code management skills. The roadmap can be used to design lesson and training plans to tailor trainings to individual needs.
Website: Research Software Roadmap | Open Science Roadmaps
Roadmap team: Charlotte Summers (Utrecht University), Nami Sunami (TU Eindhoven), Margot Teunisse (Leiden University), Helena Wedig (Erasmus University), Bjørn Bartholdy (TU Delft), Nick Hodgskin (Utrecht University), Yilin Huang (TU Delft), Neha Moopen (Utrecht University), Anastasiya Paltarzhytskaya (Radboud Univeristy)
SMP Tool: Create a Software Management Plan That Fits Your Project
During a parallel session, colleagues form the eScience Center presented a open-source, web-based SMP Tool. The tool guides developers through a questionnaire to creae a tailored software management plan and recommends best practices, resources, and examples. The tool works for small scripts just as well as for larger pieces of software.
You can find out more on this website: https://smp.research.software and on their repository: https://ss-nes.github.io/#toolkit-smp-decision-tree The project is part of the sustainable research software tool kit of the tDCC NES: SS-NES landing page
SMP Tool Team: Ole Mussmann (eScience Center), Carlos Martinez Ortiz (eScience Center), Sander van Rijn (eScience Center), Thijs van Lankveld (eScience Center), Giulio Rosani (University of Groningen)
Code Auditor: Code Auditor is a command line tool that helps assess research software projects against community best practices and provides actionable recommendations for improvement. The auditor is developed by Serkan Girgin
Find the materials on zenodo: code-auditor







