Summary

• Page properties (1 modified, 0 added, 0 removed)
• Objects (1 modified, 0 added, 0 removed)
  • Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Content

...	...	@@ -16,19 +16,11 @@
16	16
17	17	Within KIELER a single state of a simulation is represented as a //Data Pool//. A data pool can have multiple models. Each model can have multiple variables. Thus a representation of a complete run of a simulation can be implemented as list of data pools.
18	18
19		-Executables for simulation are created using the incremental project builder that is part of the project management. The typical steps to create an executable are:
	19	+== Starting a Simulation ==
20	20
21		-* Compiling a model using the KIELER compiler
22		-* Generating the simulation wrapper code for the model using template processing
23		-* Compiling the resulting code using, e.g., gcc.
24		-
25		-For more insight of the simulation generation, please take a look at the [[doc:V2 Project Management]].
26		-
27		-== Using the Simulation ==
28		-
29	29	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 started as simulation and what simulation configuration is created for it.
30	30
31		-(% class="relative-table wrapped" style="width: 99.9453%;" %)
	23	+(% class="relative-table" style="width: 99.9453%;" %)
32	32	|=(((
33	33	Selection
34	34	)))|=(% colspan="1" %)(% colspan="1" %)
...	...	@@ -100,37 +100,14 @@
100	100	The current pool of the simulation is written as JSON object to the simout file.
101	101	)))
102	102
103		-=== Playing the Simulation ===
104		-
105		-Besided manually stepping through the simulation tick after tick, it is possible to let the simulation play automatically. In play mode, a macro tick is performed after a given time, which can be defined in the data pool view (e.g. to perform a tick every 200ms).
106		-
107		-=== Stepping Back in the Simulation ===
108		-
109		-When clicking the //Step Back// button, the values of a former tick are set in the data pool view as user values, which will be assigned to the model before the next tick is executed.
110		-
111		-This it is possible to revert a model to a previous state if all variables that define the current state of this model are recorded in the data pool.
112		-
113		-=== The Data Pool View ===
114		-
115		-The current data pool can be seen in the Data Pool View (Window > Show View > Other > KIELER Simulation > Data Pool View).
116		-
117		-In the view, the variable values can be modified by the user via clicking the column //User Value//. If a user value is specified for a variable, the corresponding row is highlighted and marked with an asterisk ( * ) . The value is applied to the variable and send to the model before the next tick is performed.
118		-
119		-When using traces in the simulation, a trace mismatch of a variable will be highlighted in the data pool view. A tooltip on the //Current Value// column shows details about the mismatch. The trace mismatch is kept between ticks. To clear a mismatch, use the menu of the view and select //Clear Trace Mismatches//.
120		-
121		-When the data pool view is selected, stepping through the simulation can be done using the right arrow on the keyboard, which is often more useful than clicking the corresponding button in the toolbar.
122		-
123	123	== Data Handlers ==
124	124
125		-A simulation consists of a list of //data handlers//, that can read or write the current data pool. A macro tick in the simulation then consists of the execution of the read or write actions on these data handlers. Performing a single action on a data handler is called a //sub tick// and typically not necessary but can be useful to see the effect of single data handlers on the data pool.
	97	+A simulation consists of a list of //data handlers//, that can read or write the current data pool. Which handlers are available are explained in the following.
126	126
127		-Which handlers are available are explained in the following.
128		-
129	129	=== Executable ===
130	130
131	131	For instance, there exists a data handler for the simulation of an executable. The write operation of this data handler will send the inputs of the model as JSON object on stdin of the process. Afterwards the tick is triggered, and finally the data pool is updated with the JSON object received from stdout of the running process.
132	132
133		-(% class="wrapped" %)
134	134	|=(((
135	135	Attribute
136	136	)))|=(% colspan="1" %)(% colspan="1" %)
...	...	@@ -160,7 +160,6 @@
160	160
161	161	Multiple models may interact with each other as some can have inputs that are generated as outputs of other models. To implement this behaviour in the simulation, the redirect data handler has been created. It sets the inputs of a model to the outputs of some other model in the data pool. Thus the outputs of a some model A can be used as inputs of some model B.
162	162
163		-(% class="wrapped" %)
164	164	|=(((
165	165	Attribute
166	166	)))|=(((
...	...	@@ -201,7 +201,6 @@
201	201	* Perform the tick of the model A
202	202	* Compare the outputs of the trace and the model A
203	203
204		-(% class="wrapped" %)
205	205	|=(((
206	206	Attribute
207	207	)))|=(((
...	...	@@ -287,7 +287,7 @@
287	287
288	288	Simulation input files can also be used to feed the simulation with data to be visualized via the simulation visualization.
289	289
290		-(% class="relative-table wrapped" style="width: 81.5545%;" %)
	257	+(% class="relative-table" style="width: 81.5545%;" %)
291	291	|=(((
292	292	Attribute
293	293	)))|=(((
...	...	@@ -322,7 +322,7 @@
322	322
323	323	This data handler writes the output of the model in the simulation to the specified file.
324	324
325		-(% class="relative-table wrapped" style="width: 81.7734%;" %)
	292	+(% class="relative-table" style="width: 81.7734%;" %)
326	326	|=(((
327	327	Attribute
328	328	)))|=(((
...	...	@@ -353,7 +353,7 @@
353	353
354	354	== KiSim ==
355	355
356		-Which data handlers are used and which actions are performed on them for each macro tick can be configured using a DSL, namely **KiSim**.
	323	+Which data handlers are used and which actions are performed on them can be configured using a DSL, namely **KiSim**.
357	357
358	358	A kisim file contains two main parts:
359	359

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-31162500
	1	+31162495

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/31162500/V2 Simulation
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/31162495/V2 Simulation