unofficial mirror of gwl-devel@gnu.org
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: gwl-devel@gnu.org
Subject: Re: Rcwl
Date: Sun, 24 Feb 2019 15:52:38 +0100	[thread overview]
Message-ID: <CAJ3okZ3-OJMAA7UBw+USnA9kPVoru4L5+9eTSGqc+N8yS0cQ6g@mail.gmail.com> (raw)
In-Reply-To: <20190221154759.vd5p2c6boke25wwg@thebird.nl>

Hi Pjotr,


On Thu, 21 Feb 2019 at 17:56, Pjotr Prins <pjotr.public12@thebird.nl> wrote:
>
> This is a recent implementation of CWL in R:
>
>   https://github.com/hubentu/Rcwl

If I understand well, it is "just" a R front-end to cwltool.
Basically, it reads CWL files, it writes CWL files from R flavored
pipeline description and it runs CWL tools.

Naive question: what does they gain?
CWL extended by R?


From my opinion, the approach by SnakeMake is more interesting.
 1- they describes the workflow with snakemake and so it is natively
extendable with Python; then the "graph" is exported to CWL file.
 2- they imports a complete CWL workflow as a snakemake rule; then
this rule runs cwltool, and can be connected to any other snakemake
rules.

[1] https://snakemake.readthedocs.io/en/stable/executable.html#cwl-export
[2] https://snakemake.readthedocs.io/en/stable/snakefiles/modularization.html#common-workflow-language-cwl-support


> I am thinking for future use of GWL it would be of interest to support
> CWL output and maybe even a CWL runner. Maybe a Guile project for
> someone who wants to have a go.

We already had a discussion about this idea on guix-devel, one year ago. :-)

https://lists.gnu.org/archive/html/guix-devel/2018-01/msg00428.html

I agree that a "CWL engine" would be nice. I mean my mind has not
changed so much since last year. ;-)


What is blocking to push your guix-cwl channel to Guix master?


All the best
--
simon

      reply	other threads:[~2019-02-24 14:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-21 15:47 Rcwl Pjotr Prins
2019-02-24 14:52 ` zimoun [this message]

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=CAJ3okZ3-OJMAA7UBw+USnA9kPVoru4L5+9eTSGqc+N8yS0cQ6g@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=gwl-devel@gnu.org \
    --cc=pjotr.public12@thebird.nl \
    /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).