3 ms·
Most scientists unfortunately lack the technical skill to make their code easy to run elsewhere... however I think it is getting better. Someday I would like t
by _yb2s 2y ago
Most scientists unfortunately lack the technical skill to make their code easy to run elsewhere... however I think it is getting better.
Someday I would like to see it a requirement that the code has to run anywhere with a single command, e.g. 'docker compose up' or such, and then automatically produce all of the figures and analysis in the paper. There have been some pushes to start journals where the articles themselves can't have any plots or numbers directly, but must automatically generate them from code on the journals servers, e.g. with something like R markdown. It hasn't caught on because the work and technical skill required is too much.
- jltsiren 2y agoThat's not the code from my point of view. That's the script that processes the output of the code. The actual code often needs nontrivial time and/or money to run, and you may need to spend some effort to match the resources you have with the resources the code needs.
- _yb2s 2y agoThe vast majority of papers, even computational ones can run in that way. If there are compute intensive steps, the same process can be done, with a step that includes the previous output, such that it only gets regenerated if the user manually deletes it. I usually do this with Makefiles.