From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Niklas Holsti Newsgroups: comp.lang.ada Subject: Re: Not to incite a language war but apparently the Corona lockdown was based on 13 year old undocumented C-Code Date: Wed, 13 May 2020 01:20:11 +0300 Organization: Tidorum Ltd Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net jbo5cWVjeuLk0Jxg9+5oLAAdeTjUXnXb7nPZZ/J9jCxnRukH4c Cancel-Lock: sha1:KbfES/BEIg40D0qH5Sl8XU1aMYk= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 In-Reply-To: Content-Language: en-US Xref: reader01.eternal-september.org comp.lang.ada:58666 Date: 2020-05-13T01:20:11+03:00 List-Id: On 2020-05-13 0:27, Jeffrey R. Carter wrote: > On 5/12/20 9:16 PM, Niklas Holsti wrote: >>> >>> It seems clear that the code that was executed to create the >>> predictions was not deterministic on a single core. >> >> The first of the two cases of single-core "non-determinism" described >> and bewailed in the "review" is that the time evolution of the >> predicted epidemic is different depending on the value of a program >> option -- whether the "network" is created anew, or reused -- that >> should not affect the result. No actual non-determinism is claimed in >> the review, just that the epidemic reaches large infection rates >> sooner for one option value than for the other. It seems that the code >> was using the PRN generator slightly differently in the two cases, >> resulting in different PRN sequences. > > The single-core non-determinism that I gathered from the referenced > interpretation of the review, which I clearly have not studied as > carefully as you, was that the program gave different results on the > same computer for identical inputs: same initial conditions and same RNG > seed(s). That would indeed be non-determinism, also to me. > Perhaps I misunderstood, but that was what I got from it, and > the only part that seemed troubling. I agree that it would be troubling. If you could find that statement, it would interest me. I did not read all the bug reports and correction reports on github, so I can't claim to be sure there was no such real non-determinism, but I did not find examples in the review. The review claims that there were "many" bugs, but I don't trust the review on that. The review also says that the program's authors defended and seemed to accept "minor cases of non-determinism", but it was not clear what those cases are, if they are not the two examples discussed in the review. > This is different from the kind of non-determinism of simulations > that are intended to be run many times with different RNG seeds. Yes indeed, and I would not call that non-determinism of the code. The reviewer also condemned that kind of stochastic exploration and seemed to confuse it with real non-determinism. It is true that Monte Carlo is often used when the system being simulated is chaotic in some way so that its behaviour is essentially unpredictable, and can be so sensitive that no practical floating-point precision can give a truly reliable end result in any given simulation. > Possibly that would be caused by accessing uninitialized variables. Yes. -- Niklas Holsti niklas holsti tidorum fi . @ .