From: zimoun <zimon.toutoune@gmail.com>
To: Kyle Meyer <kyle@kyleam.com>
Cc: Ricardo Wurmus <rekado@elephly.net>, gwl-devel@gnu.org
Subject: Re: [PATCH] workflow: Consider unspecified free inputs when checking cache.
Date: Tue, 25 Jun 2019 19:33:36 +0200 [thread overview]
Message-ID: <CAJ3okZ3tLoq-YcXoMvpjtRQTKV+W0DVDeHAH0h8-kChQ7fkjWQ@mail.gmail.com> (raw)
In-Reply-To: <874l4effs5.fsf@kyleam.com>
Hi,
On Tue, 25 Jun 2019 at 06:30, Kyle Meyer <kyle@kyleam.com> wrote:
>
> Ricardo Wurmus <rekado@elephly.net> writes:
> > I’m not sure if we should keep picking
> > inputs from the environment silently and by default, but your patch is
> > anyway more correct than what we had before.
>
> Hmm, for my use case, taking free inputs from the file system based on
> the current directory is the only method that I'm actually interested in
> (i.e. I don't see myself having any use for --input). Perhaps my
> thinking is too shaped by make/snakemake, and I don't fully grasp the
> approach GWL is trying to take.
I am not sure to fully understand the issue and all the recent changes.
One idea of GWL is to have a functional workflow: the
multi-composition of functions/processes. And free inputs
are--say--the argument of this function. Therefore, if you have many
samples and you need to apply the same workflow, then you just apply
the function to each sample with --input. I mean it is my
understanding of the approach. Maybe I have wrong...
All the best,
simon
next prev parent reply other threads:[~2019-06-25 17:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 3:48 [PATCH] workflow: Consider unspecified free inputs when checking cache Kyle Meyer
2019-06-24 13:54 ` Ricardo Wurmus
2019-06-25 4:30 ` Kyle Meyer
2019-06-25 17:33 ` zimoun [this message]
2019-06-25 18:33 ` Ricardo Wurmus
2019-06-26 1:31 ` Kyle Meyer
2019-06-26 7:05 ` Ricardo Wurmus
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=CAJ3okZ3tLoq-YcXoMvpjtRQTKV+W0DVDeHAH0h8-kChQ7fkjWQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=gwl-devel@gnu.org \
--cc=kyle@kyleam.com \
--cc=rekado@elephly.net \
/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).