From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: gwl-devel@gnu.org
Subject: Re: Next steps for the GWL
Date: Mon, 3 Jun 2019 17:16:13 +0200 [thread overview]
Message-ID: <CAJ3okZ3N9n8LTJx3Ore6+hKM5xk211dQp_B8DqKynUGekgJzEQ@mail.gmail.com> (raw)
In-Reply-To: <87a7f5l6e1.fsf@mdc-berlin.de>
Hi Ricardo,
On Wed, 29 May 2019 at 16:41, Ricardo Wurmus
<ricardo.wurmus@mdc-berlin.de> wrote:
>
> I’m going to use the GWL in the next few days to rewrite the PiGx RNAseq
> pipeline from Snakemake. This will likely show me what features are
> still missing from the GWL and what implemented features are awkward to
> use.
Awesome!
> * tighter integration with Guix features, e.g. to export a container
> image per process via “guix pack” or to pack up the whole workflow as
> a relocatable executable.
Yes! Awesome.
Relocatable tarballs. Docker images. Singularity one.
And maybe generate one pack (docker) per process and something to glue
together, e.g.,
http://www.genouest.org/godocker/
> * explore the use of inferiors — the GWL should be usable with any
> version of Guix that may be installed, not just the version that was
> used at compilation time. Can we use “guix repl” and inferiors,
> perhaps?
For reproducibility, a Guix commit should be provided and a `guix
pull` (inferiors) should be used.
For example, the output of `guix describe -f channels` should be used,
either with an option, either directly in the Scheme/Wisp workflow
file with a new keyword.
>
> * add support for executing processes in isolated environments
> (containers) — this requires a better understanding of process inputs.
Maybe this is the same story than the GoDocker above.
Talking about ideas:
- what about the Content Adressable Store?
- what about a bridge with CWL?
Thank you to revive the list. :-)
All the best,
simon
next prev parent reply other threads:[~2019-06-03 15:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 13:47 Next steps for the GWL Ricardo Wurmus
2019-06-03 15:16 ` zimoun [this message]
2019-06-03 16:18 ` Ricardo Wurmus
2019-06-06 11:07 ` zimoun
2019-06-06 12:19 ` Ricardo Wurmus
2019-06-06 13:23 ` Pjotr Prins
2019-06-06 3:19 ` Kyle Meyer
2019-06-06 10:11 ` Ricardo Wurmus
2019-06-06 10:55 ` zimoun
2019-06-06 11:59 ` Ricardo Wurmus
2019-06-06 13:44 ` Pjotr Prins
2019-06-06 14:06 ` Pjotr Prins
2019-06-06 15:07 ` Kyle Meyer
2019-06-06 20:29 ` Ricardo Wurmus
2019-06-07 4:11 ` Kyle Meyer
2019-06-12 9:46 ` 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
List information: https://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ3N9n8LTJx3Ore6+hKM5xk211dQp_B8DqKynUGekgJzEQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=gwl-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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).