unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Guix Devel <guix-devel@gnu.org>
Subject: An occasion to demonstrate Guix for reproducible research
Date: Sun, 24 Nov 2019 19:53:32 +0100	[thread overview]
Message-ID: <m1eexxm7gz.fsf@khs-macbook.home> (raw)

Hi Guix,

For those of you working in scientific research, here's an occasion
to show the utility of Guix to the world: the ten-year reproducibility
challenge run by the journal ReScience. You can find the announcement
below.

The main role I see for Guix in this challenge is to ensure
reproducibility for the future, possibly resurrecting old versions of
packages in the process. I proposed two reproduction attempts myself for
this challenge, and I intend to package all dependencies in Guix
and add instructions to my code on how to reproduce it exactly
using "guix time-machine".

Cheers,
  Konrad


Did you ever try to run an old code that you wrote for a scientific
article you published years ago? Did you encounter any problems? Were
you successful? We are curious to hear your story. This is the reason
why we are editing a special issue of ReScience to collect these
stories.

The Ten Years Reproducibility Challenge is an invitation for researchers
to try to run the code they’ve created for a scientific publication that
was published more than ten years ago . This code can be anything
(statistical analysis, numerical simulation, data processing, etc.), can
be written in any language and can address any scientific domain. The
only mandatory condition to enter the challenge is to have published a
scientific article before 2010 , in a journal or a conference with
proceedings, which contains results produced by code, irrespectively of
whether this code was published in some form at the time or not.

Note that we do not ask you to write a new version of your old code. We
ask you instead to try to make your old code to run on modern
hardware/software (with minimal modifications) in order to check if you
can obtain the exact same results that were publised at least ten years
ago.

Sounds easy? We have good reasons to think this might be more difficult
than you think. And maybe the first problem you’ll have to solve is to
find your own source code.

More information at: http://rescience.github.io/ten-years/ 

             reply	other threads:[~2019-11-24 18:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-24 18:53 Konrad Hinsen [this message]
2019-11-24 19:31 ` An occasion to demonstrate Guix for reproducible research brettg

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=m1eexxm7gz.fsf@khs-macbook.home \
    --to=konrad.hinsen@fastmail.net \
    --cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).