Skip to content

Commit 15da778

Browse files
authored
Update nl-workshop1.md
Text from @sabasharma
1 parent b7a006c commit 15da778

File tree

1 file changed

+73
-1
lines changed

1 file changed

+73
-1
lines changed

nl-workshop1.md

Lines changed: 73 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,5 +4,77 @@ title: CODECHECK NL Workshop 1
44
permalink: /nl-workshop1/
55
---
66

7-
Our first workshop will be held in Delft, May 30th 2014.
7+
### Our first workshop will be held in Delft, May 30th 2014.
88

9+
10+
11+
Are you a researcher in engineering interested in reproducible code
12+
and Open Science? We have the perfect opportunity for you! 
13+
14+
As part of our newly launched NWO project CHECK-NL, we are looking for
15+
researchers from the field of engineering at a Dutch knowledge
16+
institution or university who would like their papers or projects to
17+
be “codechecked” during a live, one-day code-checking workshop on 30th
18+
May 2024.  A codecheck is a light-touch independent peer review to
19+
check that your code and data can generate the computational results
20+
in your paper or project (see more details at
21+
https://codecheck.org.uk/process/). 
22+
23+
You can participate as a codechecker (i.e., a person reviewing code),
24+
or by submitting your own work to be checked (or both if you are up
25+
for it!)
26+
27+
Our first workshop will be at the X-building in TU Delft. Anyone from
28+
engineering sciences is welcome to participate at the
29+
workshop. Participation is free of cost and includes lunch. We have
30+
limited funding (on a first come, first served basis) for reimbursing
31+
train tickets for PhD (non-AiO) students.
32+
33+
If you cannot make this workshop, there will be further opportunities
34+
later in the year as we plan three more workshops around the
35+
Netherlands.
36+
37+
38+
What do I get? 
39+
40+
A codechecker will work with you during the session to check whether
41+
your code and data can be run by others to generate the same or
42+
similar results. 
43+
44+
The codechecker will work with you to resolve any issues found during
45+
the codecheck, and make your code as reproducible as possible! 
46+
47+
Upon completion, your paper will receive a codecheck certificate that
48+
confirms your results could be reproduced.  This can be shared, for
49+
example, with potential journal editors, to enhance the visibility and
50+
reproducibility of your work.  
51+
52+
By participating, you contribute towards making science more open and
53+
transparent AND increase the visibility of your own research! 
54+
55+
56+
Sounds good! What should I do? 
57+
58+
Are you interested in submitting code or data for this event, and help
59+
contribute to promoting code reproducibility? Send an email
60+
to [email protected] by 30th April 2024 with a brief description
61+
of your paper/project, and links to your code and data. This could be
62+
code related to: 
63+
64+
- A paper that you have recently published 
65+
66+
- A preprint that is publicly available 
67+
68+
- Code and results files that have been or will be deposited in a
69+
repository, preferably GitHub or GitLab 
70+
71+
In each case, the code and data underlying the paper should be openly
72+
available, or you plan to make them available once the paper is
73+
published.
74+
75+
Selected papers/projects will be notified in early May 2024.
76+
77+
78+
Would you instead like to participate in the workshop and learn how to
79+
become a codechecker? All participants are invited to register on the
80+
event page and join the workshop.

0 commit comments

Comments
 (0)