Last modified by Richard Kreissig on 2023/09/14 10:20
<
From version < 21.1 >
edited by cds
on 2014/04/03 13:53
To version < 46.1 >
edited by Alexander Schulz-Rosengarten
on 2023/07/11 10:25
>
Change comment: Renamed from xwiki:KIELER.Home.Discontinued Projects.Layout Algorithms (KLay).KLay Layered.KLay Layered Layout Options.WebHome

Summary

Details

Page properties
Parent
... ... @@ -1,0 +1,1 @@
1 +KIELER.Home.Discontinued Projects.Layout Algorithms (KLay).KLay Layered.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.cds
1 +XWiki.als
Content
... ... @@ -1,7 +5,3 @@
1 -{{warning}}
2 -This is preliminary and incomplete documentation. You've been warned.
3 -{{/warning}}
4 -
5 5  KLay Layered supports a whole bunch of layout options. Every single one of them is documented here.
6 6  
7 7  **Contents**
... ... @@ -12,11 +12,11 @@
12 12  
13 13  = Overview =
14 14  
15 -For a general introduction on layout options, see [[the KIML documentation>>doc:KIML Layout Options]]. KLay Layered supports layout options defined by KIML and defines additional custom layout options.
11 +For a general introduction on layout options, see [[the KIML documentation>>doc:Kieler.Discontinued Projects.Infrastructure for Meta Layout (KIML).KIML Layout Options.WebHome]]. KLay Layered supports layout options defined by KIML and defines additional custom layout options.
16 16  
17 17  == Supported KIML Layout Options ==
18 18  
19 -KLay Layered supports the following standard layout options defined by KIML. Note that the default value may be altered (highlighted yellow). These layout options are documented on [[KIML's Layout Options page>>doc:KIML Layout Options]].
15 +KLay Layered supports the following standard layout options defined by KIML. Note that the default value may be altered (highlighted yellow). These layout options are documented on [[KIML's Layout Options page>>doc:Kieler.Discontinued Projects.Infrastructure for Meta Layout (KIML).KIML Layout Options.WebHome]].
20 20  
21 21  |=(((
22 22  Option
... ... @@ -29,6 +29,22 @@
29 29  )))|=(((
30 30  Default
31 31  )))
28 +|(% colspan="1" %)(% colspan="1" %)
29 +(((
30 +Additional Port Space
31 +)))|(% colspan="1" %)(% colspan="1" %)
32 +(((
33 +de.cau.cs.kieler.additionalPortSpace
34 +)))|(% colspan="1" %)(% colspan="1" %)
35 +(((
36 +Margins
37 +)))|(% colspan="1" %)(% colspan="1" %)
38 +(((
39 +Nodes
40 +)))|(% colspan="1" %)(% colspan="1" %)
41 +(((
42 +0, 0, 0, 0
43 +)))
32 32  |(((
33 33  Alignment
34 34  )))|(((
... ... @@ -108,7 +108,7 @@
108 108  
109 109  )))
110 110  |(((
111 -Direction
123 +[[Direction>>doc:||anchor="direction"]]
112 112  )))|(((
113 113  de.cau.cs.kieler.direction
114 114  )))|(((
... ... @@ -115,9 +115,8 @@
115 115  Enum
116 116  )))|(((
117 117  Parents
118 -)))|(% class="highlight-yellow" data-highlight-colour="yellow" %)(% class="highlight-yellow" data-highlight-colour="yellow" %)
119 -(((
120 -RIGHT
130 +)))|(((
131 +UNDEFINED
121 121  )))
122 122  |(% colspan="1" %)(% colspan="1" %)
123 123  (((
... ... @@ -145,7 +145,7 @@
145 145  Parents
146 146  )))|(% class="highlight-yellow" data-highlight-colour="yellow" %)(% class="highlight-yellow" data-highlight-colour="yellow" %)
147 147  (((
148 -POLYLINE
159 +ORTHOGONAL
149 149  )))
150 150  |(% colspan="1" %)(% colspan="1" %)
151 151  (((
... ... @@ -268,6 +268,22 @@
268 268  (((
269 269  
270 270  )))
282 +|(% colspan="1" %)(% colspan="1" %)
283 +(((
284 +(% class="confluence-link" %)Port Anchor Offset
285 +)))|(% colspan="1" %)(% colspan="1" %)
286 +(((
287 +de.cau.cs.kieler.klay.layered.portAnchor
288 +)))|(% colspan="1" %)(% colspan="1" %)
289 +(((
290 +Object
291 +)))|(% colspan="1" %)(% colspan="1" %)
292 +(((
293 +Ports
294 +)))|(% colspan="1" %)(% colspan="1" %)
295 +(((
296 +
297 +)))
271 271  |(((
272 272  Port Constraints
273 273  )))|(((
... ... @@ -327,6 +327,22 @@
327 327  (((
328 328  UNDEFINED
329 329  )))
357 +|(% colspan="1" %)(% colspan="1" %)
358 +(((
359 +Port Spacing
360 +)))|(% colspan="1" %)(% colspan="1" %)
361 +(((
362 +de.cau.cs.kieler.portSpacing
363 +)))|(% colspan="1" %)(% colspan="1" %)
364 +(((
365 +Float
366 +)))|(% colspan="1" %)(% colspan="1" %)
367 +(((
368 +Nodes
369 +)))|(% class="highlight-yellow" colspan="1" data-highlight-colour="yellow" %)(% class="highlight-yellow" colspan="1" data-highlight-colour="yellow" %)
370 +(((
371 +10
372 +)))
330 330  |(((
331 331  Priority
332 332  )))|(((
... ... @@ -436,6 +436,44 @@
436 436  (((
437 437  Dependency
438 438  )))
482 +|(% colspan="1" %)(% colspan="1" %)
483 +(((
484 +[[Add Unnecessary Bendpoints>>doc:||anchor="addUnnecessaryBendpoints"]]
485 +)))|(% colspan="1" %)(% colspan="1" %)
486 +(((
487 +de.cau.cs.kieler.klay.layered.unnecessaryBendpoints
488 +)))|(% colspan="1" %)(% colspan="1" %)
489 +(((
490 +Boolean
491 +)))|(% colspan="1" %)(% colspan="1" %)
492 +(((
493 +Parents
494 +)))|(% colspan="1" %)(% colspan="1" %)
495 +(((
496 +false
497 +)))|(% colspan="1" %)(% colspan="1" %)
498 +(((
499 +
500 +)))
501 +|(% colspan="1" %)(% colspan="1" %)
502 +(((
503 +[[Content Alignment>>doc:||anchor="contentAlignment"]]
504 +)))|(% colspan="1" %)(% colspan="1" %)
505 +(((
506 +de.cau.cs.kieler.klay.layered.contentAlignment
507 +)))|(% colspan="1" %)(% colspan="1" %)
508 +(((
509 +EnumSet
510 +)))|(% colspan="1" %)(% colspan="1" %)
511 +(((
512 +Parents
513 +)))|(% colspan="1" %)(% colspan="1" %)
514 +(((
515 +V_TOP, H_LEFT
516 +)))|(% colspan="1" %)(% colspan="1" %)
517 +(((
518 +
519 +)))
439 439  |(((
440 440  [[Crossing Minimization>>doc:||anchor="crossingMinimization"]]
441 441  )))|(((
... ... @@ -492,7 +492,7 @@
492 492  Parents
493 493  )))|(% colspan="1" %)(% colspan="1" %)
494 494  (((
495 -SMART
576 +ALWAYS_DOWN
496 496  )))|(% colspan="1" %)(% colspan="1" %)
497 497  (((
498 498  
... ... @@ -575,22 +575,22 @@
575 575  )))
576 576  |(% colspan="1" %)(% colspan="1" %)
577 577  (((
578 -[[Maximal Iterations>>doc:||anchor="maximalIterations"]]
659 +[[Linear Segments Deflection Dampening>>doc:||anchor="deflectionDampening"]]
579 579  )))|(% colspan="1" %)(% colspan="1" %)
580 580  (((
581 -de.cau.cs.kieler.klay.layered.nodeLayering
662 +de.cau.cs.kieler.klay.layered.linearSegmentsDeflectionDampening
582 582  )))|(% colspan="1" %)(% colspan="1" %)
583 583  (((
584 -Int
665 +Float
585 585  )))|(% colspan="1" %)(% colspan="1" %)
586 586  (((
587 587  Parents
588 588  )))|(% colspan="1" %)(% colspan="1" %)
589 589  (((
590 -10.000.000
671 +0.3
591 591  )))|(% colspan="1" %)(% colspan="1" %)
592 592  (((
593 -nodeLayering=NETWORK_SIMPLEX
674 +nodePlace=LINEAR_SEGMENTS
594 594  )))
595 595  |(% colspan="1" %)(% colspan="1" %)
596 596  (((
... ... @@ -597,7 +597,7 @@
597 597  [[Merge Edges>>doc:||anchor="mergeEdges"]]
598 598  )))|(% colspan="1" %)(% colspan="1" %)
599 599  (((
600 -de.cau.cs.kieler.klay.layered.mergePorts
681 +de.cau.cs.kieler.klay.layered.mergeEdges
601 601  )))|(% colspan="1" %)(% colspan="1" %)
602 602  (((
603 603  Boolean
... ... @@ -663,25 +663,6 @@
663 663  (((
664 664  
665 665  )))
666 -|(% colspan="1" %)(% colspan="1" %)
667 -(((
668 -[[Port Anchor Offset>>doc:||anchor="portAnchor"]]
669 -)))|(% colspan="1" %)(% colspan="1" %)
670 -(((
671 -de.cau.cs.kieler.klay.layered.portAnchor
672 -)))|(% colspan="1" %)(% colspan="1" %)
673 -(((
674 -Object
675 -)))|(% colspan="1" %)(% colspan="1" %)
676 -(((
677 -Ports
678 -)))|(% colspan="1" %)(% colspan="1" %)
679 -(((
680 -
681 -)))|(% colspan="1" %)(% colspan="1" %)
682 -(((
683 -
684 -)))
685 685  |(((
686 686  [[Thoroughness>>doc:||anchor="thoroughness"]]
687 687  )))|(((
... ... @@ -691,76 +691,75 @@
691 691  )))|(((
692 692  Parents
693 693  )))|(((
694 -7
756 +10
695 695  )))|(% colspan="1" %)(% colspan="1" %)
696 696  (((
697 697  
698 698  )))
699 699  
700 -= The Most Important Options =
762 += Detailed Documentation =
701 701  
702 -**TODO:** Write a bit of documentation about the most important layout options and how to use them, possibly with a simple example or something.
764 +This section explains every layout option in more detail. See [[the KIML documentation>>doc:Kieler.Discontinued Projects.Infrastructure for Meta Layout (KIML).KIML Layout Options.WebHome]] for more information on KIML layout options. Those options are only mentioned here if KLay Layered adds some custom behavior.
703 703  
704 -= Detailed Documentation =
766 +== ==
705 705  
706 -This section explains every layout option in more detail. See [[the KIML documentation>>doc:KIML Layout Options]] for more information on KIML layout options. Those options are only mentioned here if KLay Layered adds some custom behavior.
768 +{{id name="addUnnecessaryBendpoints"/}}Add Unnecessary BendpointsBy default, KLay Layered tries not to add bendpoints to an edge at positions where the edge doesn't change direction since there's no real bend there. Turning this option on forces such bend points. More specifically, a bend point is added for each edge that spans more than one layer at the point where it crosses a layer. If hierarchy layout is turned on, a bend point is also added whenever the edge crosses a hierarchy boundary.
707 707  
708 -== Crossing Minimization ==
770 +== ==
709 709  
772 +{{id name="contentAlignment"/}}Content AlignmentDetermines how the content of compound nodes is to be aligned if the compound node's size exceeds the bounding box of the content (i.e. child nodes). This might be the case if for a compound node the size constraint of {{code language="none"}}MINIMUM_SIZE{{/code}} is set and the minimum width and height are set large enough.
710 710  
774 +{{note}}
775 +This option is not tested for external ports with port constraints {{code language="none"}}FIXED_RATIO{{/code}} or {{code language="none"}}FIXED_POS{{/code}}.
776 +{{/note}}
711 711  
712 -{{id name="crossingMinimization"/}}
778 +== ==
713 713  
714 -Crossing minimization determines the ordering of nodes in each layer, which influences the number of edge crossings. This option switches between one of several algorithms that can be used to minimize crossings. Possible values are:
780 +{{id name="crossingMinimization"/}}Crossing MinimizationCrossing minimization determines the ordering of nodes in each layer, which influences the number of edge crossings. This option switches between one of several algorithms that can be used to minimize crossings. Possible values are:
715 715  
716 -* LAYER_SWEEP
782 +* {{code language="none"}}LAYER_SWEEP{{/code}}
717 717  The layer sweep algorithm iterates multiple times over the layers, trying to find node orderings that minimize the number of crossings. The algorithm uses randomization to increase the odds of finding a good result. To improve its results, consider increasing the //Thoroughness// option, which influences the number of iterations done. The //Randomization// seed also influences results.
718 -* INTERACTIVE
784 +* {{code language="none"}}INTERACTIVE{{/code}}
719 719  Orders the nodes of each layer by comparing their positions before the layout algorithm was started. The idea is that the relative order of nodes as it was before layout was applied is not changed. This of course requires valid positions for all nodes to have been set on the input graph before calling the layout algorithm. The interactive layer sweep algorithm uses the //Interactive Reference Point// option to determine which reference point of nodes are used to compare positions.
720 720  
721 -== Cycle Breaking ==
787 +== ==
722 722  
789 +{{id name="cycleBreaking"/}}Cycle BreakingKLay Layered tries to position nodes in a way that all edges point rightwards. This is not possible if the input graph has cycles. Such cycles have to be broken by reversing as few edges as possible. The reversed edges end up pointing leftwards in the resulting diagram. There are different cycle breaking algorithms available:
723 723  
724 -
725 -{{id name="cycleBreaking"/}}
726 -
727 -KLay Layered tries to position nodes in a way that all edges point rightwards. This is not possible if the input graph has cycles. Such cycles have to be broken by reversing as few edges as possible. The reversed edges end up pointing leftwards in the resulting diagram. There are different cycle breaking algorithms available:
728 -
729 -* GREEDY
791 +* {{code language="none"}}GREEDY{{/code}}
730 730  This algorithm reverses edges greedily. The algorithm tries to avoid edges that have the //Priority// property set.
731 -* INTERACTIVE
793 +* {{code language="none"}}INTERACTIVE{{/code}}
732 732  The interactive algorithm tries to reverse edges that already pointed leftwards in the input graph. This requires node and port coordinates to have been set to sensible values.
733 733  
734 -== Edge Spacing Factor ==
796 +== ==
735 735  
798 +{{id name="direction"/}}DirectionThe layout direction influences where the majority of edges in the final layout will point to. With data flow diagrams, this will usually be to the right. With control flow diagrams, it might be downwards. The layout direction defaults to {{code language="none"}}UNDEFINED{{/code}}. This causes KLay Layered to calculate a layout direction based on the {{code language="none"}}ASPECT_RATIO{{/code}} setting. As of now, if the aspect ratio is >=1 (that is, if the diagram should be wider than it is high), the direction is set to {{code language="none"}}RIGHT{{/code}}. Otherwise, it is set to {{code language="none"}}DOWN{{/code}}.
736 736  
800 +== ==
737 737  
738 -{{id name="edgeSpacingFactor"/}}
802 +{{id name="edgeSpacingFactor"/}}Edge Spacing FactorThe edge spacing factor determines the amount of space between edges, relative to the regular //Spacing// value. The idea is that we don't need as much space between edges as we do between nodes.
739 739  
740 -The edge spacing factor determines the amount of space between edges, relative to the regular //Spacing// value. The idea is that we don't need as much space between edges as we do between nodes.
741 -
742 742  [[image:attach:edgeSpacingFactor.png]]
743 743  
744 -== Edge Label Side Selection ==
806 +== ==
745 745  
808 +{{id name="edgeLabelSideSelection"/}}Edge Label Side SelectionDetermines how KLay Layered places edge labels. The following strategies are available:
746 746  
810 +* {{code language="none"}}ALWAYS_UP{{/code}}
811 +Always places edge labels above the edge.
812 +* {{code language="none"}}ALWAYS_DOWN{{/code}}
813 +Always places edge labels below the edge.
814 +* {{code language="none"}}DIRECTION_UP{{/code}}
815 +Places edge labels above edges pointing right, and below edges pointing left.
816 +* {{code language="none"}}DIRECTION_DOWN{{/code}}
817 +Places edge labels below edges pointing right, and above edges pointing left.
818 +* {{code language="none"}}SMART{{/code}}
819 +Uses a heuristic that determines the best edge label placement, also taking the placement of port labels into account.
747 747  
748 -{{id name="edgeLabelSideSelection"/}}
821 +== ==
749 749  
750 -{{warning}}
751 -Document!
752 -{{/warning}}
823 +{{id name="feedbackEdges"/}}Feedback EdgesFeedback edges are edges that feed the output of a node back to be the input of a previous node. This option controls how feedback edges are routed if port constraints are FREE. This influences how much emphasis is put on feedback edges.
753 753  
754 -
755 -
756 -== Feedback Edges ==
757 -
758 -
759 -
760 -{{id name="feedbackEdges"/}}
761 -
762 -Feedback edges are edges that feed the output of a node back to be the input of a previous node. This option controls how feedback edges are routed if port constraints are FREE. This influences how much emphasis is put on feedback edges.
763 -
764 764  With feedback edges:
765 765  
766 766  [[image:attach:feedback_on.png]]
... ... @@ -769,110 +769,81 @@
769 769  
770 770  [[image:attach:feedback_off.png]]
771 771  
772 -== Fixed Alignment ==
833 +== ==
773 773  
835 +{{id name="fixedAlignment"/}}Fixed AlignmentThe {{code language="none"}}BRANDES_KOEPF{{/code}} node placement algorithm computes several different node placements. One of the placements is chosen by the algorithm, usually the one that takes the least amount of space. With this option, a particular result can be chosen.
774 774  
775 -
776 -{{id name="fixedAlignment"/}}
777 -
778 -The BRANDES_KOEPF node placement algorithm computes several different node placements. One of the placements is chosen by the algorithm, usually the one that takes the least amount of space. With this option, a particular result can be chosen.
779 -
780 780  This option should usually be left alone.
781 781  
782 -== Interactive Reference Point ==
839 +== ==
783 783  
841 +{{id name="interactiveReferencePoint"/}}Interactive Reference PointInteractive layering, crossing minimization, and cycle breaking algorithms use node positions to sort nodes into layers or to determine the order of nodes in each layer. However, it is unclear if for example the top left corners of nodes should be compared, or the bottom left corners — different settings might lead to different results. The interactive reference point determines which part of nodes is used to compare their positions. It provides the following settings:
784 784  
785 -
786 -{{id name="interactiveReferencePoint"/}}
787 -
788 -Interactive layering, crossing minimization, and cycle breaking algorithms use node positions to sort nodes into layers or to determine the order of nodes in each layer. However, it is unclear if for example the top left corners of nodes should be compared, or the bottom left corners — different settings might lead to different results. The interactive reference point determines which part of nodes is used to compare their positions. It provides the following settings:
789 -
790 -* TOP_LEFT
843 +* {{code language="none"}}TOP_LEFT{{/code}}
791 791  The top left corner of a node is taken as the reference point.
792 -* CENTER
845 +* {{code language="none"}}CENTER{{/code}}
793 793  The center of a node is taken as the reference point.
794 794  
795 -== Layer Constraint ==
848 +== ==
796 796  
850 +{{id name="layerConstraint"/}}Layer ConstraintThe layer a node is placed in is usually computed by the layer assignment algorithms. However, sometimes certain nodes need to be placed in the first or in the last layer (for example, nodes that represent inputs from the outside). The layer constraint option can be set on such nodes to do just that.
797 797  
852 +[[image:attach:layer_constraints.png]]
798 798  
799 -{{id name="layerConstraint"/}}
854 +{{note}}
855 +This option can also be set to {{code language="none"}}FIRST_SEPARATE{{/code}} and {{code language="none"}}LAST_SEPARATE{{/code}}. These are for internal use only and should not have been publicly exposed in the first place. Using them can result in layout problems.
856 +{{/note}}
800 800  
801 -{{warning}}
802 -Document!
803 -{{/warning}}
858 +== ==
804 804  
805 -
860 +{{id name="deflectionDampening"/}}Linear Segments Deflection Dampening
806 806  
807 -== Maximal Iterations ==
862 +{{note}}
863 +This is a very advanced layout option that you normally shouldn't worry about.
864 +{{/note}}
808 808  
866 +The linear segments node placer can sometimes place nodes in a way that results in unnecessarily large diagrams. This option dampens how much the nodes are moved around. A dampening factor of 1.0 disables dampening and just lets the node placer do what it wants. A more conservative dampening factor of 0.3 (the default) restricts the freedom of the node placer a bit more.
809 809  
868 +== ==
810 810  
811 -{{id name="maximalIterations"/}}
870 +{{id name="maximalIterations"/}}Maximal IterationsDelimits the amount of depth-first-search iterations performed by the network simplex layering strategy. Large, highly connected graphs might require a long time to be processed. This property serves as a timeout after which an exception is raised.
812 812  
813 -Delimits the amount of depth-first-search iterations performed by the network simplex layering strategy. Large, highly connected graphs might require a long time to be processed. This property serves as a timeout after which an exception is raised.
872 +== ==
814 814  
815 -== Merge Edges ==
874 +{{id name="mergeEdges"/}}Merge EdgesIn the KGraph model, edges can either connect to nodes through ports or directly. In the latter case, KLay Layered will introduce a virtual port for each edge, which results in all edges connecting to the node at different points in the final drawing. If this option is switched on, KLay Layered will only generate up to one input and one output port for each node. The option is set on a parent node and applies to all of its children, but not to the parent node itself.
816 816  
817 -
818 -
819 -{{id name="mergeEdges"/}}
820 -
821 -In the KGraph model, edges can either connect to nodes through ports or directly. In the latter case, KLay Layered will introduce a virtual port for each edge, which results in all edges connecting to the node at different points in the final drawing. If this option is switched on, KLay Layered will only generate up to one input and one output port for each node. The option is set on a parent node and applies to all of its children, but not to the parent node itself.
822 -
823 823  [[image:attach:merging.png]]
824 824  
825 -== Merge Hierarchy-Crossing Edges ==
878 +== ==
826 826  
880 +{{id name="mergeHierarchyEdges"/}}Merge Hierarchy-Crossing EdgesIf hierarchical layout is active, this option is the hierarchical equivalent to //Merge Edges//. If set to true on a compound node, all hierarchy-crossing edges that start or end inside that compound node are eligible for merging.
827 827  
882 +[[image:attach:merge_hierarchy_edges.png]]
828 828  
829 -{{id name="mergeHierarchyEdges"/}}
884 +== ==
830 830  
831 -{{warning}}
832 -Document!
833 -{{/warning}}
886 +{{id name="nodeLayering"/}}Node LayeringDecides which algorithm is used to compute the layer each node is placed in. We have different algorithms available, with different optimization goals:
834 834  
835 -== Node Layering ==
836 -
837 -
838 -
839 -{{id name="nodeLayering"/}}
840 -
841 -Decides which algorithm is used to compute the layer each node is placed in. We have different algorithms available, with different optimization goals:
842 -
843 -* NETWORK_SIMPLEX
888 +* {{code language="none"}}NETWORK_SIMPLEX{{/code}}
844 844  This algorithm tries to minimize the length of edges. This is the most computationally intensive algorithm. The number of iterations after which it aborts if it hasn't found a result yet can be set with the [[Maximal Iterations>>doc:||anchor="maximalInterations"]] option.
845 -* LONGEST_PATH
890 +* {{code language="none"}}LONGEST_PATH{{/code}}
846 846  A very simple algorithm that distributes nodes along their longest path to a sink node.
847 -* INTERACTIVE
892 +* {{code language="none"}}INTERACTIVE{{/code}}
848 848  Distributes the nodes into layers by comparing their positions before the layout algorithm was started. The idea is that the relative horizontal order of nodes as it was before layout was applied is not changed. This of course requires valid positions for all nodes to have been set on the input graph before calling the layout algorithm. The interactive node layering algorithm uses the //Interactive Reference Point// option to determine which reference point of nodes are used to compare positions.
849 849  
850 -== Node Placement ==
895 +== ==
851 851  
897 +{{id name="nodePlacement"/}}Node PlacementDecides which algorithm is used to compute the y coordinate of each node. This influences the length of edges, the number of edge bends, and the height of the diagram. We have different algorithms available, with different optimization goals:
852 852  
899 +* {{code language="none"}}BRANDES_KOEPF{{/code}}
900 +Minimizes the number of edge bends at the expense of diagram size: diagrams drawn with this algorithm are usually higher than diagrams drawn with other algorithms.
901 +* {{code language="none"}}LINEAR_SEGMENTS{{/code}}
902 +Computes a balanced placement.
903 +* {{code language="none"}}INTERACTIVE{{/code}}
904 +Tries to keep the preset y coordinates of nodes from the original layout. For dummy nodes, a guess is made to infer their coordinates. Requires the other interactive phase implementations to have run as well.
905 +* {{code language="none"}}SIMPLE{{/code}}
906 +Minimizes the area at the expense of... well, pretty much everything else.
853 853  
854 -{{id name="nodePlacement"/}}
908 +== ==
855 855  
856 -{{warning}}
857 -Document!
858 -{{/warning}}
859 -
860 -== Port Anchor Offset ==
861 -
862 -
863 -
864 -{{id name="portAnchor"/}}
865 -
866 -{{warning}}
867 -Document!
868 -{{/warning}}
869 -
870 -
871 -
872 -== Thoroughness ==
873 -
874 -
875 -
876 -{{id name="thoroughness"/}}
877 -
878 -There are heuristics in use all over KLay Layered whose results often improve with the number of iterations computed. The thoroughness is a measure for telling KLay Layered to compute more iterations to improve the quality of results, at the expense of performance.
910 +{{id name="thoroughness"/}}ThoroughnessThere are heuristics in use all over KLay Layered whose results often improve with the number of iterations computed. The thoroughness is a measure for telling KLay Layered to compute more iterations to improve the quality of results, at the expense of performance.
edgeSpacingFactor.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +10.2 KB
Content
feedback_off.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +7.1 KB
Content
feedback_on.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +11.4 KB
Content
layer_constraints.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +17.5 KB
Content
merge_hierarchy_edges.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +102.1 KB
Content
merging.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +16.0 KB
Content
port_anchors.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +5.4 KB
Content
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -9470136
1 +7111098
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/9470136/KLay Layered Layout Options
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/7111098/KLay Layered Layout Options

Navigation

Quick Links

KIELER on GitHub
RTSYS Homepage