From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>,
guix-devel <guix-devel@gnu.org>
Cc: guix-hpc@gnu.org
Subject: Re: “Reproducible research articles, from source code to PDF”
Date: Wed, 17 Jun 2020 09:06:49 +0200 [thread overview]
Message-ID: <864kraxjau.fsf@gmail.com> (raw)
In-Reply-To: <87d05ztcxj.fsf@inria.fr>
Hi Ludo,
On Tue, 16 Jun 2020 at 14:25, Ludovic Courtès <ludovic.courtes@inria.fr> wrote:
> Hello!
>
> This new post introduces the work I did to have a fully reproducible
> replication (!) of a 13-year old article, using Guix to express the
> whole pipeline:
>
> https://hpc.guix.info/blog/2020/06/reproducible-research-articles-from-source-code-to-pdf/
Really cool!
IMHO, it even deserves an entry to guix.gnu.org/blog. :-)
Aside, I have learnt the interesting project maneage.org.
As always, it gives me some food for thought.
For example, they are future bridges to think: connect the Guix archive
somehow with zenodo DOI and/or Software Heritage identifier.
When I read this comment in the review [1]:
As a final note, I wonder if, and how much, the author's
approach to reproducible computation/automated report generation
is feasible for the average scientist, in particular when
compared to tools with a smoother learning curve, such as Docker
containers, Jupyter notebooks, R Markdown documents and the
like. A brief analysis of this topic with a clear presentation
of the advantages of the author's approach in the Discussion
session would be worthwhile.
and then the Konrad's answer [2], I asked myself what pieces are
missing. And what could be the articulation of "guix pack -f docker",
Guix-Jupyter or other notebooks (RMarkdown, Org)? And what could be a
practical workflow? (Keeping in mind that the average scientist is not a
Linux guru but often run MacOS or Windows.)
1: https://github.com/ReScience/submissions/issues/32#issuecomment-633739558
2: https://github.com/ReScience/submissions/issues/32#issuecomment-634149030
Half-related to the blog post. You mention elsewhere this baby channel
[3], maybe it could be worth to link it somewhere in the blog post.
Moreover, totally unrelated, I feel it lacks a list of "Scientific"
channels, as [4] or [5], maybe on hpc.guix.info
3: https://gitlab.inria.fr/guix-hpc/guix-past
4: https://github.com/BIMSBbioinfo/guix-bimsb
5: https://gitlab.inria.fr/guix-hpc/guix-hpc
Thanks,
simon
next prev parent reply other threads:[~2020-06-17 7:07 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 [this message]
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
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=864kraxjau.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=guix-hpc@gnu.org \
--cc=ludovic.courtes@inria.fr \
/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).