Re:Simple rules for documenting scientific software
by btrettel on Saturday December 22, 2018 @07:07PM
(#18743344)
The second link was fascinating and would make a good submission to HN.
> Given my experience with those who write them, I tend not to trust most conjugational results coming from science.
In computational fluid dynamics, there's a saying: No one believes computations aside from the person who ran them, and everyone believes experiments aside from the person who ran them.
To be fair, this is mostly because turbulence modeling can be very inaccurate, but bugs in the code are also a major concern of mine.
Re:Simple rules for documenting scientific software
by BeetleB on Sunday December 23, 2018 @12:37AM
(#18744629)
>The second link was fascinating and would make a good submission to HN.
It was - that's where I got it from.
Re:Simple rules for documenting scientific software
by petschge on Saturday December 22, 2018 @06:39PM
(#18743172)
Oh it is nothing new that HN is bashing code in science. But if anything that story is a reason for each group to build their own independent code instead of trying to enforce so much software engineering overhead until there is only one code by the best funded group is left because nobody else dares to (or can afford to) build their own code.
https://news.ycombinator.com/item?id=18368455
This is normal. Poor sw practices lead to bugs, which lead to invalid science.
Also
https://physicstoday.scitation.org/do/10.1063/PT.6.1.2018082...
This got caught because it led to a big fight. Most other scientific software is not audited at all. Given my experience with those who write them, I tend not to trust most conjugational results coming from science.