Re:Challenge to scientists: does your ten-year-old code stil...
by vngzs on Monday August 24, 2020 @12:16PM
(#24262102)
Alternatively: seed the program randomly by default, but allow the user to specify a seed as a CLI argument or function argument (for tests).
In the common case, the software behaves as expected (random output), but it is reproducible for tests. You can then publish your RNG seed with the commit hash when you release your code/paper, and others may see your results and investigate that particular code execution.
Re:Challenge to scientists: does your ten-year-old code stil...
by petschge on Monday August 24, 2020 @12:22PM
(#24262163)
Sure that works too. But word of advice from real life: Print the random seed at the beginning of the run so you can find out which seed caused it to crash or do stupid things.
In the common case, the software behaves as expected (random output), but it is reproducible for tests. You can then publish your RNG seed with the commit hash when you release your code/paper, and others may see your results and investigate that particular code execution.