5 ms·
One example: My code used to crash for a long time if you set the thermal speed to something greater than the speed if light. Should the code crash? No. And by
by petschge 6y ago
One example: My code used to crash for a long time if you set the thermal speed to something greater than the speed if light. Should the code crash? No. And by now I have found the time to write extra code to catch the error and midly insult the user (It says "Faster than light? Please share that trick with me!") Does it matter? No. It didn't run and give plausible-but-wrong results. So that is code that I would call "science-ready" but I wouldn't want it criticized by people outside my domain.
- gowld 6y agoThen you publish your work and critics publish theirs and the community decides which claims have proven their merit. This is the fundamental structure of the scientific community. How is "your code has error and I rebuke you" a more painful critique than "you are hiding your methodology and so I rebuke you"?
- petschge 6y agoNothing limits the field of critics to people who have written their own code and know what they are doing.
- jnxx 6y agoI don't think that would be any problem (why should it?). Code exhibiting undefined behavior is a different kettle of fish...
- petschge 6y agoWhich is why I run valgrind on my code (with a parameter file containing physically valid inputs) to get rid of all undefined behavior. But I gave up on running afl-fuzz, because all it found was crashes following from physically invalid inputs. I fixed the obvious once to make the code nicer for new users, but once afl started to find only very creative corner cases I stopped.
- jnxx 6y agoWell done!