Skip to Content

Changes for page Kieler Compiler

Last modified by Richard Kreissig on 2023/09/14 10:52
From version 16.1
edited by cmot
on 2014/03/17 14:47
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,18 +20,19 @@
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 -
30 -
31 -
32 -
33 -
34 -
35 35  == Extension Point ==
36 36  
37 37  In order to add a transformation to KiCo you must follow these steps:
... ... @@ -41,13 +41,13 @@
41 41  
42 42  {{{de.cau.cs.kieler.kico}}}
43 43  
44 -
47 +\\
45 45  )))
46 46  1. Add the extension
47 47  
48 48  
49 49  {{{de.cau.cs.kieler.kico.transformation}}}(((
50 -
53 +\\
51 51  )))
52 52  1. (((
53 53  Add one of the following extension element
... ... @@ -55,6 +55,7 @@
55 55  [[image:attach:KiCo2.jpg]]
56 56  )))
57 57  
61 +(% class="wrapped" %)
58 58  |=(((
59 59  Extension Element
60 60  )))|=(((
... ... @@ -79,7 +79,7 @@
79 79  * 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.
80 80  * id: The unique String ID for this transformation. This is the ID the transformation will be referenced throughout KiCo.
81 81  * name: An optional String name for this transformation. If nothing is entered here the ID will be used as a name.
82 -* 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.
83 83  )))
84 84  |(((
85 85  transformationGroup
... ... @@ -102,9 +102,7 @@
102 102   dependencies="TRIGGEREFFECT, SURFACEDEPTH"
103 103   name="Transform All Normalize">
104 104   </transformationGroup>
105 - </extension>
106 - <extension
107 - point="de.cau.cs.kieler.kico.transformation">
109 +
108 108   <transformationMethod
109 109   class="de.cau.cs.kieler.sccharts.extensions.SCChartsCoreTransformation"
110 110   id="TRIGGEREFFECT"
... ... @@ -111,10 +111,7 @@
111 111   method="transformTriggerEffect"
112 112   name="Transform Trigger and Effect">
113 113   </transformationMethod>
114 - </extension>
115 -
116 - <extension
117 - point="de.cau.cs.kieler.kico.transformation">
116 +
118 118   <transformationMethod
119 119   class="de.cau.cs.kieler.sccharts.extensions.SCChartsCoreTransformation"
120 120   id="SURFACEDEPTH"
... ... @@ -121,10 +121,7 @@
121 121   method="transformSurfaceDepth"
122 122   name="Transform Surface Depth">
123 123   </transformationMethod>
124 - </extension>
125 -
126 - <extension
127 - point="de.cau.cs.kieler.kico.transformation">
123 +
128 128   <transformationGroup
129 129   id="ALL"
130 130   dependencies="CORE NORMALIZE"
... ... @@ -133,12 +133,13 @@
133 133   </extension>
134 134  {{/code}}
135 135  
136 -
132 +\\
137 137  
138 138  == Compilation ==
139 139  
140 140  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:
141 141  
138 +(% class="wrapped" %)
142 142  |=(((
143 143  Method
144 144  )))|=(((
... ... @@ -196,10 +196,153 @@
196 196  
197 197  {{/code}}
198 198  
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 +
199 199  == Help / Problems / FAQs ==
200 200  
201 201  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).
202 202  
342 +(% class="wrapped" %)
203 203  |=(((
204 204  Symptom
205 205  )))|=(((
... ... @@ -228,7 +228,7 @@
228 228  Maybe the plugin declaring "ABORT2" was not loaded
229 229  or the ID is misspelled.
230 230  
231 -
371 +\\
232 232  )))|(((
233 233  Check why "ABORT2" may not be found
234 234  by KiCo, more specifically, check if the
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -9470087
1 +50823224
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/9470087/Kieler Compiler
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/50823224/Kieler Compiler