You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
13
+
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.
14
14
15
-
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).
15
+
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).
16
16
17
-
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!
17
+
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!
18
18
19
-
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!
19
+
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!
20
20
21
-
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!
21
+
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!
of your paper/project, andlinks to your code and data. This could be
75
+
code related to:
76
76
77
-
- A paper that you have recently published
77
+
- A paper that you have recently published
78
78
79
-
- A preprint that is publicly available
79
+
- A preprint that is publicly available
80
80
81
81
- Code and results files that have been or will be deposited in a
82
-
repository, preferably GitHub or GitLab
82
+
repository, preferably GitHub or GitLab
83
83
84
-
In each case, the code and data underlying the paper should beopenly
84
+
In each case, the code and data underlying the paper should beopenly
85
85
available, or you plan to make them available once the paper is
86
86
published.
87
87
88
-
**Selected papers/projects will be notified in early May 2024.**
89
-
88
+
**Selected papers/projects will be notified in early May 2024.**
90
89
91
90
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.
92
91
93
-
For questions related to the NWO project CHECK-NL, please contact Frank Ostermann ([email protected])
94
-
95
-
92
+
For questions related to the NWO project CHECK-NL, please contact Frank Ostermann (<[email protected]>)
Copy file name to clipboardExpand all lines: nl.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
layout: page
3
-
title: CODECHECK NL
3
+
title: CODECHECKing goes NL (CHECK-NL)
4
4
permalink: /nl/
5
5
---
6
6
@@ -9,12 +9,14 @@ permalink: /nl/
9
9
The Dutch research organization *NWO* funds the project [CodeCHECKing goes NL](https://www.nwo.nl/projecten/osf232063).
10
10
11
11
Many research outputs rely on computational methods.
12
-
Open Science principles ask for those to be shared and to be reproducible.
12
+
Open Science principles ask for those methods and data to be shared and to be reproducible.
13
13
However, in traditional scientific publishing, computational methods are rarely re-run during review.
14
14
[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.
15
15
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.
16
16
17
-
Find all codechecks conducted as part of CODECHECK NL in the CODECHECK Register: <https://codecheck.org.uk/register/venues/community/codecheck_nl/>
17
+
In addition, the project funds improvements to the CODECHECK infrastructure by adding new features to the [CODECHECK Register](https://codecheck.org.uk/register/).
18
+
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+).
19
+
Thanks to these contributions by CHECK-NL, you can find all codechecks conducted as part of CHECK-NL in the new community page at <https://codecheck.org.uk/register/venues/communities/codecheck_nl/>.
18
20
19
21
### Latest News
20
22
@@ -26,7 +28,7 @@ Find all codechecks conducted as part of CODECHECK NL in the CODECHECK Register:
26
28
27
29
-**First CODECHECK-NL event at TU Delft successfully concluded!** Read about it on our [TUD workshop page](https://codecheck.org.uk/nl-workshop1/)
28
30
29
-
-**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 [email protected]. For questions on the project, please contact Frank Ostermann ([email protected]). For updates, watch this space or follow us on the channels listed below!
31
+
-**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 <mailto:[email protected]>. For questions on the project, please contact Frank Ostermann (<mailto:[email protected]>). For updates, watch this space or follow us on the channels listed below!
0 commit comments