> You forgot to attach the link, but I guess you meant this project [1].
Sorry for forgot the link and my delay in reply.
The link you provided is correct:
https://github.com/gems-uff/noworkflow
signature.asc
Description: Digital signature
___
Discuss
Hi all,
Greg just contacted me and suggested that I might want to participate in this
discussion, as I've been discussing another provenance tool with him
(a Software Carpentry blog post will be coming shortly).
The tool is called 'recipy' [1] and is described in more detail in my blog
post [2].
Good idea, Peter - I've created a discussion issue on GitHub here [1],
and I'd be grateful if people could add comments to it instead of
sending replies to this list. I'll collate and turn into a blog post.
Thanks,
Greg
[1] https://github.com/swcarpentry/site/issues/1085
On 2015-09-07 11:02
I'm really interested in this field (and scientific workflow systems more
generally), but perhaps we should get this off the Discuss list. NoWorkflow
uses Prolog for reasoning across its workflow traces - this approach has
been mentioned previously in Bowers, McPhillips and Anand et al's work
("Pro
Hi Raniere,
You forgot to attach the link, but I guess you meant this project [1].
We have developed similar project, called sumatra, to track provenance
for python and non-python projects [2,3]
Sumatra has been used so far in neural modelling and data analysis, but
I am not aware of any rep
Hi everyone,
during last Spring I watched one talk from João Felipe, in copy,
about his M.S. project noWorkflow [1] that is under MIT license and briefly
aims at allowing scientists to benefit from provenance data analysis even
when they don't use a workflow system.
João contacted me be
