<
From version < 7.1 >
edited by ima
on 2016/01/13 17:24
To version < 6.1 >
edited by ima
on 2016/01/13 17:02
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,26 +16,6 @@
16 16  
17 17  
18 18  
19 -We are in a group that works with interactive timing analysis that offers the overall timing value in the right upper corner of the model state ("Robot"), it is 2183. Also we get timing values for all three regions in their right upper corners. The first of the two timing values in each case denotes the share of the overall execution time that relates to this region, without its included child regions. The second timing value takes the child regions into account additionally. For example, the total execution time is spent in region "Main", but only 28 time units on the uppermost level, the rest is spent in the child regions. In addition to the region time values, the KIELER instance offers hotspot highlighting, which means here that the regions will be colored in different shades of red, which are related to the share this regions has of the overall execution time. For example in this case, about 98 percent of the overall execution time are spent in region HandleMotor, which is why it has a rather dark shade of red, while the other regions are almost white.
19 +We are in a group that works with interactive timing analysis that offers the overall timing value in the right upper corner of the model state ("Robot"), it is 2183. Also we get timing values for all three regions in their right upper corners. The first of the two timing values in each case denotes the share of the overall execution time that relates to this region, without its included child regions. The second timing value takes the child regions into account additionally. For example, the total execution time is spent in region "Robot
20 20  
21 21  
22 -
23 -In addition to this model we get a sheet with information on alternatives for the host code calls in the model and with the specification on the maximum overall worst case execution time we want to acchieve:
24 -
25 -
26 -
27 -**Maximum Worst Case Execution Time: 500 tu**
28 -
29 -**errorLog() / logErrors()**
30 -
31 -**writeLog() / logProcess()**
32 -
33 -**getImage() / takePicture()**
34 -
35 -
36 -
37 -Now we can start to swap host code calls in the textual code to revise our model:
38 -
39 -[[image:attach:ExperimentExampleArrows.png]][[attach:ExperimentExampleArrows.png]]
40 -
41 -
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -14516383
1 +14516381
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/14516383/Experiment Hotspot-Highlighting
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/14516381/Experiment Hotspot-Highlighting