<
From version < 9.10 >
edited by Alexander Schulz-Rosengarten
on 2023/09/11 16:16
To version < 10.1
edited by Richard Kreissig
on 2023/09/14 10:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.als
1 +XWiki.stu230980
Content
... ... @@ -1,8 +1,7 @@
1 -{{panel bgColor="orange" title="Deprecated since 0.12"}}
1 +== Deprecated since 0.12 ==
2 2  This article is deprecated. The described features are no longer available in current releases.
3 -{{/panel}}
4 4  
5 -{{panel borderStyle="dashed" title="Project Overview"}}
4 +== Project Overview ==
6 6  Responsible:
7 7  
8 8  * [[Christian Motika>>url:http://www.informatik.uni-kiel.de/rtsys/kontakt/cmot/||shape="rect"]]
... ... @@ -10,7 +10,6 @@
10 10  Related Theses:
11 11  
12 12  * Christian Motika, //Semantics and Execution of Domain Specific Models – KlePto and an Execution Framework//, December 2009 ([[pdf>>url:http://rtsys.informatik.uni-kiel.de/confluence/%7Ebiblio/downloads/theses/cmot-dt.pdf||shape="rect"]])
13 -{{/panel}}
14 14  
15 15  = KlePto - KIELER leveraging Ptolemy semantics =
16 16  
... ... @@ -84,7 +84,6 @@
84 84  
85 85  [[image:attach:klepto-problems.jpg]]
86 86  
87 -\\
88 88  
89 89  === unsaved changes ===
90 90  
... ... @@ -92,7 +92,6 @@
92 92  
93 93  * If you have any unsaved changes, you must save your model in order to simulate it because the transformation only considers the model file. You cannot start a simulation for an editor with any unsaved changes (even only graphical/non-semantical ones).
94 94  
95 -\\
96 96  
97 97  === model changes during simulation ===
98 98  
... ... @@ -100,7 +100,6 @@
100 100  
101 101  * If you change the model during the simulation, you will be warned about this. The transformation took place on the last saved version of your model and the simulation cannot consider on-the-fly changes. If you ignore this warning, keep in mind that you do not simulate the (changed) model in your editor.
102 102  
103 -\\
104 104  
105 105  === Ptolemy Model could not be generated ===
106 106  
... ... @@ -109,7 +109,6 @@
109 109  * If the transformation could not take place, there might be some unsolved problems left. Check the "Problems" View of Eclipse (s.a.).
110 110  * This error message for example indicates that you have used an output signal in a trigger or an input signal in an output action. But this is fully brought to your attention when you inspect the "Problems" View as already described above.
111 111  
112 -\\
113 113  
114 114  === Ptolemy Model could not make a step ===
115 115