[Swift-devel] Re: oops provenance

[Ben Clifford]

If you want to look at the provenance db as it is now, read sections 2 and 
3 of this page:

http://www.ci.uchicago.edu/~benc/provenance.html#owndb

I recommend if you try this at home to use sqlite3, not postgres.

> I think a starting point for oops provenance is this: For every run, you want
> to know:

many of these are straightforward to add, and i will look at doing so 
after pc3 stuff

> - an ID for the run

this exists now

> - analyzed scores of the run output

not sure what that is - is this application specific output?

> - what version of oops was used

the extrainfo stuff I implemented previously for the oops app may be used 
here. I've heard no feedback about it actually being used, though.

> - what version of the oops.swift script was used

For all the version stuff, you need to figure out what version semantics 
you want (eg md5sum of swift script, which gives fine grained version 
distinction but no order; user specified version numbering which is pretty 
much guaranteed to be wrong but you might think you want that, and also 
gives ordering; ... there are lots of schemes ...)

> Given this in a database, you could also compare structure scores for one
> version of code or one algorithm vs another

This is more application specific data?

Are you looking here to have data output from a run end up in a database?

--