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>
Cc: Simon Tournier <zimon.toutoune@gmail.com>,
	guix-devel@gnu.org, Kyle Andrews <kyle@posteo.net>
Subject: Re: Google Summer of Code 2023 Inquiry
Date: Thu, 30 Mar 2023 19:27:37 -0400	[thread overview]
Message-ID: <c4218892-75f5-1a0d-9674-287bacde3730@terpmail.umd.edu> (raw)
In-Reply-To: <87zg81hki5.fsf@mdc-berlin.de>

Hi Ricardo,

On 3/23/23 03:58, Ricardo Wurmus wrote:
> Hi,
> 
> Spencer Skylar Chan <schan12@terpmail.umd.edu> writes:
> 
>> 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
> 
> This seems doable.

Great! I've been reading the chapter in Evolutionary Genomics on 
different scalable workflows to understand this process better.

>> 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.
> 
> Compared to the previous approach this seems vastly more complex.  It’s
> one thing to *execute* Snakemake code without running it through Python,
> but quite a bit more challenging to transpile Python to Scheme.
> 
> Personally, I wouldn’t know where to start.  Do you have an idea
> already?
> 

Actually I was hoping you might have some ideas :)
I do think that if the execution of the pipeline is more important than 
its representation (Snakemake or otherwise), then it would make more 
sense to focus efforts on increasing GWL's capabilities.

Thanks,
Skylar


  reply	other threads:[~2023-03-30 23:27 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
2023-03-23  7:58       ` Ricardo Wurmus
2023-03-30 23:27         ` Spencer Skylar Chan [this message]
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=c4218892-75f5-1a0d-9674-287bacde3730@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).