diff --git a/nl-workshop1.md b/nl-workshop1.md index 21ba371..23f06d7 100644 --- a/nl-workshop1.md +++ b/nl-workshop1.md @@ -1,6 +1,6 @@ --- layout: page -title: CODECHECK NL Workshop for Engineering Sciences +title: CHECK-NL Workshop for Engineering Sciences permalink: /nl-workshop1/ --- @@ -10,29 +10,29 @@ permalink: /nl-workshop1/ Delft workshop participants

-On the 30th of May 2024, the CODECHECK-NL team organised its first roadshow event in Delft. The event marks the beginning of a series of four workshops to be conducted across the Netherlands, where we carry out live codechecks with authors and reviewers, while also training a new batch of codecheckers across universities in the Netherlands. +On the 30th of May 2024, the CODECHECK-NL team organised its first roadshow event in Delft. The event marks the beginning of a series of four workshops to be conducted across the Netherlands, where we carry out live codechecks with authors and reviewers, while also training a new batch of codecheckers across universities in the Netherlands. -The Delft event kicked off in the morning with 20 participants and members of the CODECHECK-NL team. We began with a short introduction to the project and its scope by Frank Ostermann (PI for the project, based at the University of Twente), followed by an introduction to codechecking by Stephen Eglen, one of the founders of CODECHECK, and a computational neuroscientist based at the University of Cambridge. Stephen’s presentation (which can be found [here](https://sje30.github.io/talks/2024/codecheck2024-02.html#/title-slide)) introduced the philosophy behind codecheck, and the importance of the concept of “good enough” in facilitating code reproducibility. The introduction was followed by a live demo codecheck, conducted on a project submitted by Filip Surma of Delft University of Technology. Curious to see what a CODECHECK certificate looks like? See Filip's certificate [here](https://zenodo.org/records/11403956). +The Delft event kicked off in the morning with 20 participants and members of the CODECHECK-NL team. We began with a short introduction to the project and its scope by Frank Ostermann (PI for the project, based at the University of Twente), followed by an introduction to codechecking by Stephen Eglen, one of the founders of CODECHECK, and a computational neuroscientist based at the University of Cambridge. Stephen's presentation (which can be found [here](https://sje30.github.io/talks/2024/codecheck2024-02.html#/title-slide)) introduced the philosophy behind codecheck, and the importance of the concept of “good enough” in facilitating code reproducibility. The introduction was followed by a live demo codecheck, conducted on a project submitted by Filip Surma of Delft University of Technology. Curious to see what a CODECHECK certificate looks like? See Filip's certificate [here](https://zenodo.org/records/11403956). -Following lunch and the successful codecheck of Filip’s project, in collaboration with the participants, in the afternoon we moved into breakout sessions, codechecking three more projects in smaller groups, with authors also present during the process. Three more successful codechecks later, participants had a much clearer picture of what codechecks are, how the process works, and how easy or difficult it can be to run or reuse someone else’s code! +Following lunch and the successful codecheck of Filip's project, in collaboration with the participants, in the afternoon we moved into breakout sessions, codechecking three more projects in smaller groups, with authors also present during the process. Three more successful codechecks later, participants had a much clearer picture of what codechecks are, how the process works, and how easy or difficult it can be to run or reuse someone else's code! -All these points were touched upon in our final reflection session, where we considered questions of how codechecks could be incorporated into the research and publishing workflow, and ideas for the sustainability of codechecking. Some important issues were raised, such as the importance of institutional support, how to recognise codecheck efforts for both authors and reviewers. Some interesting solutions were also proposed, like the concept of ‘codecheck buddies’, or making codechecks a service researchers could avail of, having a dedicated ‘codechecker’ based at a journal. The discussion was finally only concluded because it was time to leave the room! +All these points were touched upon in our final reflection session, where we considered questions of how codechecks could be incorporated into the research and publishing workflow, and ideas for the sustainability of codechecking. Some important issues were raised, such as the importance of institutional support, how to recognise codecheck efforts for both authors and reviewers. Some interesting solutions were also proposed, like the concept of ‘codecheck buddies', or making codechecks a service researchers could avail of, having a dedicated ‘codechecker' based at a journal. The discussion was finally only concluded because it was time to leave the room! -Do you find the topics of code reuse, reproducibility and learning a hands-on skill interesting? Then join us at one of our next workshops! We are hosting our next event at the **University of Twente on 26th of September 2024**, and another at the **Erasmus University Rotterdam on the 28th of November 2024**. Save the (tentative) dates, and stay tuned for updates! +Do you find the topics of code reuse, reproducibility and learning a hands-on skill interesting? Then join us at one of our next workshops! We are hosting our next event at the **University of Twente on 26th of September 2024**, and another at the **Erasmus University Rotterdam on the 28th of November 2024**. Save the (tentative) dates, and stay tuned for updates! --------------------------------------------------------------------------------------- ## Our call for papers for the Delft worksop -### Are you a researcher in engineering interested in reproducible code and Open Science? We have the perfect opportunity for you!  - +### Are you a researcher in engineering interested in reproducible code and Open Science? We have the perfect opportunity for you! + As part of our newly launched NWO project [CHECK-NL](https://codecheck.org.uk/nl/), **we are looking for researchers from the field of engineering at a Dutch knowledge institution or university who would like their papers or projects to be “codechecked” during a live, one-day code-checking workshop on 30th -May 2024**, at the X-building in TU Delft.  A codecheck is a light-touch independent peer review to +May 2024**, at the X-building in TU Delft. A codecheck is a light-touch independent peer review to check that your code and data can generate the computational results -in your paper or project (see more details [here](https://codecheck.org.uk/process/)).  +in your paper or project (see more details [here](https://codecheck.org.uk/process/)). You can participate as a codechecker (a person reviewing code), or by submitting your own work to be checked (or both if you are up @@ -48,48 +48,45 @@ later in the year as we plan three more workshops around the Netherlands. -### What do I get if I submit my code?  +### What do I get if I submit my code? A codechecker will work with you during the session to check whether your code and data can be run by others to generate the same or -similar results.  +similar results. The codechecker will work with you to resolve any issues found during -the codecheck, and make your code as reproducible as possible!  +the codecheck, and make your code as reproducible as possible! -Upon completion, your paper will receive a codecheck certificate that -confirms your results could be reproduced.  This can be shared, for +Upon completion, your paper will receive a codecheck certificate that +confirms your results could be reproduced. This can be shared, for example, with potential journal editors, to enhance the visibility and -reproducibility of your work.   +reproducibility of your work. By participating, you contribute towards making science more open and -transparent AND increase the visibility of your own research!  +transparent AND increase the visibility of your own research! -### Sounds good! What should I do?  +### Sounds good! What should I do? Are you interested in submitting code or data for this event, and helping to promote code reproducibility? Send an email -to codechecknl@gmail.com by **30th April 2024** with a brief description -of your paper/project, and links to your code and data. This could be -code related to:  +to by **30th April 2024** with a brief description +of your paper/project, and links to your code and data. This could be +code related to: -- A paper that you have recently published  +- A paper that you have recently published -- A preprint that is publicly available  +- A preprint that is publicly available - Code and results files that have been or will be deposited in a -repository, preferably GitHub or GitLab  +repository, preferably GitHub or GitLab -In each case, the code and data underlying the paper should be openly +In each case, the code and data underlying the paper should be openly available, or you plan to make them available once the paper is published. -**Selected papers/projects will be notified in early May 2024.** - +**Selected papers/projects will be notified in early May 2024.** Would you instead like to participate in the workshop and learn how to codecheck? All participants are invited to register on the [event page](https://www.eventbrite.com/e/codecheck-workshop-for-engineering-sciences-tickets-867503124197) and join the workshop. -For questions related to the NWO project CHECK-NL, please contact Frank Ostermann (f.o.ostermann@utwente.nl) - - +For questions related to the NWO project CHECK-NL, please contact Frank Ostermann () diff --git a/nl.md b/nl.md index bed180a..ca770f7 100644 --- a/nl.md +++ b/nl.md @@ -1,6 +1,6 @@ --- layout: page -title: CODECHECK NL +title: CODECHECKing goes NL (CHECK-NL) permalink: /nl/ --- @@ -9,12 +9,14 @@ permalink: /nl/ The Dutch research organization *NWO* funds the project [CodeCHECKing goes NL](https://www.nwo.nl/projecten/osf232063). Many research outputs rely on computational methods. -Open Science principles ask for those to be shared and to be reproducible. +Open Science principles ask for those methods and data to be shared and to be reproducible. However, in traditional scientific publishing, computational methods are rarely re-run during review. [Our project team](#meet-the-project-team) aims to check the computational workflows of at least 50 scientific articles for reproducibility, and we aim to reach an agreement with journal editors to establish such a check routinely in their review process. To kickstart both, we will organise roadshows at four locations to bring experienced and new code reviewers, authors, and editors together to implement codechecking in a sustainable way. -Find all codechecks conducted as part of CODECHECK NL in the CODECHECK Register: +In addition, the project funds improvements to the CODECHECK infrastructure by adding new features to the [CODECHECK Register](https://codecheck.org.uk/register/). +You can find all developments within CHECK-NL [in these pull requests on GitHub](https://github.com/codecheckers/register/pulls?q=is%3Apr+label%3Acheck-nl+). +Thanks to these contributions by CHECK-NL, you can find all codechecks conducted as part of CHECK-NL in the new community page at . ### Latest News @@ -26,7 +28,7 @@ Find all codechecks conducted as part of CODECHECK NL in the CODECHECK Register: - **First CODECHECK-NL event at TU Delft successfully concluded!** Read about it on our [TUD workshop page](https://codecheck.org.uk/nl-workshop1/) -- **Reserve 30 May in your agenda for the first event at the TU Delft** More info including how to register found [here](https://codecheck.org.uk/nl-workshop1/). For all questions on the events, send an e-mail to codechecknl@gmail.com. For questions on the project, please contact Frank Ostermann (f.o.ostermann@utwente.nl). For updates, watch this space or follow us on the channels listed below! +- **Reserve 30 May in your agenda for the first event at the TU Delft** More info including how to register found [here](https://codecheck.org.uk/nl-workshop1/). For all questions on the events, send an e-mail to . For questions on the project, please contact Frank Ostermann (). For updates, watch this space or follow us on the channels listed below! ### Meet the project team