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

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.uru
1 +XWiki.dag
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-PMoJE"/}}
4 +* {{mention reference="XWiki.uru" style="FULL_NAME" anchor="XWiki-uru-azXeo"/}}
5 5  
6 6  Related Theses:
7 7  
... ... @@ -34,7 +34,7 @@
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 {{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.
37 +Besides jobs, there are also {{code language="none"}}RangeJobs and CompareJobs.{{/code}} A RangeJob can be used to 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. The CompareJob can apply two different layouts to a graph and compare the results (the graph is copied internally so the layouts do not influence each other). The two layouts are specified via two layout blocks as shown in the avg_distance example below. This kind of job can be used to analyze the effect of a layout on the individual nodes (e.g. the distance nodes are moved).
38 38  
39 39  To execute GrAna based on a //.grana// file, right click the file and select //Execute Analysis Batch ...//
40 40  
... ... @@ -48,6 +48,7 @@
48 48   original_alg "/Test/results/original.csv"
49 49   awesome_alg "file://workspaces/eclps/Test/results/new.csv"
50 50   thoroughness "/Test/results/thorough.csv"
51 + compare "/Test/results/compare.csv"
51 51  
52 52  execute all
53 53  
... ... @@ -102,6 +102,20 @@
102 102   de.cau.cs.kieler.kiml.grana.edgeCrossings
103 103   component 3
104 104   output ref thoroughness
106 +
107 +comparejob avg_distance
108 + resources
109 + ref random
110 + layoutoptions
111 + l1 {
112 + algorithm: fixed
113 + }
114 + l2 {
115 + algorithm: layered
116 + }
117 + analyses
118 + de.cau.cs.kieler.grana.compare.averageDistance
119 + output ref compare
105 105  {{/code}}
106 106  
107 107  == Eclipse Wizard ==
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -28672399
1 +40075275
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/28672399/Graph Analysis (GrAna)
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/40075275/Graph Analysis (GrAna)