Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -1,6 +1,5 @@
1		-{{panel bgColor="orange" title="Deprecated since 0.14"}}
	1	+== Deprecated since 0.14 ==
2	2	This article is deprecated. The described features are no longer available in current releases.
3		-{{/panel}}
4	4
5	5	= Simulation of Models in KIELER =
6	6
...	...	@@ -28,7 +28,7 @@
28	28	* Generating the simulation wrapper code for the model using template processing
29	29	* Compiling the resulting code using, e.g., gcc.
30	30
31		-For more insight of the simulation generation, please take a look at the [[doc:KIELER.SCCharts (DeprecatedHistorical Documentation & Features).Project Management (Prom).WebHome]].
	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]].
32	32
33	33	----
34	34
...	...	@@ -36,7 +36,7 @@
36	36
37	37	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.
38	38
39		-(% class="relative-table wrapped" style="width: 99.9453%;" %)
	38	+(% class="relative-table wrapped" style="width:99.9453%" %)
40	40	|=(((
41	41	Selection
42	42	)))|=(% colspan="1" %)(% colspan="1" %)
...	...	@@ -327,7 +327,6 @@
327	327	If this is false and for example the trace contains a variable that does not exist in the model, this issue is ignored.
328	328	)))
329	329
330		-\\
331	331
332	332	=== Simulation Input Files ===
333	333
...	...	@@ -339,7 +339,7 @@
339	339
340	340	Simulation input files can also be used to feed the simulation with data to be visualized via the simulation visualization.
341	341
342		-(% class="relative-table wrapped" style="width: 81.5545%;" %)
	340	+(% class="relative-table wrapped" style="width:81.5545%" %)
343	343	|=(((
344	344	Attribute
345	345	)))|=(((
...	...	@@ -369,13 +369,12 @@
369	369	Name of the model in the simulation that the data in the simin file is for.
370	370	)))
371	371
372		-\\
373	373
374	374	=== Simulation Outputs Files ===
375	375
376	376	This data handler writes the output of the model in the simulation to the specified file.
377	377
378		-(% class="relative-table wrapped" style="width: 81.7734%;" %)
	375	+(% class="relative-table wrapped" style="width:81.7734%" %)
379	379	|=(((
380	380	Attribute
381	381	)))|=(((
...	...	@@ -437,9 +437,7 @@
437	437	This way different setters can be defined for different simulation runs or manual testing.
438	438	)))
439	439
440		-\\
441	441
442		-\\
443	443
444	444	----
445	445
...	...	@@ -470,7 +470,6 @@
470	470	}
471	471	{{/code}}
472	472
473		-\\
474	474
475	475	Configuration for two executables with redirection between both:
476	476
...	...	@@ -565,7 +565,6 @@
565	565	}
566	566	{{/code}}
567	567
568		-\\
569	569
570	570	== Implementation Details ==
571	571
...	...	@@ -572,7 +572,7 @@
572	572	The following are details about the implementation of the simulation and the JSON format that is used to communicate the variables in the models.
573	573
574	574	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.
575		-\\
	568	+
576	576
577	577	=== The JSON Format ===
578	578