From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: guix-science@gnu.org
Subject: Guix 1.2.0 & reproducible research
Date: Mon, 30 Nov 2020 16:17:21 +0100 [thread overview]
Message-ID: <877dq2nabi.fsf@inria.fr> (raw)
Hello!
Some news to break the silence on this list…
On the Guix-HPC blog, we announced last week what HPC practitioners and
scientists interested in reproducible research may like from the new
1.2.0 release:
https://hpc.guix.info/blog/2020/11/hpc-reproducible-research-in-guix-1.2.0/
A bit earlier, Konrad Hinsen wrote an article entitled “The four
possibilities of reproducible scientific computations” that in my
opinion very nicely summarizes requirements for a “reproducible
computation” and their implications:
https://blog.khinsen.net/posts/2020/11/20/the-four-possibilities-of-reproducible-scientific-computations/
It effectively rules out pre-built binaries (Docker images) as well as
SaaSS (Binder), but it does so in a way that demonstrates how they fail
some of the basic high-level criteria rather than entering a technical
debate.
Ludo’.
reply other threads:[~2020-11-30 15:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877dq2nabi.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=guix-science@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).