3 ms·
Your argument doesn't seem to apply to most code in natural sciences. The difference being that their theoretical models are, in most cases, only approximated b
by stygianguest 16y ago
Your argument doesn't seem to apply to most code in natural sciences.
The difference being that their theoretical models are, in most cases, only approximated by code.
Yet, in papers, they claim to prove or test their theoretical model by experiments on the approximation.
Note that this is nothing terribly new.
Sometimes experiments testing a hypothesis give false positives because something went wrong in the experiment.
In that sense there is no real difference between a faulty thermometer and a bug in your code.
Having written this, I think your argument in fact does apply after all.
In natural sciences one would argue that if your buggy code confirms an invalid hypothesis, someone redoing your argument with the same code would not uncover the problem. Publishing your code invites people to use your faulty thermomenter.
Of course I'm assuming that the published paper contains all necessary details to reproduce the experiment.
In case of e.g. climate models or modelling the formation of galaxies that might be a problem because the code _is_ the experiment.
Describing what code does is very hard, and it would be easier to just publish it in stead.
- jonhendry 16y ago" Describing what code does is very hard, and it would be easier to just publish it in stead.' Depends on what level you're describing it. "It does an FFT" or "it sorts" are pretty clear. It gets hairy if you describe the specific details of the implementations. But the implementation is likely irrelevant, because other scientists can choose any implementation. Even with complex models you ought to be able to piece much of them together out of descriptions at that higher level.
- deleted 16y ago[deleted]
- stygianguest 16y agoTrue, but I was thinking more of numerical solutions to partial differential equations and the like.