Commit message (Collapse) | Author | Age | ||
---|---|---|---|---|
... | ||||
* | Merge branch 'master' of https://github.com/viatra/VIATRA-Generator | 2020-04-28 | ||
|\ | ||||
| * | Rename pledge case study file | 2020-04-28 | ||
| | | ||||
| * | Able to run Pledge Case Study | 2020-04-28 | ||
| | | ||||
| * | rename Pledge Case Studies and add familyTree case study | 2020-04-27 | ||
| | | ||||
| * | Merge branch 'Attribute-Solver' | 2020-04-26 | ||
| |\ | ||||
| | * | Added FakeIntegerElement | 2020-04-26 | ||
| | | | ||||
| * | | Add PLEDGE case study files | 2020-04-26 | ||
| | | | ||||
| * | | Merge branch 'Attribute-Solver' | 2020-04-25 | ||
| |\| | ||||
| | * | Added new test | 2020-04-22 | ||
| | | | ||||
| | * | Added measurements | 2020-04-15 | ||
| | | | ||||
| | * | Added test methods with running time measurement | 2020-04-15 | ||
| | | | ||||
| | * | Added logic to get a solution | 2020-04-15 | ||
| | | | ||||
| | * | Updated logic that creates a numeric problem using matches | 2020-04-08 | ||
| | | | ||||
| | * | Added logic to create a numeric problem instance with pattern matches | 2020-04-07 | ||
| | | | ||||
| | * | Added logic to form numeric problem templates | 2020-03-31 | ||
| | | | ||||
| | * | Added call to form numeric problem templates | 2020-03-31 | ||
| | | | ||||
* | | | initial commit | 2020-04-28 | ||
|/ / | ||||
* | | check expressions are mapped to WF constraints | 2020-04-17 | ||
| | | ||||
* | | variable mapping trace is created after mapping | 2020-04-17 | ||
| | | ||||
* | | Variable trace added to Viatra2Logic mapping | 2020-04-17 | ||
| | | ||||
* | | (lipstick) | 2020-04-15 | ||
| | | ||||
* | | memory management support for v8 javascript engine added (visualization) | 2020-04-15 | ||
| | | ||||
* | | javascript engine memory increased for visualizing | 2020-04-15 | ||
| | | ||||
* | | Alloy type mapping fix | 2020-04-15 | ||
| | | ||||
* | | check constraint is a special eval | 2020-04-15 | ||
| | | ||||
* | | Alloy typeQuery fix | 2020-04-14 | ||
| | | ||||
* | | restructured pattern generation | 2020-04-14 | ||
| | | ||||
* | | Primitive object indexing update | 2020-04-08 | ||
|/ | ||||
* | fixing index out ot bound exceptions for state coders | 2019-10-19 | ||
| | ||||
* | handler refactor | 2019-10-01 | ||
| | ||||
* | Alloy upper multiplicity under-approximation with keyword bug fix | 2019-09-02 | ||
| | | | candidate 1 | |||
* | Type Interpretation for Alloy with Inheritance+Horizontal mapping | 2019-08-30 | ||
| | ||||
* | scopes added to alloy | 2019-08-30 | ||
| | ||||
* | Whitespacing in manifest updated | 2019-08-30 | ||
| | ||||
* | Bug fixed in transitive closure expression builder | 2019-08-30 | ||
| | ||||
* | Alloy RunCommand int scope fix candidate | 2019-08-27 | ||
| | ||||
* | https://github.com/kris7t graph width calculation -> | 2019-07-15 | ||
| | | | | from https://github.com/kris7t/VIATRA-Generator/blob/c0c5a1644cc221352b8b9b370eea6a87677ba948/Solvers/VIATRA-Solver/hu.bme.mit.inf.dslreasoner.viatrasolver.partialinterpretationlanguage/src/hu/bme/mit/inf/dslreasoner/viatrasolver/partialinterpretationlanguage/neighbourhood/PartialInterpretation2NeighbourhoodRepresentation.xtend#L99-L138 | |||
* | adding slf4j dependency to avoid error message in logs | 2019-07-15 | ||
| | ||||
* | parsing count, min, max, check and eval v1 | 2019-07-15 | ||
| | ||||
* | aggregated partial substitution + builder | 2019-07-09 | ||
| | ||||
* | Updated link to Alloy | 2019-06-25 | ||
| | ||||
* | Default state coder range set to Width, as it should be | 2019-06-01 | ||
| | ||||
* | Inverse references works if opposite reference is pruned away. | 2019-06-01 | ||
| | ||||
* | Fix for symmetric activation codes on symmetric models | 2019-05-13 | ||
| | ||||
* | fixed manifest | 2019-05-05 | ||
| | ||||
* | Removed unwanted OCL dependency | 2019-05-05 | ||
| | ||||
* | typo in launch config name | 2019-05-04 | ||
| | ||||
* | removed unused test case | 2019-05-04 | ||
| | ||||
* | Added aggregate expressions to logic language on the model level | 2019-05-04 | ||
| | ||||
* | Fixed misformalization of (may/must)(X!=Y) for abstract objects | 2019-04-16 | ||
| |