From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Paul Garlick <pgarlick@tourbillion-technology.com>
Cc: guix-science@gnu.org
Subject: Re: reproducibility of numerical experiments
Date: Tue, 06 Apr 2021 09:18:50 +0200 [thread overview]
Message-ID: <87pmz7q3s5.fsf@inria.fr> (raw)
In-Reply-To: <ca6d393e30be6aab645c9417cc00ba8f818455c4.camel@tourbillion-technology.com> (Paul Garlick's message of "Sat, 03 Apr 2021 15:36:40 +0100")
Hi Paul,
Paul Garlick <pgarlick@tourbillion-technology.com> skribis:
> There were two questions on the day:
>
> i) Q: what happens if a repository disappears? Is the environment
> still reproducible?
> A: Yes. The Software Heritage Project provides a backup of all Guix
> packages. This is automatically used as a fallback, if needed.
>
> ii) Q: Suppose I am an end user who wishes to include some third-party
> python package, do I require it to exist as a Guix package to be able
> to have the "exact" reproducibility you described?
> A: There is a useful feature that allows a local channel to be
> defined. One can keep extra packages and one’s own solvers in the
> local channel. These are not visible in the main Guix repository but
> have all the same features regarding reproducibility.
OK.
>> Is the FenICS community generally aware of reproducible deployment
>> issues?
>
> Yes, reproducible deployment is seen as desirable, though difficult to
> achieve with the currently-used tools. Typically model development
> starts on a local workstation and is scaled-up to an HPC system when
> needed. Tools such as singularity are often used. However, the local
> and remote installations may differ and as a consequence applications
> that run on the local system may not run on the remote system.
>
>> It’s great to reach out to the numerical simulation community.
>> Reproducible deployment and numerical simulation are two links in the
>> long chain of reproducible science that we have to connect.
>
> Sure. My view is that Guix provides the machinery to transform what
> can be a stop-start mode of numerical model development to something
> that is more sustainable over time.
Interesting, thank you!
Ludo’.
prev parent reply other threads:[~2021-04-06 7:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 14:54 reproducibility of numerical experiments Paul Garlick
2021-04-02 15:11 ` Ludovic Courtès
2021-04-03 14:36 ` Paul Garlick
2021-04-06 7:18 ` Ludovic Courtès [this message]
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=87pmz7q3s5.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=guix-science@gnu.org \
--cc=pgarlick@tourbillion-technology.com \
/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).