Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.stu230980
	1	+XWiki.als

Content

...	...	@@ -1,5 +1,6 @@
1		-== Deprecated since 0.14 ==
	1	+{{panel bgColor="orange" title="Deprecated since 0.14"}}
2	2	This article is deprecated. The described features are no longer available in current releases.
	3	+{{/panel}}
3	3
4	4	= Simulation of Models in KIELER =
5	5
...	...	@@ -27,7 +27,7 @@
27	27	* Generating the simulation wrapper code for the model using template processing
28	28	* Compiling the resulting code using, e.g., gcc.
29	29
30		-For more insight of the simulation generation, please take a look at the [[doc:KIELER.SCCharts (DeprecatedHistorical Documentation & Features).Project Creation, Initialization and Launch (Prom).Project Management.WebHome]].
	31	+For more insight of the simulation generation, please take a look at the [[doc:KIELER.SCCharts (DeprecatedHistorical Documentation & Features).Project Management (Prom).WebHome]].
31	31
32	32	----
33	33
...	...	@@ -35,7 +35,7 @@
35	35
36	36	Besides the explicit configuration of a simulation using a kisim file, it is possible to start simulations directly on models, executables or trace files. This will start a pre-defined configuration depending on the selected files. The following table shows which files can be used to start a simulation and what simulation configuration is created for it.
37	37
38		-(% class="relative-table wrapped" style="width:99.9453%" %)
	39	+(% class="relative-table wrapped" style="width: 99.9453%;" %)
39	39	|=(((
40	40	Selection
41	41	)))|=(% colspan="1" %)(% colspan="1" %)
...	...	@@ -326,6 +326,7 @@
326	326	If this is false and for example the trace contains a variable that does not exist in the model, this issue is ignored.
327	327	)))
328	328
	330	+\\
329	329
330	330	=== Simulation Input Files ===
331	331
...	...	@@ -337,7 +337,7 @@
337	337
338	338	Simulation input files can also be used to feed the simulation with data to be visualized via the simulation visualization.
339	339
340		-(% class="relative-table wrapped" style="width:81.5545%" %)
	342	+(% class="relative-table wrapped" style="width: 81.5545%;" %)
341	341	|=(((
342	342	Attribute
343	343	)))|=(((
...	...	@@ -367,12 +367,13 @@
367	367	Name of the model in the simulation that the data in the simin file is for.
368	368	)))
369	369
	372	+\\
370	370
371	371	=== Simulation Outputs Files ===
372	372
373	373	This data handler writes the output of the model in the simulation to the specified file.
374	374
375		-(% class="relative-table wrapped" style="width:81.7734%" %)
	378	+(% class="relative-table wrapped" style="width: 81.7734%;" %)
376	376	|=(((
377	377	Attribute
378	378	)))|=(((
...	...	@@ -434,7 +434,9 @@
434	434	This way different setters can be defined for different simulation runs or manual testing.
435	435	)))
436	436
	440	+\\
437	437
	442	+\\
438	438
439	439	----
440	440
...	...	@@ -465,6 +465,7 @@
465	465	}
466	466	{{/code}}
467	467
	473	+\\
468	468
469	469	Configuration for two executables with redirection between both:
470	470
...	...	@@ -559,6 +559,7 @@
559	559	}
560	560	{{/code}}
561	561
	568	+\\
562	562
563	563	== Implementation Details ==
564	564
...	...	@@ -565,7 +565,7 @@
565	565	The following are details about the implementation of the simulation and the JSON format that is used to communicate the variables in the models.
566	566
567	567	As said above the simulation is seen as black box which takes inputs on stdin, computes a reaction, and sends outputs stdout. Thus an executable simulation is a normal program that communicates in a specific JSON format and can also be used from command line.
568		-
	575	+\\
569	569
570	570	=== The JSON Format ===
571	571