3 ms·
There's some other criticism (which I won't link because the text is partisan, and it's elsewhere on HN already) with some links that point to (potential or pe
by lbeltrame 6y ago
There's some other criticism (which I won't link because the text is partisan, and it's elsewhere on HN already) with some links that point to (potential or perceived) issues:
- https://github.com/mrc-ide/covid-sim/issues/116 https://github.com/mrc-ide/covid-sim/issues/116
- https://github.com/mrc-ide/covid-sim/issues/30 https://github.com/mrc-ide/covid-sim/issues/30
- acqq 6y agoBoth of these issues don't have any connection at all with any claim that the code could produce scientifically wrong results. The 116 is "if I use it this special way I would expect something else and not what I see" which can be simply answered with "well, don't do THAT." The simulations by design are not expected to produce exactly the same results in different runs. That's why they are simulations. The reporter tried some "partial save" and expected something else. The 30, if I understand correctly, is observed on Cray to behave in some minor detail not exactly the same as on the PC (which again doesn't have to even mean that the output is scientifically wrong). Seriously? If one is a Cray user, he can fix it, so what?