My capstone example for Data Management in the Weather and Climate Sciences teaches a simple method for recording provenance that doesn't require any formal tools (only the ability to write command line programs): http://damienirving.github.io/capstone-oceanography/03-data-provenance.html
On Mon, Sep 7, 2015 at 6:01 AM, Greg Wilson <[email protected] > wrote: > There was a discussion on the blog about simple provenance tools back in > 2012 [1], and Robin Wilson recently introduced me to another Python-only > tool called recipy [2]. What do people on this list currently use to track > the provenance of their original data sets and their intermediate and final > results? How well does it work across languages? How easy was it to > learn, and how much effort does it take day-to-day? > > Thanks, > Greg > > [1] > http://software-carpentry.org/blog/2012/10/wanted-an-entry-level-provenance-library.html > > [2] https://github.com/recipy/recipy > > On 2015-09-07 10:39 AM, Bartosz wrote: > >> 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 reports describing use of sumatra in real world >> projects. Perhaps, you could contact the main developer, Andrew Davison (in >> cc), who might be able to provide you with more information. >> >> Yours, >> >> Bartosz >> >> [1] https://github.com/gems-uff/noworkflow >> [2] http://pythonhosted.org/Sumatra/ >> [3] https://osf.io/rc5jf/ >> >> 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 because he is looking for open science projects >>> under developing that he could use as examples for noWorkflow >>> or that are interested in testing noWorkflow (I'm sure that he will be >>> happy >>> to help you doing it as easy as possible if this is the case). >>> >>> Since I think that many people in this list could be interested >>> in João's project I'm sending this email. >>> You can contact João directly. >>> >>> Cheers, >>> Raniere >>> >>> _______________________________________________ >>> Discuss mailing list >>> [email protected] >>> >>> http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org >>> >> >> >> _______________________________________________ >> Discuss mailing list >> [email protected] >> >> http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org >> > > -- > Dr. Greg Wilson | [email protected] > Software Carpentry | http://software-carpentry.org > > > _______________________________________________ > Discuss mailing list > [email protected] > > http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
