From: zimoun <zimon.toutoune@gmail.com>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Feedback from JRES in Dijon
Date: Thu, 5 Dec 2019 16:52:47 +0100 [thread overview]
Message-ID: <CAJ3okZ2hKBPZNthZpBQ=xibxzjJu7_gO8HoEcAzxaZcNbR_0gg@mail.gmail.com> (raw)
In-Reply-To: <m1lfrqrd3f.fsf@khs-macbook.home>
Hi,
On Thu, 5 Dec 2019 at 16:45, Konrad Hinsen <konrad.hinsen@fastmail.net> wrote:
> > So they are doing physical simulation (fluid dynamics), so they don't
> > (can't) get the same result when running the same experiment
> > twice. They wart replicability, that is, even if the results are
> > different, they are close enough to each other that you have to draw
> > the same scientific conclusion, independent of your compiler or other
> > package inputs.
>
> That's a common point of view in the numerical simulation community.
> What the people defending it don't realize is that both reproducibility
> and replicability matter, but in different situations and for different
> reasons. Reproducibility matters for verification ("was the computation
> done correctly?"), replicability matters for validation ("was the
> computation the right one for the scientific question?").
If I might, one the best presentation [1] -- that I am aware of -- on
this. Sorry in French.
[1] https://webcast.in2p3.fr/video/les-enjeux-et-defis-de-la-recherche-reproductible
https://aramis.resinfo.org/wiki/lib/exe/fetch.php?media=pleniaires:aramis_keynote_enjeux-et-defis-recherche-reproductible_konrad_hinsen.pdf
Maybe we could convert it to an entry for the HPC blog. What do you think?
Cheers,
simon
next prev parent reply other threads:[~2019-12-05 15:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 14:16 Feedback from JRES in Dijon Julien Lepiller
2019-12-05 14:34 ` Pierre Neidhardt
2019-12-05 14:42 ` Julien Lepiller
2019-12-05 15:44 ` Konrad Hinsen
2019-12-05 15:52 ` zimoun [this message]
2019-12-06 7:07 ` Bengt Richter
2019-12-06 12:24 ` Konrad Hinsen
2019-12-07 16:35 ` Timothy Sample
2019-12-08 2:48 ` Bengt Richter
2019-12-08 4:11 ` Timothy Sample
2019-12-08 23:09 ` Bengt Richter
2019-12-09 5:23 ` Konrad Hinsen
2019-12-06 12:57 ` Konrad Hinsen
2019-12-10 16:57 ` Ludovic Courtès
2019-12-11 20:48 ` Konrad Hinsen
2020-01-07 16:05 ` Proposal for a blog contribution on reproducible computations Konrad Hinsen
2020-01-09 20:40 ` zimoun
2020-01-10 16:59 ` Ludovic Courtès
2020-01-10 17:19 ` zimoun
2020-01-10 18:53 ` Giovanni Biscuolo
2020-01-11 9:31 ` Konrad Hinsen
2020-01-11 14:05 ` Giovanni Biscuolo
2020-01-13 8:37 ` Ludovic Courtès
2020-01-14 9:06 ` Konrad Hinsen
2020-01-14 15:38 ` Ludovic Courtès
2020-01-14 16:18 ` Konrad Hinsen
2020-01-14 16:40 ` Ludovic Courtès
2020-01-10 17:03 ` Ludovic Courtès
2020-01-11 9:39 ` Konrad Hinsen
2020-01-15 22:20 ` Ludovic Courtès
2019-12-05 15:47 ` Feedback from JRES in Dijon zimoun
2019-12-05 14:39 ` Julien Lepiller
2019-12-05 15:42 ` zimoun
2019-12-10 17:06 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ3okZ2hKBPZNthZpBQ=xibxzjJu7_gO8HoEcAzxaZcNbR_0gg@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=konrad.hinsen@fastmail.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.