From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <20190613034821.1705513-1-kyle@kyleam.com> <874l4ft7gl.fsf@elephly.net> <874l4effs5.fsf@kyleam.com> In-Reply-To: <874l4effs5.fsf@kyleam.com> From: zimoun Date: Tue, 25 Jun 2019 19:33:36 +0200 Message-ID: Subject: Re: [PATCH] workflow: Consider unspecified free inputs when checking cache. Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable To: Kyle Meyer Cc: Ricardo Wurmus , gwl-devel@gnu.org List-ID: Hi, On Tue, 25 Jun 2019 at 06:30, Kyle Meyer wrote: > > Ricardo Wurmus writes: > > I=E2=80=99m 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