From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: guix-devel@gnu.org
Subject: Re: Use guix to distribute data & reproducible (data) science
Date: Fri, 9 Feb 2018 20:15:28 +0100 [thread overview]
Message-ID: <1cb709d0-b282-192c-ce1d-20fbff43430e@fastmail.net> (raw)
In-Reply-To: <87mv0ixf07.fsf@gnu.org>
Hi,
On 09/02/2018 18:13, Ludovic Courtès wrote:
> Amirouche Boubekki <amirouche@hypermove.net> skribis:
>
>> tl;dr: Distribution of data and software seems similar.
>> Data is more and more important in software and reproducible
>> science. Data science ecosystem lakes resources sharing.
>> I think guix can help.
>
> Now, whether Guix is the right tool to distribute data, I don’t know.
> Distributing large amounts of data is a job in itself, and the store
> isn’t designed for that. It could quickly become a bottleneck. That’s
> one of the reasons why the Guix Workflow Language (GWL) does not store
> scientific data in the store itself.
I'd say it depends on the data and how it is used inside and outside of
a workflow. Some data could very well stored in the store, and then
distributed via standard channels (Zenodo, ...) after export by "guix
pack". For big datasets, some other mechanism is required.
I think it's worth thinking carefully about how to exploit guix for
reproducible computations. As Lispers know very well, code is data and
data is code. Building a package is a computation like any other.
Scientific workflows could be handled by a specific build system. In
fact, as long as no big datasets or multiple processors are involved, we
can do this right now, using standard package declarations.
It would be nice if big datasets could conceptually be handled in the
same way while being stored elsewhere - a bit like git-annex does for
git. And for parallel computing, we could have special build daemons.
Konrad.
next prev parent reply other threads:[~2018-02-09 19:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 16:32 Use guix to distribute data & reproducible (data) science Amirouche Boubekki
2018-02-09 17:13 ` Ludovic Courtès
2018-02-09 17:48 ` zimoun
2018-02-09 19:15 ` Konrad Hinsen [this message]
2018-02-09 23:01 ` zimoun
2018-02-09 23:17 ` Ricardo Wurmus
2018-02-12 11:46 ` Konrad Hinsen
2018-02-14 4:43 ` Do you use packages in Guix to run neural networks? Fis Trivial
2018-02-14 6:07 ` Pjotr Prins
2018-02-14 7:27 ` Fis Trivial
2018-02-14 8:04 ` Konrad Hinsen
2018-02-10 9:51 ` Use guix to distribute data & reproducible (data) science Amirouche Boubekki
2018-02-10 11:28 ` zimoun
2018-02-14 13:06 ` Ludovic Courtès
2018-02-15 17:10 ` zimoun
2018-02-16 9:28 ` Konrad Hinsen
2018-02-16 14:33 ` myglc2
2018-02-16 15:20 ` Konrad Hinsen
2018-02-16 12:41 ` Amirouche Boubekki
-- strict thread matches above, loose matches on Subject: below --
2018-02-16 16:43 Amirouche Boubekki
2018-02-17 22:21 ` Roel Janssen
2018-02-18 23:42 ` Ludovic Courtès
2018-02-19 7:57 ` Ricardo Wurmus
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=1cb709d0-b282-192c-ce1d-20fbff43430e@fastmail.net \
--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 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.