Revision as of 10:35, 26 November 2015

New and Noteworthy - VIATRA 0.8.0

Previously VIATRA-DSE 0.7 had a slow and sometimes buggy state coder (which is needed for identifying recurring state in the search space) but at least worked for any problem domain. In 0.8 a new state coder is introduced which is much more simple and therefore faster but. It simply encodes 1) all the attribute values and 2) all the attribute values of the referenced EObjects of all the EObjects. The disadvantage of the new state coder is that it may fail in certain scenarios (e.g., if a rule can add "A"s, another can delete "A"s and a third one can make references between them). From 0.8 this is the default state coder. When used, the metamodel (EPackage) of the domain must be defined for the DSE framework. VIATRA/DSE/UserGuide/API#State_coding

@@ Line 7: / Line 7: @@
 * [[VIATRA/Transformation_API/MWE2_Integration]]
-== The DSE component ==
+== VIATRA-DSE component ==
-* A new general state coder: [[VIATRA/DSE/UserGuide/API#State_coding]]
+* Previously VIATRA-DSE 0.7 had a slow and sometimes buggy state coder (which is needed for identifying recurring state in the search space) but at least worked for any problem domain. In 0.8 a new state coder is introduced which is much more simple and therefore faster but. It simply encodes 1) all the attribute values and 2) all the attribute values of the referenced EObjects of all the EObjects. The disadvantage of the new state coder is that it may fail in certain scenarios (e.g., if a rule can add "A"s, another can delete "A"s and a third one can make references between them). From 0.8 this is the default state coder. When used, the metamodel (EPackage) of the domain must be defined for the DSE framework. [[VIATRA/DSE/UserGuide/API#State_coding]]
 == VIATRA-CEP ==