Summary

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

Details

Page properties

Content

...	...	@@ -4,6 +4,8 @@
4	4
5	5	{{toc/}}
6	6
	7	+----
	8	+
7	7	== Overview ==
8	8
9	9	After a model has been created, it is reasonable to test if the model does what is expected. This can be achieved by simulating the model. The simulation must
...	...	@@ -16,6 +16,16 @@
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
	21	+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:
	22	+
	23	+* Compiling a model using the KIELER compiler
	24	+* Generating the simulation wrapper code for the model using template processing
	25	+* Compiling the resulting code using, e.g., gcc.
	26	+
	27	+For more insight of the simulation generation, please take a look at the [[doc:V2 Project Management]].
	28	+
	29	+----
	30	+
19	19	== Using the Simulation ==
20	20
21	21	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.
...	...	@@ -112,6 +112,8 @@
112	112
113	113	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.
114	114
	127	+----
	128	+
115	115	== Data Handlers ==
116	116
117	117	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.
...	...	@@ -343,6 +343,8 @@
343	343	Name of the model in the simulation that will be written as JSON object to the simout file
344	344	)))
345	345
	360	+----
	361	+
346	346	== KiSim ==
347	347
348	348	Which data handlers are used and which actions are performed on them for each macro tick can be configured using a DSL, namely **KiSim**.

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-31162497
	1	+33260015

URL

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