From: Simon TOURNIER <simon.tournier@inserm.fr>
To: "guix-science@gnu.org" <guix-science@gnu.org>
Subject: RE: Hackatathon: 27th June! Let redo ReScience C.
Date: Mon, 26 Jun 2023 16:05:50 +0000 [thread overview]
Message-ID: <7e052fbe1d7448648d72be2122949c08@inserm.fr> (raw)
In-Reply-To: <96e447087983499c890e1fc4db3e7f04@inserm.fr>
Hi
Tomorrow, do not miss the second Reproducible Research hackathon
using Guix:
*Tuesday June, 27th*. Start: 9h30 (CEST) End: 17h30
Please join at 9h30 the BigBlueButton instance,
https://bbb.inria.fr/cou-pmi-g09-ute
More details in [1]. Especially a PAD for keeping track of the plan and progress,
We suggest to pick articles from the ReScience C journal [2] -- they
provide a high level of transparency about the materials required for
redoing, IMHO. The aim of the day is to learn altogether how to produce research
reproducible papers [3] using Guix. The key points are:
+ writing the manifest file
+ describing the channel file
with various bonus points as archiving on Software Heritage.
1: https://hpc.guix.info/blog/2023/05/reproducible-research-hackathon-let-redo/
2: http://rescience.github.io
3: https://hpc.guix.info/blog/2023/06/a-guide-to-reproducible-research-papers/
Cheers,
simon
next prev parent reply other threads:[~2023-06-26 16:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 13:51 Hackatathon: 27th June! Let redo ReScience C Simon TOURNIER
2023-05-12 18:46 ` [Spam:]Hackatathon: " Konrad Hinsen
2023-05-17 17:10 ` Hackatathon: " Etienne B. Roesch
2023-05-24 13:31 ` Ludovic Courtès
2023-05-25 10:08 ` Etienne B. Roesch
2023-05-25 12:19 ` Konrad Hinsen
2023-05-25 12:31 ` Etienne B. Roesch
2023-05-25 12:40 ` Konrad Hinsen
2023-05-31 10:32 ` Simon Tournier
2023-05-31 17:14 ` Etienne B. Roesch
2023-06-26 16:05 ` Simon TOURNIER [this message]
2023-07-17 14:00 ` Hackatathon let redo, experience report Simon TOURNIER
[not found] <mailman.135.1684425636.22153.guix-science@gnu.org>
2023-05-18 17:15 ` Hackatathon: 27th June! Let redo ReScience C Peter Polidoro
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=7e052fbe1d7448648d72be2122949c08@inserm.fr \
--to=simon.tournier@inserm.fr \
--cc=guix-science@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.
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).