2 ms·
I kinda take issue with the approach vs. simply attempting to email the corresponding author, but I understand the premise. I think the onus really has to start
by asdff 6y ago
I kinda take issue with the approach vs. simply attempting to email the corresponding author, but I understand the premise. I think the onus really has to start coming from journals. I should be able to have the pieces to reproduce a given work, but often times I'm left short of either the data (or a very key portion of it) or the code, and methods often just state what tools were used (much of it boilerplate if you look at the same authors other papers with the same tooling), not how these tools were used on the input data in particular nor how the output is handled.
Reproducing a computational paper should be the easiest thing, but often times you are left in the weeds reading arcane documentation for tooling that hasn't been updated since that post doc left the group 6 years ago, and trying to piece together an appropriate pipeline, work that wouldn't have to be done if you could simply inspect the underlying code behind the figures presented in the text and see how these tools were used. I don't care if the pile of scripts is a sloppy mess, just give me a github repo with all the code used and a link to access the data from a public repository if it isn't under some form of controlled access (of which I should be able to easily apply for and also use for research purposes just like the original authors have done).
Journals should mandate that all code and data used to generate results be made available to the community, because it's clear that with no mandate in place people aren't exactly taking this onus on themselves, nor do reviewers seem to be asking for this information from authors.