-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix some md warnings, add backlings to NL workshop pages
- Loading branch information
Showing
6 changed files
with
62 additions
and
72 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -19,5 +19,6 @@ | |
| ] | ||
| }, | ||
| "MD013": false, | ||
| "MD041": false | ||
| "MD041": false, | ||
| "MD026": false | ||
| } | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,81 +5,68 @@ redirect_from: | |
| - /nl-workshop2/ | ||
| --- | ||
|
|
||
| \[[Go back to CHECK-NL main page](/nl/)\] | ||
|
|
||
| ## Update from UTwente: Small is beautiful (and reproducible) | ||
|
|
||
| On the stormy morning of 26th September, despite disrupted train schedules, a small but determined group of codecheckers assembled at the Faculty of Geosciences and Earth Observation at the University of Twente for the second codecheck workshop of our project. The trains may not have run that day, but the code sure did! | ||
| On the stormy morning of 26th September, despite disrupted train schedules, a small but determined group of codecheckers assembled at the Faculty of Geosciences and Earth Observation at the University of Twente for the second codecheck workshop of our project. The trains may not have run that day, but the code sure did! | ||
|
|
||
| We began our morning with a round of introductions, and an intro to the project by Frank Ostermann, our PI. Shortly after, Stephen Eglen, one of the founders of codecheck, joined us virtually to introduce the concept and logistics of codecheck, and how it aligns with the goals of reproducibility in science. Following Stephen, Frank took over again to run us through a practical application of codecheck, drawing on examples from codechecks he has done as part of reproducibility reviews at previous [AGILE conferences](https://reproducible-agile.github.io/). | ||
| We began our morning with a round of introductions, and an intro to the project by Frank Ostermann, our PI. Shortly after, Stephen Eglen, one of the founders of codecheck, joined us virtually to introduce the concept and logistics of codecheck, and how it aligns with the goals of reproducibility in science. Following Stephen, Frank took over again to run us through a practical application of codecheck, drawing on examples from codechecks he has done as part of reproducibility reviews at previous [AGILE conferences](https://reproducible-agile.github.io/). | ||
|
|
||
| We took a break for an excellent warm lunch in the faculty canteen -- much needed in the gloomy weather -- and then delved straight into breakout groups for the afternoon. Four authors joined us with their submissions, which the breakout groups began to codecheck. Three were finished on the spot, and a fourth was begun and we agreed to complete it after the session. And voila! Completed codecheck certificates from the workshop are already available, [have a look](https://osf.io/m7tze/)! | ||
| We took a break for an excellent warm lunch in the faculty canteen -- much needed in the gloomy weather -- and then delved straight into breakout groups for the afternoon. Four authors joined us with their submissions, which the breakout groups began to codecheck. Three were finished on the spot, and a fourth was begun and we agreed to complete it after the session. And voila! Completed codecheck certificates from the workshop are already available, [have a look](https://osf.io/m7tze/)! | ||
|
|
||
| We wrapped up the day with an interesting reflection session. Along with the authors and codecheckers, we were also joined by Prof. Dr Alfred Stein, editor of the Journal of Spatial Statistics, and (virtually) Daniel Nuest, another founder of Codecheck. One of our goals in this project is to explore ways in which the codecheck workflow can be incorporated into journal submission processes, and a lively discussion followed on what codecheck can add to the review process, where in the review workflow codecheck could fit, and who would conduct them. As always, issues of reward and recognition were central to our discussions about codecheck. Have an idea about this? Join us at the next codecheck session in [Rotterdam](https://codecheckRotterdam.eventbrite.com)! | ||
| We wrapped up the day with an interesting reflection session. Along with the authors and codecheckers, we were also joined by Prof. Dr Alfred Stein, editor of the Journal of Spatial Statistics, and (virtually) Daniel Nuest, another founder of Codecheck. One of our goals in this project is to explore ways in which the codecheck workflow can be incorporated into journal submission processes, and a lively discussion followed on what codecheck can add to the review process, where in the review workflow codecheck could fit, and who would conduct them. As always, issues of reward and recognition were central to our discussions about codecheck. Have an idea about this? Join us at the next codecheck session in [Rotterdam](https://codecheckRotterdam.eventbrite.com)! | ||
|
|
||
| --------------------------------------------------------------------------------------------------- | ||
|
|
||
| ## CALL FOR PAPERS/PREPRINTS/CODE: Are you a researcher in geosciences/environmental sciences interested in reproducible code and Open Science? We have the perfect opportunity for you! | ||
|
|
||
| As part of our NWO project [CHECK-NL](https://codecheck.org.uk/nl), **we are looking for researchers from the field of geosciences/environmental sciences based 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 26 September 2024** at the University of Twente. 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/)). | ||
|
|
||
|
|
||
| ## CALL FOR PAPERS/PREPRINTS/CODE: Are you a researcher in geosciences/environmental sciences interested in reproducible code and Open Science? We have the perfect opportunity for you! | ||
|
|
||
| You can participate as a codechecker (i.e., a person reviewing code), or by submitting your own work to be checked (or both if you are up for it!). *Curious to know how it works? Read about our first [workshop in Delft](https://codecheck.org.uk/nl-workshop1/).* | ||
| As part of our NWO project [CHECK-NL](https://codecheck.org.uk/nl), **we are looking for researchers from the field of geosciences/environmental sciences based 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 26 September 2024** at the University of Twente. 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/)). | ||
|
|
||
| You can participate as a codechecker (i.e., a person reviewing code), or by submitting your own work to be checked (or both if you are up for it!). *Curious to know how it works? Read about our first [workshop in Delft](https://codecheck.org.uk/nl-workshop1/).* | ||
|
|
||
| Anyone is welcome to participate at the workshop. Participation is free of cost and includes lunch. We have limited funding (on a first come, first served basis) for reimbursing train tickets for PhD (non-AiO) students. PhD candidates who participate in the workshop can reach out to us about getting credits for participation, provided their supervisors and institutions/departments also agree. | ||
|
|
||
|
|
||
|
|
||
| ## What do I get if I submit my paper or pre-print? | ||
|
|
||
| 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. | ||
| ## What do I get if I submit my paper or pre-print? | ||
|
|
||
| The codechecker will work with you to resolve any issues found during the code check, and make your code as reproducible as possible! | ||
| 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. | ||
|
|
||
| Upon completion, your paper will receive a codecheck certificate that confirms your results could be reproduced. This can be shared, for instance with potential journal editors, to enhance the visibility and reproducibility of your work. | ||
| The codechecker will work with you to resolve any issues found during the code check, and make your code as reproducible as possible! | ||
|
|
||
| By participating, you contribute towards making science more open and transparent AND increase the visibility of your own research! | ||
| Upon completion, your paper will receive a codecheck certificate that confirms your results could be reproduced. This can be shared, for instance with potential journal editors, to enhance the visibility and reproducibility of your work. | ||
|
|
||
|
|
||
| ## Sounds good! What should I do? | ||
| By participating, you contribute towards making science more open and transparent AND increase the visibility of your own research! | ||
|
|
||
| Are you interested in participating in this event, and help contribute to promoting code reproducibility? Send an email to [email protected] **by 9 September 2024** with a *brief description of your paper/project, and links to your code and data*. This could be code related to: | ||
| ## Sounds good! What should I do? | ||
|
|
||
| - A paper that you have recently published | ||
| Are you interested in participating in this event, and help contribute to promoting code reproducibility? Send an email to <[email protected]> **by 9 September 2024** with a *brief description of your paper/project, and links to your code and data*. This could be code related to: | ||
|
|
||
| - A preprint that is publicly available | ||
| - A paper that you have recently published | ||
|
|
||
| - Code and results files that have been or will be deposited in a repository, preferably GitHub or GitLab | ||
| - A preprint that is publicly available | ||
|
|
||
| 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. | ||
| - Code and results files that have been or will be deposited in a repository, preferably GitHub or GitLab | ||
|
|
||
| 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 September 2024. All authors are invited to register join the workshop.** | ||
|
|
||
| **Selected papers/projects will be notified in early September 2024. All authors are invited to register join the workshop.** | ||
| ## What if I want to volunteer to be a codechecker instead? | ||
|
|
||
|
|
||
|
|
||
| ## What if I want to volunteer to be a codechecker instead? | ||
|
|
||
|
|
||
| If you are interested in learning more about the codecheck process and becoming a codechecker, please register on our [eventbrite page](https://www.eventbrite.nl/e/codecheck-workshop-for-the-geosciences-and-environmental-sciences-tickets-945474348227?aff=oddtdtcreator) to volunteer to become a codechecker at the workshop on 26th September. The event will be held in person at the University of Twente. | ||
|
|
||
| ### Why would I volunteer your time to code check other people's work? | ||
| ### Why would I volunteer your time to code check other people's work? | ||
|
|
||
| - Learn how others ensure reproducibility of their work | ||
| - Learn how others ensure reproducibility of their work | ||
|
|
||
| - Gaining hands-on experience in peer reviewing code | ||
|
|
||
| - Learn to make your own code more reproducible | ||
|
|
||
| - Contributing to more transparent science | ||
|
|
||
|
|
||
| - Contributing to more transparent science | ||
|
|
||
| *Interested but still have questions? Ask us!* | ||
| *Interested but still have questions? Ask us!* | ||
|
|
||
| Write to us at [email protected], we are happy to answer any questions! | ||
| Write to us at <[email protected]>, we are happy to answer any questions! | ||
|
|
||
| For questions related to the NWO project CHECK-NL, please contact Frank Ostermann ([email protected]) | ||
|
|
||
| For questions related to the NWO project CHECK-NL, please contact Frank Ostermann (<[email protected]>) | ||
Oops, something went wrong.