Skip to Content

Changes for page Kieler Compiler

Last modified by Richard Kreissig on 2023/09/14 10:52
From version 18.1
edited by cmot
on 2014/03/17 14:48
Change comment: There is no comment for this version
To version 28.1
edited by aas2
on 2017/04/04 13:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.cmot
1 +XWiki.aas2
Content
... ... @@ -1,4 +1,4 @@
1 -{{panel title="Project Overview" borderStyle="dashed"}}
1 +{{panel borderStyle="dashed" title="Project Overview"}}
2 2  Responsible:
3 3  
4 4  * [[Christian Motika>>url:http://www.informatik.uni-kiel.de/rtsys/kontakt/cmot/||shape="rect"]], [[Steven Smyth>>url:http://www.informatik.uni-kiel.de/rtsys/kontakt/ssm/||shape="rect"]]
... ... @@ -6,11 +6,13 @@
6 6  Related Theses:
7 7  
8 8  * none yet
9 +
10 +**To see the KielerCompiler in action, we provide an Online SCCharts Compiler [[here>>doc:Online Compiler]].**
9 9  {{/panel}}
10 10  
11 11  = Kieler Compiler (KiCo) =
12 12  
13 -In order to integrate and be able to evaluate our compiler chain from SCCharts to C or VHDL code we use the KiCo project as a generic framework that allows to register setp-by-step transformations on EObjects. These can then be handled by the generic KIEM KiCo DataComponent.
15 +In order to integrate and be able to evaluate our compiler chain from SCCharts to C or VHDL code we use the KiCo project as a generic framework that allows to register setp-by-step transformations on EObjects. These can then be handled by the generic KIEM KiCo DataComponent. **To see the KielerCompiler in action, we provide an Online SCCharts Compiler [[here>>url:http://www.sccharts.com/||shape="rect"]].**
14 14  
15 15  
16 16  
... ... @@ -20,11 +20,18 @@
20 20  
21 21  The KIELER Compiler (KiCo) project allows to register step-by-step model transformations on EObjects that could be written in Xtend or Java. These transformations are registered using an extension point provided (see below). After registering transformations these can be used by simply call the KielerCompiler compilation method as also explained further below.
22 22  
25 +(% class="wrapped" %)
23 23  |=(((
24 -[[image:attach:KiCo.jpg]]
27 +(% class="content-wrapper" %)
28 +(((
29 +[[image:attach:IMAG4642.jpg]]
30 +)))
25 25  )))|=(((
26 -[[image:attach:KiCo3.jpg]]
32 +(% class="content-wrapper" %)
33 +(((
34 +[[image:attach:KiCo.jpg]]
27 27  )))
36 +)))
28 28  
29 29  == Extension Point ==
30 30  
... ... @@ -35,13 +35,13 @@
35 35  
36 36  {{{de.cau.cs.kieler.kico}}}
37 37  
38 -
47 +\\
39 39  )))
40 40  1. Add the extension
41 41  
42 42  
43 43  {{{de.cau.cs.kieler.kico.transformation}}}(((
44 -
53 +\\
45 45  )))
46 46  1. (((
47 47  Add one of the following extension element
... ... @@ -49,6 +49,7 @@
49 49  [[image:attach:KiCo2.jpg]]
50 50  )))
51 51  
61 +(% class="wrapped" %)
52 52  |=(((
53 53  Extension Element
54 54  )))|=(((
... ... @@ -73,7 +73,7 @@
73 73  * method: The name of the transformation method. Its signature must ensure that it returns an EObject an only take an EObject argument. Otherwise it cannot be found by KiCo.
74 74  * id: The unique String ID for this transformation. This is the ID the transformation will be referenced throughout KiCo.
75 75  * name: An optional String name for this transformation. If nothing is entered here the ID will be used as a name.
76 -* dependencies: An optional String as comma separated list of other transformation IDs that must run BEFORE this transformation. If nothing is entered here then this means there are no dependencies.
86 +* dependencies: An optional String as comma separated list of other transformation IDs that must run AFTER this transformation down the compile-chain. This means if the current transformation is selected to run, all transformations that have dependencies on this will be run BEFORE. If nothing is entered here then this means there are no dependencies.
77 77  )))
78 78  |(((
79 79  transformationGroup
... ... @@ -96,9 +96,7 @@
96 96   dependencies="TRIGGEREFFECT, SURFACEDEPTH"
97 97   name="Transform All Normalize">
98 98   </transformationGroup>
99 - </extension>
100 - <extension
101 - point="de.cau.cs.kieler.kico.transformation">
109 +
102 102   <transformationMethod
103 103   class="de.cau.cs.kieler.sccharts.extensions.SCChartsCoreTransformation"
104 104   id="TRIGGEREFFECT"
... ... @@ -105,10 +105,7 @@
105 105   method="transformTriggerEffect"
106 106   name="Transform Trigger and Effect">
107 107   </transformationMethod>
108 - </extension>
109 -
110 - <extension
111 - point="de.cau.cs.kieler.kico.transformation">
116 +
112 112   <transformationMethod
113 113   class="de.cau.cs.kieler.sccharts.extensions.SCChartsCoreTransformation"
114 114   id="SURFACEDEPTH"
... ... @@ -115,10 +115,7 @@
115 115   method="transformSurfaceDepth"
116 116   name="Transform Surface Depth">
117 117   </transformationMethod>
118 - </extension>
119 -
120 - <extension
121 - point="de.cau.cs.kieler.kico.transformation">
123 +
122 122   <transformationGroup
123 123   id="ALL"
124 124   dependencies="CORE NORMALIZE"
... ... @@ -127,12 +127,13 @@
127 127   </extension>
128 128  {{/code}}
129 129  
130 -
132 +\\
131 131  
132 132  == Compilation ==
133 133  
134 134  Once a bunch of model transformations are registered, these can simply be called using the KiCo central "KielerCompiler" class with its method compile(). This will be given a List<String> of transformation IDs or a comma separated String of transformation IDs as the first parameter. The second parameter is the EObject that is being transformed. It should meet the signature of the first model transformation called. Note that the actual model transformations that are done may vary because KiCo will automatically inspect the dependencies of each transformation requested (deep-recursively). If you do not like this to happen as an advanced user you can use a third parameter that will skip this autocompletion. Note that if you switch this off also NO transformation groups can be processed. Here is an overview and examples how to use the compile() method:
135 135  
138 +(% class="wrapped" %)
136 136  |=(((
137 137  Method
138 138  )))|=(((
... ... @@ -190,10 +190,153 @@
190 190  
191 191  {{/code}}
192 192  
196 +=== Requirement Completion ===
197 +
198 +\\
199 +
200 +(% class="wrapped" %)
201 +|=(((
202 +(% class="content-wrapper" %)
203 +(((
204 +(% style="text-align: center;" %)
205 +Original
206 +
207 +(% class="wrapped" %)
208 +|=(((
209 +(% class="content-wrapper" %)
210 +(((
211 + [[image:attach:dependencies2.jpg]]
212 +
213 +(% style="text-align: center;" %)
214 +Original Dependency
215 +Graph
216 +)))
217 +)))|=(((
218 +(% class="content-wrapper" %)
219 +(((
220 +(% style="text-align: center;" %)
221 +[[image:attach:dependencies3.jpg]]
222 +
223 +(% style="text-align: center;" %)
224 +Two alternative
225 +transformation
226 +implementations
227 +for Abort
228 +)))
229 +)))
230 +
231 +\\
232 +)))
233 +)))|=(((
234 +(% class="content-wrapper" %)
235 +(((
236 +(% style="text-align: center;" %)
237 +Example 1
238 +
239 +(% class="wrapped" %)
240 +|=(((
241 +(% class="content-wrapper" %)
242 +(((
243 + [[image:attach:dependencies4.jpg]]
244 +
245 +(% style="text-align: center;" %)
246 +Selected for
247 +transformation
248 +)))
249 +)))|=(((
250 +(% class="content-wrapper" %)
251 +(((
252 + [[image:attach:dependencies4b.jpg]]
253 +
254 +(% style="text-align: center;" %)
255 +Auto selected
256 +requirements
257 +)))
258 +)))
259 +
260 +\\
261 +)))
262 +)))
263 +
264 +\\
265 +
266 +\\
267 +
268 +(% class="wrapped" %)
269 +|=(((
270 +(% class="content-wrapper" %)
271 +(((
272 +(% style="text-align: center;" %)
273 +Example 2
274 +
275 +(% class="wrapped" %)
276 +|=(((
277 +(% class="content-wrapper" %)
278 +(((
279 +[[image:attach:dependencies5.jpg]]
280 +
281 +(% style="text-align: center;" %)
282 +Selected for
283 +transformation
284 +)))
285 +)))|=(% style="text-align: center;" %)(% style="text-align: center;" %)
286 +(((
287 +(% class="content-wrapper" %)
288 +(((
289 +[[image:attach:dependencies5b.jpg]]
290 +
291 +Auto selected
292 +requirements
293 +using DEFAULT
294 +of alternative
295 +group
296 +
297 +\\
298 +)))
299 +)))
300 +
301 +\\
302 +)))
303 +)))|=(((
304 +(% class="content-wrapper" %)
305 +(((
306 +(% style="text-align: center;" %)
307 +Example 3
308 +
309 +(% class="wrapped" %)
310 +|=(((
311 +(% class="content-wrapper" %)
312 +(((
313 +[[image:attach:dependencies6.jpg]]
314 +
315 +(% style="text-align: center;" %)
316 +Selected for
317 +transformation
318 +)))
319 +)))|=(((
320 +(% class="content-wrapper" %)
321 +(((
322 +[[image:attach:dependencies6b.jpg]]
323 +
324 +(% style="text-align: center;" %)
325 +Auto selected
326 +requirements
327 +using selected
328 +alternative
329 +)))
330 +)))
331 +
332 +\\
333 +)))
334 +)))
335 +
336 +\\
337 +
193 193  == Help / Problems / FAQs ==
194 194  
195 195  Maybe you get into problems when using KiCo. The following list should give you hints to solve these. If you have a problem not considered here please write us an e-mail (see above for contact information of the persons in charge of KiCo).
196 196  
342 +(% class="wrapped" %)
197 197  |=(((
198 198  Symptom
199 199  )))|=(((
... ... @@ -222,7 +222,7 @@
222 222  Maybe the plugin declaring "ABORT2" was not loaded
223 223  or the ID is misspelled.
224 224  
225 -
371 +\\
226 226  )))|(((
227 227  Check why "ABORT2" may not be found
228 228  by KiCo, more specifically, check if the
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -9470109
1 +50823224
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/9470109/Kieler Compiler
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/50823224/Kieler Compiler