Summary

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

Details

Page properties

Content

...	...	@@ -1,5 +3,3 @@
1		-== General information: ==
2		-
3	3	We are currently running an experiment for which we need participants that are willing to contribute aproximately 20 to 30 minutes of their time. All participants (unless they protest, of course) will be entered into a price draw for 3 amazon vouchers for 25 Euro value each. Thanks if you are considering to take part! Please contact Insa Fuhrmann for one of the time slots from 18th to 25th of January: 0431-880-7526 or in person in room 1113. Also contact Insa Fuhrmann if you have questions that are not answered below.
4	4
5	5	The participants will be asked to give information on how experienced they are with modeling SCCharts and modeling and programming in general.
...	...	@@ -8,34 +8,12 @@
8	8
9	9	The participants will be devided into groups that will work with KIELER versions with different degrees of interactive timing support. We will measure the time it takes for each participant to solve the task as well as the number of call replacements. We will also document the final state of the model.
10	10
11		-== Here is a small example to illustrate the work process (please note that the actual model for the experiment will be larger than this example!): ==
12		-
13		-In a KIELER instance we get a given model:
14		-
15		-[[image:attach:Bildschirmfoto 2016-01-13 um 17.00.47.png]]
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.
	11	+Here is a small example to illustrate the work process (please note that the actual model for the experiment will be larger than the example!):
20	20
21		-
	13	+1. In a KIELER instance we get a given model:
22	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	25
26	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		-
	17	+[[image:attach:Bildschirmfoto 2016-01-13 um 16.48.10.png]][[attach:Bildschirmfoto 2016-01-13 um 16.48.10.png]]

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-14516383
	1	+14516379

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/14516379/Experiment Hotspot-Highlighting