From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: Lars-Dominik Braun <ldb@leibniz-psychology.org>,
Simon Tournier <zimon.toutoune@gmail.com>,
guix-science@gnu.org,
Simon Tournier <simon.tournier@u-paris.fr>
Subject: Re: [PATCH] Add draft post "CRAN, a practical example for being reproducible at large scale using GNU Guix".
Date: Fri, 16 Dec 2022 09:58:05 +0100 [thread overview]
Message-ID: <87tu1vk9nm.fsf@inria.fr> (raw)
In-Reply-To: <Y5wlpCDSvrIDi06L@noor.fritz.box> (Lars-Dominik Braun's message of "Fri, 16 Dec 2022 09:00:36 +0100")
Hello Lars,
Lars-Dominik Braun <lars@6xq.net> skribis:
>> As mentioned on #guix-hpc, I think it’d be interesting to add a
>> reference to https://www.nature.com/articles/s41597-022-01143-6 to
>> illustrate the rationale. I think it’s important because R users are
>> likely to wonder why they’d bother with Guix in the first place.
> from the article and the quotes in your patch I feel it’s not clear
> the execution failures are the result of mismatched dependencies. Sure,
> if I put on my Guix glasses I would assume they are at least partially
> responsible, but in “Limitations of the Study” they mention they did
> not investigate causes for the failures. So arguing that code quality
> in these open repositories is just terrible – as we can see from the
> automated cleaning step doing wonders – would be equally valid. Or am
> I missing something?
The point I wanted to make is that, instead of going through the hacks
they describe (R version guesswork, source “cleanup”) and yet being
unable to run a large part of the code, we could have a tool that
ensures *by construction* that one is going to be able to rerun the
code.
> You’re right that if the blog post would be published in a non-Guix
> context it would need a good reason to use Guix, but in this case I was
> just describing a cool new toy for people already using Guix. Is that
> mind-set acceptable for posts on hpc.guix.info or do we need a motivating
> section?
The way I see it, we’re trying to reach out to people who’re using R and
are interested in reproducible research. Their first reaction might be
“this sounds nice, but is it really necessary?”, or: “isn’t renv/packrat
already doing the job?” Guix fans already know the answers. :-)
Having said all that, you’re the author of the article, so let us know
whether you want to publish it as-is or to modify it, and we’ll go ahead
(I’ll be on IRC today). I think it’s already an insightful article!
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-12-16 8:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 7:53 [PATCH] Add draft post "CRAN, a practical example for being reproducible at large scale using GNU Guix" Lars-Dominik Braun
2022-12-06 12:51 ` Simon Tournier
2022-12-07 7:44 ` Efraim Flashner
2022-12-07 8:39 ` Lars-Dominik Braun
2022-12-07 11:11 ` Simon Tournier
2022-12-07 8:36 ` Lars-Dominik Braun
2022-12-13 13:53 ` Ludovic Courtès
2022-12-13 16:34 ` zimoun
2022-12-16 8:00 ` Lars-Dominik Braun
2022-12-16 8:58 ` Ludovic Courtès [this message]
2022-12-17 9:53 ` Lars-Dominik Braun
2022-12-17 11:43 ` Simon Tournier
2022-12-19 15:06 ` Lars-Dominik Braun
2022-12-21 14:43 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tu1vk9nm.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=guix-science@gnu.org \
--cc=lars@6xq.net \
--cc=ldb@leibniz-psychology.org \
--cc=simon.tournier@u-paris.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.