unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Spencer Skylar Chan <schan12@terpmail.umd.edu>
To: Ricardo Wurmus <rekado@elephly.net>,
	Simon Tournier <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org, Kyle Andrews <kyle@posteo.net>
Subject: Re: Google Summer of Code 2023 Inquiry
Date: Wed, 22 Mar 2023 17:44:52 -0400	[thread overview]
Message-ID: <b3c568c3-ec96-e3d1-4157-8bbdf56ff83c@terpmail.umd.edu> (raw)
In-Reply-To: <87ttycir7r.fsf@elephly.net>

Hi Ricardo,

On 3/22/23 14:19, Ricardo Wurmus wrote:
> 
>>> - Translating Snakemake to Guix Workflow Language (GWL)
>>
>> Ricardo, maybe you would have some suggestions. :-)
> 
> Oh, this looks interesting.  Could you please elaborate on the idea?
> 
My idea is to take as input a Snakemake workflow file and eventually 
output an equivalent GWL workflow file.

Currently, Snakemake workflows can be exported to CWL (Common Workflow 
Language):

https://snakemake.readthedocs.io/en/stable/executing/interoperability.html

One approach could be to add CWL import/export capabilities to GWL. Then 
Snakemake/GWL conversion would be a 2 step process, using CWL as an 
intermediate step:

1. Snakemake -> CWL
2. CWL -> GWL

However, CWL is not as expressive as Snakemake. There may be some 
details that are lost from Snakemake workflows.

So a 1-step Snakemake/GWL transpiler could be interesting, as both 
Snakemake/GWL use a domain-specific language inside a general purpose 
language (Python/Guile respectively). There may be a possibility to 
achieve more "accurate" translations between workflows.

Is this topic something that could fit into a summer project?


  reply	other threads:[~2023-03-23  0:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07  1:31 Google Summer of Code 2023 Inquiry Spencer Skylar Chan
2023-03-11 13:32 ` Simon Tournier
2023-03-14 10:10   ` Simon Tournier
2023-03-22 17:41   ` Spencer Skylar Chan
2023-03-22 18:19   ` Ricardo Wurmus
2023-03-22 21:44     ` Spencer Skylar Chan [this message]
2023-03-23  7:58       ` Ricardo Wurmus
2023-03-30 23:27         ` Spencer Skylar Chan
2023-03-31  0:52           ` Kyle
2023-03-24 18:59       ` Kyle
2023-03-30 23:22         ` Spencer Skylar Chan
2023-03-31 15:15           ` Kyle
2023-04-04  0:41             ` Spencer Skylar Chan
2023-04-04  6:29               ` Kyle
2023-04-04  8:59               ` Simon Tournier
2023-04-04 14:32                 ` Kyle
2023-04-04 17:15                   ` Simon Tournier
  -- strict thread matches above, loose matches on Subject: below --
2023-03-08  2:33 Spencer Skylar Chan

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=b3c568c3-ec96-e3d1-4157-8bbdf56ff83c@terpmail.umd.edu \
    --to=schan12@terpmail.umd.edu \
    --cc=guix-devel@gnu.org \
    --cc=kyle@posteo.net \
    --cc=rekado@elephly.net \
    --cc=zimon.toutoune@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.
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).