Add SpineInterface and SpineOpt commits to results DB

[DillonJ]

Often it's difficult to know which version of SpineOpt and SpineInterface was used for a set of old results or for an old model. For example, sometimes we will notice a performance degradation or an old DB doesn't work any more. In these cases it's very valuable to have this information.

It feels like the best solution would be for SpineOpt to write the commit of SpineInterface and SpineOpt that have been used to generate a set of results. Perhaps it could write new parameters (e,g, SpineOpt_Version and SpineInterface_Version the model object under the result altnerative in the output DB. While it's at it, maybe it could write total execution time and other useful information?

[manuelma]

We write it to the log - but we could write them to the DB too.

[DillonJ]

That would be good. Often the log is not saved ad it’s usually actually multiple files and requires manual steps and may or may not have been written at all

[manuelma]

the two are good, because often the model doesn't solve or results are not written but the log is available. It is not very hard to setup and very easy to find the first file.

[manuelma]

We are now writing versions and elapsed time to a model Map parameter called 'solution_stats'. Please reopen if no good or if more stuff is needed.

[DillonJ]

@manuelma this is really nice. It would be even better if we could include the following (in the case of a Benders Model):

• Number of benders iterations
• Benders Gap
• Objective function value

[manuelma]

I just added all that @DillonJ - it's very handy indeed.

[DillonJ]

Looks like SpineOpt only writes the version and not the commit hash. I think it should write both since we can't be sure the version has been bumped. The commit hash is the only thing we can believe in.