Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 0.3.9 #63

Merged
merged 54 commits into from Mar 6, 2015
Merged

Release 0.3.9 #63

merged 54 commits into from Mar 6, 2015

Conversation

mantkiew
Copy link
Member

@mantkiew mantkiew commented Mar 5, 2015

  1. added support for inheritance from nested abstract clafers, see simple test case and more complex test case. Supported only in the Alloy backend.

  2. fixed problem with lifting nested constraints, see test case.

  3. fixed group cardinality inheritance, see test case.

  4. added assertion generation for Alloy, see test case and the corresponding Alloy output. Supported only in the Alloy backend.

  5. added a unary operator product, see test case, pull request. Supported only in the Choco backend.

  6. added a binary operator % ("reminder" or "modulo division"), see test case.

  7. Improved HTML and Graph generation by escaping special characters.

  8. changed Alloy 4.2 to be the default mode.

  9. changed the Python output to be in line with the Choco output, which is very concise and simple.

  10. removed GLPK Scope analyzer and improved compiler performance, see pull request. Results:

performance

Models:

  • Scade by Aymen Ketata

All clafers: 435 | Abstract: 114 | Concrete: 321 | Reference: 204
Constraints: 242
Goals: 0

  • AADL by Alex Murashkin

All clafers: 209 | Abstract: 47 | Concrete: 162 | Reference: 43
Constraints: 341
Goals: 1

  • PowerWindow by Alex Murashkin

All clafers: 137 | Abstract: 20 | Concrete: 117 | Reference: 46
Constraints: 246
Goals: 3

mantkiew and others added 30 commits February 4, 2015 10:53
in eCos and Linux use hard constraints for defaults
in resolution, cannot use X because it's a reserved keyword in
behavioral  Clafer
cannot use identifier F because it is a keyword in behavioral Clafer
to remove spourious differences
"product Failure.probability"  computes p$1* p$2 * ... * p$n of all
failures
regression fails because the check commands must have the same scopes as
the run command.
GenEnv contains clafer args and uidIClaferMap
use transformers' Control.Monad.Trans.Maybe instead
getSuperId allows navigation paths
Alloy generates parent subrelation constraint
Analysis used more general getSuper and getReference instead of explicit
pattern match
sugarer prints any PExp for reference, not just IClaferId
added nestedInheritanceWithReference test case and Alloy regression
…utput

The test case currently fails. The group cardinality constraint should
be enforced only for concrete clafers but the actual group cardinality
is correctly inherited and refined.
UIDIClaferMap type synonym
…rs, include all inherited children

for the test case GroupCardInheritance.cfr the assertions now hold.
Added html, js, py, xml regressions
removed findHierarchy and renamed findHierarchyWithMap to findHierarchy
fixed a subtle bug with group inheritance
updated regressions for EAST-ADL-PowerWindow and added new regressions
for liftingNestedConstraints
…rType

replaced Info with UIDIClaferMap to be explicit
obtain the root from the map
updated test cases as the output is correct now - py and js regressions
remain the same
Remove Analysis/SClafer & GLPK scope analyzer
@mantkiew mantkiew self-assigned this Mar 5, 2015
@mantkiew mantkiew added this to the 0.3.9 milestone Mar 5, 2015
mantkiew added a commit that referenced this pull request Mar 6, 2015
@mantkiew mantkiew merged commit 117c2e2 into master Mar 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants