Re:What makes software engineering for climate models differ...
by derefr on Sunday February 01, 2015 @08:27PM
(#8982364)
The impact of errors in climate model software engineering that causes the software to fail safely (crash, return no output, fail to compile, etc.) is zero, which is different than other industries—effectively, a climate model is only needed insofar as it is predicting something with higher precision than any other model we already have, and, when it fails (in essence, when it provides output with zero confidence), we simply fall back on what we were doing before we had it—sourcing our predictions from some other model, or perhaps relying on the "model" of our own intuition.
Of course, there are also software engineering errors that cause incorrect outputs from the model to be provided, and incorrectly high confidence to be attached to those predictions. But, given the kinds of errors commonly seen in similar fields (e.g. physics engines), I would expect the probability of those kinds of error to be far outweighed by the other kind, the 'clear errors' where the model encounters out-of-tolerance data, and can then either bail out or "taint" all computations going forward.
Of course, there are also software engineering errors that cause incorrect outputs from the model to be provided, and incorrectly high confidence to be attached to those predictions. But, given the kinds of errors commonly seen in similar fields (e.g. physics engines), I would expect the probability of those kinds of error to be far outweighed by the other kind, the 'clear errors' where the model encounters out-of-tolerance data, and can then either bail out or "taint" all computations going forward.