From: myglc2 <myglc2@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: leaky pipelines and Guix
Date: Mon, 07 Mar 2016 18:21:08 -0500 [thread overview]
Message-ID: <87twkhdgd7.fsf@gmail.com> (raw)
In-Reply-To: <87ziuavcfi.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 07 Mar 2016 10:56:33 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> myglc2 <myglc2@gmail.com> skribis:
>
>> ludo@gnu.org (Ludovic Courtès) writes:
>
> [...]
>
>>> Perhaps as a first step you could try and write a procedure and a CLI
>>> around it that simply runs a given pipeline:
>>>
>>> $ guix biopipeline foo frog.dna human.dna
>>> …
>>> /gnu/store/…-freak.dna
>>>
>>> The procedure itself would be along the lines of:
>>>
>>> (define (foo-pipeline input1 input2)
>>> (gexp->derivation "result"
>>> #~(begin
>>> (setenv "PATH" "/foo/bar")
>>> (invoke-make-and-co #$input1 #$input2
>>> #$output))))
>>
>> Sidebar:
>>
>> - What is "biopipeline" above? A new guix command?
>
> Right. Basically I was suggesting implementing the pipeline as a Scheme
> procedure (‘foo-pipeline’ above), and adding a command-line interface on
> top of it (‘guix biopipeline’.)
>
> This means that all inputs and outputs would go through the store, so
> you would get caching and all that for free.
>
> But I now understand that I was slightly off-topic. ;-)
Thanks. Having built bespoke analysis pipelines for the last five years,
I find your idea intriguing. So my response to the original post was
slightly off-topic. also ;)
next prev parent reply other threads:[~2016-03-07 23:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 11:25 leaky pipelines and Guix Ricardo Wurmus
2016-02-12 14:04 ` Ludovic Courtès
2016-03-04 23:29 ` myglc2
2016-03-07 9:56 ` Ludovic Courtès
2016-03-07 23:21 ` myglc2 [this message]
2016-03-05 11:05 ` Ricardo Wurmus
2016-03-07 9:54 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87twkhdgd7.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=help-guix@gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.