unofficial mirror of gwl-devel@gnu.org
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Josh Marshall <joshua.r.marshall.1991@gmail.com>
Cc: gwl-devel@gnu.org
Subject: Re: How do I support building a guix package over multiple machines in a cloud environment?
Date: Mon, 2 Dec 2019 20:00:07 +0100	[thread overview]
Message-ID: <CAJ3okZ0Z-FA2kpnn2BX1y=rafXhZ671cJ+s5OqxbiJU55a72Vw@mail.gmail.com> (raw)
In-Reply-To: <CAFkJGRcHeL7DqPfR9nGXGyV_Q1bVURmYJ9LOLD8eObW-pdJz9g@mail.gmail.com>

Hi (again) Josh :-)

On Mon, 2 Dec 2019 at 19:38, Josh Marshall
<joshua.r.marshall.1991@gmail.com> wrote:

> He uses it as a bioinformatics workflow to generate some analysis.  It

GWL should work for this use case. o/

> Is this kind of use case supported?  If so, how so?  Is nextflow not
> practical to keep?  Please, someone catch me up here so I can start to
> write code to help him out.  If this goes well, my company could
> integrate for gwl/guix in our work, which would be amazing.

Netxflow [1] is a Domain Specific Language (DSL): you write "rules"
and how these rules are combined together. In the bioinformatics
field, Snakemake [2] seems more popular. Other alternatives are CWL
[3], WDL [4], etc.

Basically, you describe:
 - what is the inputs
 - what is the outputs
 - how to process the inputs to produce the outputs

You can find examples there [*]. It uses the WISP syntax [5] but it
perfectly works with a Scheme-syntax if you prefer parenthesis. ;-)

[*] https://guixwl.org/


However, you should be interested by this blog post [#] by Pjotr using
Guix and CWL and other niceties!

[#] https://hpc.guix.info/blog/2019/01/creating-a-reproducible-workflow-with-cwl/

AFAIK, Nextflow is not yet packaged in Guix. One direction is to
package it and then use the workflow described in Nextflow DSL in the
spirit of [#]. One other direction is to rewrite the workflow using
the GWL DSL. It depends a bit on what is your final aim.


Hope that helps.
simon

[1] https://www.nextflow.io/
[2] https://snakemake.readthedocs.io/en/stable/
[3] https://www.commonwl.org/
[4] http://www.openwdl.org/
[5] https://srfi.schemers.org/srfi-119/srfi-119.html

  reply	other threads:[~2019-12-02 19:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02 17:36 How do I support building a guix package over multiple machines in a cloud environment? Josh Marshall
2019-12-02 19:00 ` zimoun [this message]
2019-12-02 20:02   ` pjotr.public12
2019-12-02 20:16     ` Josh Marshall
2019-12-02 21:00       ` zimoun
2019-12-02 20:03   ` Josh Marshall
2019-12-02 20:59     ` zimoun
2019-12-02 23:39 ` Ricardo Wurmus
2019-12-03  3:00   ` Josh Marshall
2019-12-03 11:03   ` zimoun
2019-12-03 13:47     ` Pjotr Prins

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='CAJ3okZ0Z-FA2kpnn2BX1y=rafXhZ671cJ+s5OqxbiJU55a72Vw@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=gwl-devel@gnu.org \
    --cc=joshua.r.marshall.1991@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.
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).