This PR adds for the first time most of the common code about concurrent execution (eg. AbstractConcurrentExecutionEngine) in the common GEMOC execution framework. Previously, this code was in the gemoc-studio-execution-moccml repository , since Moccml was the only possible concurrent engine. Nowadays, a Henshin engine exists and should not have to import and extends classes from the Moccml execution engine code base.
In addition, following the work presented in this paper, this PR changes how concurrency was originally managed in the GEMOC Studio. Now a concurrent engine must build a symbolic representation of logical steps, through inclusion/exclusion constraints over small steps. Strategies, which come with its own UI, are then available to choose what logical steps will be available when debugging. In the code, this symbolic representation is accomplished using the Choco solver.
Description
This PR adds for the first time most of the common code about concurrent execution (eg.
AbstractConcurrentExecutionEngine) in the common GEMOC execution framework. Previously, this code was in the gemoc-studio-execution-moccml repository , since Moccml was the only possible concurrent engine. Nowadays, a Henshin engine exists and should not have to import and extends classes from the Moccml execution engine code base.In addition, following the work presented in this paper, this PR changes how concurrency was originally managed in the GEMOC Studio. Now a concurrent engine must build a symbolic representation of logical steps, through inclusion/exclusion constraints over small steps. Strategies, which come with its own UI, are then available to choose what logical steps will be available when debugging. In the code, this symbolic representation is accomplished using the Choco solver.
Companion Pull Requests