unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Konrad Hinsen <konrad.hinsen@cnrs.fr>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>,
	zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>, guix-hpc@gnu.org
Subject: Re: “Reproducible research articles, from source code to PDF”
Date: Sun, 21 Jun 2020 16:50:16 +0200	[thread overview]
Message-ID: <m1imfkxyl3.fsf@khs-macbook.home> (raw)
In-Reply-To: <m1pn9we3tg.fsf@fastmail.net>

Konrad Hinsen <konrad.hinsen@cnrs.fr> writes:

> Sounds fine. I am not much of a hackathon expert, so I don't propose
> myself for organizing this, but I can make a preselection of suitable
> submissions to the ReScience challenge (no proprietary software etc.)
> with comments about the specific challenges.

Here is my list of candidate projects. There are three general
categories:

1) Package old software that is of sufficiently wide interest
   (i.e. add to guix-past)
    - g77 (used in https://github.com/ReScience/submissions/issues/41)
    - SciPy ecosystem from 2007 (at least Python, NumPy, matplotlib)
      (used in https://github.com/ReScience/submissions/issues/14)

2) Package highly specialized research software

   These programs are too specialized for the Guix distribution, so
   "packaging" means writing a guix.scm. The long-term goal is to learn how
   to make this kind of packaging easier, to the point that scientists are
   willing to do it themselves. This means it must be doable with minimal
   Guile competence, ideally by modifying templates provided by experts.

   I have picked four cases, listed by increasing level of difficulty:

   a) https://github.com/ReScience/submissions/issues/42

   A rather standard Fortran code, with only the popular BLAS and LAPACK
   libraries as dependencies. Instructions are given for manual
   compilation.

   b) https://github.com/ReScience/submissions/issues/36

   A medium-sized Fortran program with a Makefile.

   c) https://github.com/ReScience/submissions/issues/41

   A mixed C-Fortran code from 2008, built with autotools. Looks simple,
   but the author did not succeed in compiling it on a modern machine
   because it requires the abandoned g77 compiler.

   d) https://github.com/ReScience/submissions/issues/20

   A medium-sized Fortran library with a Makefile. Tricky because it adds
   its own wrappers around the Fortran compiler.

3) Fully automated reproductions of results (typically figures)

   There is only one case (other than Ludo's which already uses Guix):

   - https://github.com/ReScience/submissions/issues/39

   A fully reproducible reproduction of two Open Source simulation software
   packages (C/C++), based on Debian and its debuerreotype system. The
   challenge is to demonstrate how Guix can do it better!

Cheers,
  Konrad
-- 
---------------------------------------------------------------------
Konrad Hinsen
Centre de Biophysique Moléculaire, CNRS Orléans
Synchrotron Soleil - Division Expériences
Saint Aubin - BP 48
91192 Gif sur Yvette Cedex, France
Tel. +33-1 69 35 97 15
E-Mail: konrad DOT hinsen AT cnrs DOT fr
http://dirac.cnrs-orleans.fr/~hinsen/
ORCID: https://orcid.org/0000-0003-0330-9428
Twitter: @khinsen
---------------------------------------------------------------------


  parent reply	other threads:[~2020-06-21 14:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16 12:25 “Reproducible research articles, from source code to PDF” Ludovic Courtès
2020-06-17  7:06 ` zimoun
2020-06-18  7:31   ` Ludovic Courtès
2020-06-18  9:37     ` Konrad Hinsen
2020-06-18 11:42       ` Ludovic Courtès
2020-06-18 12:56         ` zimoun
2020-06-18 13:05           ` Ludovic Courtès
2020-06-18 16:28             ` Konrad Hinsen
2020-06-19 12:04               ` Ludovic Courtès
2020-06-19 12:14                 ` zimoun
2020-06-19 13:21                   ` Ludovic Courtès
2020-06-21 14:50               ` Konrad Hinsen [this message]
2020-06-22  7:38                 ` Ludovic Courtès
2020-06-18 16:39             ` Pjotr Prins
2020-06-18  2:33 ` Maxim Cournoyer

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=m1imfkxyl3.fsf@khs-macbook.home \
    --to=konrad.hinsen@cnrs.fr \
    --cc=guix-devel@gnu.org \
    --cc=guix-hpc@gnu.org \
    --cc=ludovic.courtes@inria.fr \
    --cc=zimon.toutoune@gmail.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.
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).