search

ModelInference / synoptic

Inferring models of systems from observations of their behavior
Other
83 stars 25 forks source link

Get rid of the InvariMint branch #290

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
InvariMint branch is no longer necessary. Instead, we should be using 
issue-based branches. Merge whatever code is in the InvariMint branch into 
default.

Original issue reported on code.google.com by bestchai on 20 Feb 2013 at 8:19

GoogleCodeExporter commented 9 years ago 
Functionally the only changes in the InvariMint branch was an option to mine 
some subset of Synoptic invariants when performing InvariMint-Synoptic and to 
optionally add some subset of Synoptic invariants when performing 
InvariMint-KTails. This is more challenging to cleanly implement in the default 
branch now given all the code restructuring committed in default since May. 
I've closed the InvariMint branch for now. Is re-implementing those options in 
default still high-priority?

Original comment by jenny.abrahamson on 20 Feb 2013 at 10:17

GoogleCodeExporter commented 9 years ago 
Yes, I think so. We have to add at least some customization to InvariMint to be 
able to claim in our paper (due in about a week) that the tool allows 
developers to select particular invariant types.

(You can also generate a new issue for it, and finish out the other ShiVector 
tasks before coming back to this.)

Original comment by bestchai on 20 Feb 2013 at 10:26

GoogleCodeExporter commented 9 years ago 
Closed in revision 0903fceab619. Relevant remaining work moved to issue 297.

Original comment by jenny.abrahamson on 5 Mar 2013 at 9:49