|
Re: Viatra tutorial [message #1759164 is a reply to message #1759150] |
Fri, 07 April 2017 08:06 |
Zoltan Ujhelyi Messages: 392 Registered: July 2015 |
Senior Member |
|
|
Hi,
thanks for your interest in the tutorial; I try to answer your questions here. If something is unclear, feel free to ask for clarification.
1) Event-driven transformations have to maintain a trace back to the original model in some way to allow the continuation of the transformation (basically, rule preconditions should be able to distinguish between source model elements that have or have not been transformed into the target models). Traceability models is such an approach that is also useful for a post-mortem analysis or documenting the relation between the different model artifacts. However, if e.g. new model elements are created with shared model identifiers, they can be reused to provide such trace information. Such a transformation (based on queries) is described in [1] (sorry for the raw asciidoc format here, the documentation is being moved to eclipse.org, and we have not finished deploying the output yet).
2) Yes, as the transformation state (e.g. what rules were already executed) is encoded in the transformation itself. This approach was selected to ensure the tutorial does not take too long to complete. If you want to have an _incremental_ transformation (e.g. that handles restarts), you should have queries that also check the traceability records, as in [2].
[1] http://git.eclipse.org/c/viatra/org.eclipse.viatra.git/tree/documentation/org.eclipse.viatra.documentation.help/src/main/asciidoc/cps/Query-result-traceability-M2M-transformation.adoc
[2] http://git.eclipse.org/c/viatra/org.eclipse.viatra.git/tree/documentation/org.eclipse.viatra.documentation.help/src/main/asciidoc/cps/Explicit-traceability-M2M-transformation.adoc
Best regards,
Zoltán
|
|
|
Re: Viatra tutorial [message #1769154 is a reply to message #1759164] |
Thu, 27 July 2017 07:12 |
zhang ph Messages: 43 Registered: March 2017 |
Member |
|
|
Hi,
Today I perform the M2M transformation with incremental method as described in the tutorial, I load an existing CPS model(about 8.5MB, generated by CPS benchmark in LOW_SYNCH scenario, scale is 32) into my eclipse, my eclipse is blocked. And about 20 minutes later, it become active. Then I load larger model into it, it need more time to become active, even is alway blocked. From my opinion, it is because EMF takes long time to parse the model, am I right? Do you encounter the same issue or Could you give me any suggestions to handle it?
Hope for your reply, Thanks!
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.07314 seconds