Open Code and Peer Review ⋆ Open Science Talk

"What CODE CHECK actually do is to run the code to make sure that the workflow can be reproduced. As Eglen explains in the podcast episode, they don’t evaluate the result or pass judgment on scientific merit.

That means that it can be fairly easy to cheat their system. However, and that is the beauty of open science, the source code is open. That means that at some point someone will probably discover any attempts to cheat the CODE CHECK-system....

Here are the benefits that Eglen showed during the Conference in 2019:

1. The author gets an early check that the “code works”: and gets a snapshot of code archived and increased trust in the stability of results.
2. The codechecker gets insight into the latest research and methods, credit from the community, and a citable object.
3. The publisher gets a citable certificate with code/data bundle to share and increase reputation of published articles.
4. Peer reviewers can see certificate rather than check the code themselves
5. the reader can check certificate and build upon work immediatley...."