Changes for page Simulation (KiSim)

Last modified by Richard Kreissig on 2023/09/14 11:07
<
From version < 7.1 >
edited by aas2
on 2017/10/23 15:51
To version < 8.1 >
edited by aas2
on 2017/10/23 16:34
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -405,7 +405,7 @@
405 405  
406 406  This data handler is only used for easier debugging and setting up simulations for different test runs. It sets the variables in the data pool to constant values, typically once for the simulation in the initialization part of a kisim file.
407 407  
408 -(% class="relative-table" %)
408 +(% class="relative-table wrapped" %)
409 409  |=(((
410 410  Attribute
411 411  )))|=(((
... ... @@ -560,3 +560,143 @@
560 560   write sim A
561 561  }
562 562  {{/code}}
563 +
564 +\\
565 +
566 +== Implementation Details ==
567 +
568 +The following are details about the implementation of the simulation and the JSON format that is used to communicate the variables in the models.
569 +
570 +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.
571 +\\
572 +
573 +=== The JSON Format ===
574 +
575 +The JSON format is designed to communicate the state of a simulation. In KIELER such a state is saved as a single data pool. This means the JSON format for the communication with running simulations is also the JSON format for data pools.
576 +
577 +It mainly consists of a list of models and a map of models. The models consist mainly of a map of their variables. The most important field of a variable is their value.
578 +
579 +{{code}}
580 +{ "MODEL_NAME0" : {
581 + "VAR0":{"value": "VAR0_VALUE"}, "VAR1":{"value":"VAR1_VALUE"}, ...
582 + }
583 + "MODEL_NAME1" : {
584 + "VAR0":{"value": "VAR0_VALUE"}, "VAR1":{"value":"VAR1_VALUE"}, ...
585 + }
586 + ...
587 + "actionIndex" : "ACTION_INDEX_AFTER_WHICH_THE_DATA_POOL_WAS_CREATED"
588 +}
589 +{{/code}}
590 +
591 +Besides these core informations, an additional field "actionIndex" can be set for the data pool. In the simulation the actions of data handlers are executed to create a macro tick. Therefore the action index takes the task of a program counter. It determines the next action to be executed. Thus in the JSON format the field "actionIndex" can be set to store when the data pool was created in the simulation.
592 +
593 +There are also additional fields for variables than their value. However these only need to be communicated once after the initialization of the model and are explained in the table below.
594 +
595 +|=(((
596 +Field Name
597 +)))|=(((
598 +Example Values
599 +)))|=(((
600 +Description
601 +)))
602 +|(((
603 +type
604 +)))|(((
605 +int
606 +
607 +bool
608 +
609 +pure
610 +
611 +float
612 +
613 +double
614 +
615 +string
616 +)))|(((
617 +The type of the variable in the source model.
618 +
619 +Because this information is lost in general in the compilation (for instance a bool is compiled to a char in C code), the simulation can communicate the intended variable type in the source model.
620 +)))
621 +|(((
622 +interface
623 +)))|(((
624 +0
625 +
626 +1
627 +
628 +2
629 +
630 +3
631 +
632 +4
633 +
634 +5
635 +
636 +6
637 +)))|(((
638 +Bitmask, that determines how the variable is used in the source model's interface (e.g. input, output, internal, other).
639 +A bitmask has been choosen because a mixture of a variables interface types is possible (e.g. input, output, input output)
640 +
641 +|=(((
642 +Interface Type
643 +)))|=(((
644 +Binary Bitmask
645 +)))|=(((
646 +Decimal Number
647 +)))
648 +|(((
649 +Other
650 +)))|(((
651 +0000
652 +)))|(((
653 +0
654 +)))
655 +|(% colspan="1" %)(% colspan="1" %)
656 +(((
657 +Internal
658 +)))|(% colspan="1" %)(% colspan="1" %)
659 +(((
660 +0001
661 +)))|(% colspan="1" %)(% colspan="1" %)
662 +(((
663 +1
664 +)))
665 +|(% colspan="1" %)(% colspan="1" %)
666 +(((
667 +Output
668 +)))|(% colspan="1" %)(% colspan="1" %)
669 +(((
670 +0010
671 +)))|(% colspan="1" %)(% colspan="1" %)
672 +(((
673 +2
674 +)))
675 +|(% colspan="1" %)(% colspan="1" %)
676 +(((
677 +Input
678 +)))|(% colspan="1" %)(% colspan="1" %)
679 +(((
680 +0100
681 +)))|(% colspan="1" %)(% colspan="1" %)
682 +(((
683 +4
684 +)))
685 +|(% colspan="1" %)(% colspan="1" %)
686 +(((
687 +Input Output
688 +)))|(% colspan="1" %)(% colspan="1" %)
689 +(((
690 +0110
691 +)))|(% colspan="1" %)(% colspan="1" %)
692 +(((
693 +6
694 +)))
695 +
696 +Not that internal is intended for variables that are neither input nor output but still part of the source model, in contrast to variables that are created in the compilation (e.g. register flags).
697 +Anyway an input and output is also a internal variable normally.
698 +)))
699 +
700 +=== Python Example ===
701 +
702 +\\
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -33260022
1 +33260063
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/33260022/V2 Simulation
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/33260063/V2 Simulation

Navigation

Quick Links

KIELER on GitHub
RTSYS Homepage