From: zimoun <zimon.toutoune@gmail.com>
To: guix-devel@gnu.org
Subject: Guix Workflow Language ?
Date: Wed, 24 Jan 2018 15:25:01 +0100 [thread overview]
Message-ID: <CAJ3okZ13w0TXuWnpoKJ7=S3id4Sn7bgydxq3uyL_tT47Q7dv6g@mail.gmail.com> (raw)
Dear,
Thank you to provide a workflow manager!
It is fun. :-)
I am currently investigating to describe basic and simple workflows.
And there is a couple of solutions, from python-oriented Snakemake
with Conda capabilities to Common Workflow Language or Workflow
Description Language.
https://snakemake.readthedocs.io/en/latest/
http://www.commonwl.org
https://software.broadinstitute.org/wdl/
And there is already some pipelines elsewhere, e.g.,
https://view.commonwl.org/workflows?search=rnaseq
https://github.com/UMCUGenetics/GGR-cwl
Moreover, some hyper-specialised and classical genomics pipelines are
also available elsewhere, e.g.,
http://bioinformatics.mdc-berlin.de/pigx/
Well, my question is: does it appear to you reasonable to write a
front-end for CWL ?
Because it seems hard to have some room in this landscape, even if I
think that the Guix-way is the most scientific (reproducible, open,
etc.).
I mean, there is room for a guix-backend engine (another CWL
implementation), I guess.
So, during a raining week-end, I gave a look to the specs of CWL and
why not start by define a subset, but then I have failed to write a
parser of it in Guile.
Hum? another question: does it exist an easy-to-use Guile library for
parsing YAML-like files ?
I have found Racket ones, but it was not clear to me how to do with
Guile (without reinventing the wheel).
What do you think about feeding GWL engine by CWL pipeline ?
Thank you for any advice.
All the best,
simon
next reply other threads:[~2018-01-24 14:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 14:25 zimoun [this message]
2018-01-24 20:07 ` Guix Workflow Language ? Roel Janssen
2018-01-25 16:16 ` zimoun
2018-01-25 20:36 ` Ricardo Wurmus
2018-01-25 22:04 ` Roel Janssen
2018-01-25 22:23 ` Cook, Malcolm
2018-01-26 13:05 ` Pjotr Prins
2018-01-29 16:55 ` zimoun
2018-01-30 1:57 ` Ricardo Wurmus
2018-02-15 17:28 ` zimoun
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='CAJ3okZ13w0TXuWnpoKJ7=S3id4Sn7bgydxq3uyL_tT47Q7dv6g@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).