Changes for page How to try out Interactive Timing Analysis
Last modified by Alexander Schulz-Rosengarten on 2023/09/11 16:17
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -23,12 +23,11 @@ 23 23 1. Open any of the .sct files in the editor (right click the file). The Diagram view should open automatically and show you an image of the model. If that does not work, open that view by choosing Window -> Show View -> Other -> KIELER Lightweight Diagrams -> Diagram 24 24 1. Choose your desired Timing Analysis Options in the Diagram Options bar (click image to enlarge): 25 25 \\{{view-file att--filename="ITABild.pdf" height="250"/}} 26 -\\You can switch between percentage, cycles and milliseconds for the timing value display. 27 -1. As a first step you can play around with the timing assumptions on function calls you find in the .asu files for the models (note that FunParc2 has no function calls, so choose something else). You can see how the values and the Hotspot Highlighting change, the view 28 -is updated with every save action. 29 -1. Try to create and edit your own models (right click the project -> new -> Folder, then right click the folder -> new -> file, give the file 30 -a name that ends with .sct). You can edit your file in the textual editor now. Please note that you have to add an assumption file with 31 -the same name as the model file, but the ending .asu that contains timing assumptions for any function call you use in your model. 26 +\\You can switch between percentage, cycles and milliseconds for the timing value display. You can of course also try out the other Diagram and Layout Options in the bar. 27 +1. As a first step you can play around with the timing assumptions on function calls you find in the .asu files for the models (note that FunParc2 has no function calls, so choose something else): 28 +[[image:attach:ITABildAsu.png]] 29 +1. You can see how the values and the Hotspot Highlighting change, the view is updated with every save action. 30 +1. Try to create and edit your own models (right click the project -> new -> Folder, then right click the folder -> new -> file, give the file a name that ends with .sct). You can edit your file in the textual editor now. Please note that you have to add an assumption file with the same name as the model file, but the ending .asu that contains timing assumptions for any function call you use in your model. 32 32 \\\\ 33 33 34 34
- Confluence.Code.ConfluencePageClass[0]
-
- Id
-
... ... @@ -1,1 +1,1 @@ 1 -1739989 21 +17399895 - URL
-
... ... @@ -1,1 +1,1 @@ 1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/1739989 2/How to try out Interactive Timing Analysis1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/17399895/How to try out Interactive Timing Analysis