News for hackers. Stuff that matters.
Re:A Code Glitch May Have Caused Errors in More Than a Hundr... by Tistel on Saturday October 12, 2019 @03:34PM (#21235649)
Researchers should consider making their papers runnable. Jupyter notebooks being a great tool for it. Also, check out Knuth’s literate programming.
Re:A Code Glitch May Have Caused Errors in More Than a Hundr... by gwd on Saturday October 12, 2019 @05:47PM (#21236593)
I was going to say that would almost make things worse: right now these sorts of bugs are discovered by attempting to re-implement the described algorithm, and discovering that the described algorithm was wrong. If the code was available but wrong, most people would just run the code and find the same wrong answers as the original researchers.

But actually I think that's wrong; far more people would run the code than currently try to re-implement the code; and it's likely that someone will notice something fishy about the code and report it.

Re:A Code Glitch May Have Caused Errors in More Than a Hundr... by erichocean on Saturday October 12, 2019 @06:12PM (#21236739)
Well, we don’t have to wonder since this was done with PBRT.

Result? An incredibly high quality codebase with many hundreds of subtle fixes over time coming from readers and researchers.

Re:A Code Glitch May Have Caused Errors in More Than a Hundr... by zhdc1 on Saturday October 12, 2019 @04:08PM (#21235846)
This is standard practice in some fields. I'm helping an old colleague with one of their projects, and one of the requirements for publication is documented runnable code and all of the underlying data.

I'm still surprised that this isn't expected in other research areas.