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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a37:9e52:: with SMTP id h79mr9092993qke.467.1591896521614; Thu, 11 Jun 2020 10:28:41 -0700 (PDT) X-Received: by 2002:a9d:7852:: with SMTP id c18mr7425094otm.82.1591896521394; Thu, 11 Jun 2020 10:28:41 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!aioe.org!peer03.ams4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Thu, 11 Jun 2020 10:28:41 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: google-groups.googlegroups.com; posting-host=208.114.128.24; posting-account=MRPdDAoAAADUJmZVjnYaoafXFMadSeY1 NNTP-Posting-Host: 208.114.128.24 References: User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <6bd5d971-6101-4e9e-aac3-7c5c2a8390abo@googlegroups.com> Subject: Re: Not to incite a language war but apparently the Corona lockdown was based on 13 year old undocumented C-Code From: Olivier Henley Injection-Date: Thu, 11 Jun 2020 17:28:41 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Received-Bytes: 5809 X-Received-Body-CRC: 389455194 Xref: reader01.eternal-september.org comp.lang.ada:59041 Date: 2020-06-11T10:28:41-07:00 List-Id: On Saturday, May 16, 2020 at 1:01:05 AM UTC-4, Anatoly Chernyshev wrote: > "Clowns will dominate the pandemic-forecasting domain..." >=20 > I like that one... >=20 > Oh dear, you've lured me out. As a person who just published a Covid-19 f= orecasting model programmed in Ada, I can't stay away from this heated conv= ersation. >=20 > There are so many concerns raised about scientists doing their rookie pro= gramming without resorting to professionals, so I don't even know where to = start. >=20 > First of all, we are curious bunch, and learning something new (like prog= ramming) is always fun. Second, in scientific programming the chance that s= omeone in power will lock down a country based on the output of your progra= m is negligible (certainly it wasn't on the radars 13 years ago). Third, fo= urth...=20 >=20 > To make a long story short, for the experiment's sake, is there anyone wi= lling to review my code? It's not a marvel of Ada programming, it just work= s. >=20 > Yet it's quite short - I went from the model's formulation, programming, = testing, data acquisition, manuscript writeup in a matter of a fortnight. >=20 > If the review is useful, in terms that it helps to produce more accurate = forecasts or identifies a drastic flaw in the code, I would be more than ha= ppy to do a revised version of the manuscript in a coauthorship with the re= viewer(s). Or even go for a peer-reviewed publication when dust settles. >=20 > The model forecasts are here: > April 10th: https://xph.co.nz/temp/album/ > May 12th: https://xph.co.nz/temp/album2005/ > Some technical details: https://xph.co.nz/index.php/covid-19-progression-= model/ > The model description: https://www.medrxiv.org/content/10.1101/2020.04.03= .20052985v1 >=20 > This is not an epidemiology-based model (so you don't have to be one). Ra= ther, it's a phenomenological one. It can predict what will happen, but can= 't (yet) say why this will happen. A contribution on the model is welcomed = too. >=20 > The code is not published (since I didn't expect anyone would care), but = I'll do it once there's interest. >=20 > If keen, please write to me directly: a~at~xph~dot~co~dot~nz >=20 > Anatoly Hi Anatoly, Maybe, if you agree, are interested, and your code is not a nightmare to wo= rk with (refactor to expose things needed to drive it in UI), I could find = time to code a graphical tool for it. Please consider what I did for Gautie= r's work (the screenshot does not show but everything is dynamic and the ex= port to .csv works like a charm). It took me half a day learning the qt5ada= binding on the fly: https://github.com/ohenley/covidsim My plan would be quite straightforward; in loose Model-View-Controller term= inology: 1. Take your 'engine/simulation' code, make a git repo, publish it as a for= k on GitHub. No fork this time if your code is not on GitHub already. Would= be best for you to own it (create a Github user, upload your code, etc. Bu= t if you are not up to that, I will take care of it. You can collaborate on= my repo with proper credentials explicitly set anyways.) 2. I refactor your code to push at the frontier, only parameters and simula= tion outputs to be driven/drive the UI layer. I do not touch the simulation= calculations, this is not my expertise, and if the engine internals break = I want *you* to fix it. I only/mostly touch on the inputs and outputs of th= ose computes for them to become parametrizable externally. (This layer is t= he Model, your know-how.) 3. I create the visual layer, expose the parameters and behavior we want fo= r the tool. (This layer is the View and Controller). I make another git rep= o out of this. This layer owns your layer to 'talk' with it. We end up we 2 codebase/repos, like that, you and other scientists can fix = the 'engine' without me knowing/caring because you touch on the 'model' lay= er only. Anytime you come up with new features/computations etc working, you tell me= , I repeat steps 2. and 3. to have the feature exposed in the visual tool. Let me know what you think if you are interested. I will forward this to yo= ur mail too. Olivier p.s: If your codebase is huge/complex/lot of features maybe we can start to= expose only a subset in a tool. From there, because it's available through= github, people in this thread could collaborate (clone, edit, push)