<
From version < 4.1 >
edited by uru
on 2015/06/06 22:05
To version < 5.1 >
edited by uru
on 2015/06/12 15:11
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,7 +1,7 @@
1 1  {{panel title="Project Overview"}}
2 2  Responsible:
3 3  
4 -* {{mention reference="XWiki.uru" style="FULL_NAME" anchor="XWiki-uru-QRYfl"/}}
4 +* {{mention reference="XWiki.uru" style="FULL_NAME" anchor="XWiki-uru-PMoJE"/}}
5 5  
6 6  Related Theses:
7 7  
... ... @@ -34,6 +34,8 @@
34 34  
35 35  You can specify a list of {{code language="none"}}Job{{/code}}s. A job is a self-contained unit of work. It specifies the previously mentioned data using the following keywords: {{code language="none"}}resources{{/code}}, {{code language="none"}}layoutoptions{{/code}}, {{code language="none"}}analyses{{/code}}, and {{code language="none"}}output{{/code}}. Layout options are specified by blocks that start with an arbitrary identifier followed by curly brackets. It is possible to specify multiple blocks of layout options. Each block results in a separate layout run allowing, for instance, to first execute a node placement algorithm and then an edge routing algorithm. For convenience it is possible to specify resources and output files globally at the beginning of the file and then use the {{code language="none"}}ref{{/code}} keyword to reference them from a job.
36 36  
37 +Besides jobs, there is also a {{code language="none"}}RangeJob{{/code}} which can be used analyze the effect of a specific layout option onto a specific metric. In the example below, the //thoroughness// layout option is registered using the {{code language="none"}}rangeoption{{/code}} keyword. An integer range is specified resulting in all values between (inclusive) 1 and 50 being tested. While the analyses specified using the {{code language="none"}}analyses{{/code}} keyword are only measured on the initial graph, the analysis specified using the {{code language="none"}}rangeanalysis{{/code}} keyword will be measured for every tested value of the range layout option. Since analyses can be composed out of multiple components (e.g. the edge crossing analysis states the minimum, maximum, and average number of crossings per edge as well as the sum – four components), the {{code language="none"}}component{{/code}} keyword tells GrAna which component to write to the output file.
38 +
37 37  To execute GrAna based on a //.grana// file, right click the file and select //Execute Analysis Batch ...//
38 38  
39 39  {{code language="java"}}
... ... @@ -45,6 +45,7 @@
45 45  globalOutputs
46 46   original_alg "/Test/results/original.csv"
47 47   awesome_alg "file://workspaces/eclps/Test/results/new.csv"
50 + thoroughness "/Test/results/thorough.csv"
48 48  
49 49  execute all
50 50  
... ... @@ -80,6 +80,25 @@
80 80   de.cau.cs.kieler.kiml.grana.nodeCount
81 81   de.cau.cs.kieler.kiml.grana.edgeCrossings
82 82   output ref awesome_alg
86 +
87 +rangejob thoroughness
88 + resources
89 + ref random
90 + layoutoptions
91 + klay {
92 + de.cau.cs.kieler.algorithm: de.cau.cs.kieler.klay.layered
93 + de.cau.cs.kieler.klay.layered.crossMin: LAYER_SWEEP
94 + }
95 + analyses
96 + de.cau.cs.kieler.kiml.grana.nodeCount
97 + rangeoption
98 + de.cau.cs.kieler.klay.layered.thoroughness
99 + intrange 1 to 50
100 + // floatvalues 0.3, 0.4, 0.5
101 + rangeanalysis
102 + de.cau.cs.kieler.kiml.grana.edgeCrossings
103 + component 3
104 + output ref thoroughness
83 83  {{/code}}
84 84  
85 85  == Eclipse Wizard ==
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -12288349
1 +28672399
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/12288349/Graph Analysis (GrAna)
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/28672399/Graph Analysis (GrAna)