Last modified by Richard Kreissig on 2023/09/14 10:20
<
From version < 35.1 >
edited by uru
on 2015/01/28 15:16
To version < 37.1 >
edited by uru
on 2015/01/28 15:52
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -279,6 +279,22 @@
279 279  (((
280 280  
281 281  )))
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 +)))
282 282  |(((
283 283  Port Constraints
284 284  )))|(((
... ... @@ -484,7 +484,7 @@
484 484  )))
485 485  |(% colspan="1" %)(% colspan="1" %)
486 486  (((
487 -(% class="confluence-link" %) Content Alignment[[doc:||anchor="contentAlignment"]]
503 +[[Content Alignment>>doc:||anchor="contentAlignment"]]
488 488  )))|(% colspan="1" %)(% colspan="1" %)
489 489  (((
490 490  de.cau.cs.kieler.klay.layered.contentAlignment
... ... @@ -659,25 +659,6 @@
659 659  )))
660 660  |(% colspan="1" %)(% colspan="1" %)
661 661  (((
662 -[[Maximal Iterations>>doc:||anchor="maximalIterations"]]
663 -)))|(% colspan="1" %)(% colspan="1" %)
664 -(((
665 -de.cau.cs.kieler.klay.layered.nodeLayering
666 -)))|(% colspan="1" %)(% colspan="1" %)
667 -(((
668 -Int
669 -)))|(% colspan="1" %)(% colspan="1" %)
670 -(((
671 -Parents
672 -)))|(% colspan="1" %)(% colspan="1" %)
673 -(((
674 -10.000.000
675 -)))|(% colspan="1" %)(% colspan="1" %)
676 -(((
677 -nodeLayering=NETWORK_SIMPLEX
678 -)))
679 -|(% colspan="1" %)(% colspan="1" %)
680 -(((
681 681  [[Merge Edges>>doc:||anchor="mergeEdges"]]
682 682  )))|(% colspan="1" %)(% colspan="1" %)
683 683  (((
... ... @@ -747,25 +747,6 @@
747 747  (((
748 748  
749 749  )))
750 -|(% colspan="1" %)(% colspan="1" %)
751 -(((
752 -[[Port Anchor Offset>>doc:||anchor="portAnchor"]]
753 -)))|(% colspan="1" %)(% colspan="1" %)
754 -(((
755 -de.cau.cs.kieler.klay.layered.portAnchor
756 -)))|(% colspan="1" %)(% colspan="1" %)
757 -(((
758 -Object
759 -)))|(% colspan="1" %)(% colspan="1" %)
760 -(((
761 -Ports
762 -)))|(% colspan="1" %)(% colspan="1" %)
763 -(((
764 -
765 -)))|(% colspan="1" %)(% colspan="1" %)
766 -(((
767 -
768 -)))
769 769  |(((
770 770  [[Thoroughness>>doc:||anchor="thoroughness"]]
771 771  )))|(((
... ... @@ -787,18 +787,18 @@
787 787  
788 788  == Add Unnecessary Bendpoints ==
789 789  
790 -
791 -
792 792  {{id name="addUnnecessaryBendpoints"/}}
793 793  
770 +
771 +
794 794  By 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.
795 795  
796 796  == Content Alignment ==
797 797  
798 -
799 -
800 800  {{id name="contentAlignment"/}}
801 801  
778 +
779 +
802 802  Determines 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.
803 803  
804 804  {{note}}
... ... @@ -805,14 +805,12 @@
805 805  This option is not tested for external ports with port constraints {{code language="none"}}FIXED_RATIO{{/code}} or {{code language="none"}}FIXED_POS{{/code}}.
806 806  {{/note}}
807 807  
808 -
809 -
810 810  == Crossing Minimization ==
811 811  
812 -
813 -
814 814  {{id name="crossingMinimization"/}}
815 815  
790 +
791 +
816 816  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:
817 817  
818 818  * LAYER_SWEEP
... ... @@ -822,10 +822,10 @@
822 822  
823 823  == Cycle Breaking ==
824 824  
825 -
826 -
827 827  {{id name="cycleBreaking"/}}
828 828  
803 +
804 +
829 829  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:
830 830  
831 831  * GREEDY
... ... @@ -835,18 +835,18 @@
835 835  
836 836  == Direction ==
837 837  
838 -
839 -
840 840  {{id name="direction"/}}
841 841  
816 +
817 +
842 842  The 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}}.
843 843  
844 844  == Edge Spacing Factor ==
845 845  
846 -
847 -
848 848  {{id name="edgeSpacingFactor"/}}
849 849  
824 +
825 +
850 850  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.
851 851  
852 852  [[image:attach:edgeSpacingFactor.png]]
... ... @@ -853,10 +853,10 @@
853 853  
854 854  == Edge Label Side Selection ==
855 855  
856 -
857 -
858 858  {{id name="edgeLabelSideSelection"/}}
859 859  
834 +
835 +
860 860  Determines how KLay Layered places edge labels. The following strategies are available:
861 861  
862 862  * ALWAYS_UP
... ... @@ -872,10 +872,10 @@
872 872  
873 873  == Feedback Edges ==
874 874  
875 -
876 -
877 877  {{id name="feedbackEdges"/}}
878 878  
853 +
854 +
879 879  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.
880 880  
881 881  With feedback edges:
... ... @@ -888,10 +888,10 @@
888 888  
889 889  == Fixed Alignment ==
890 890  
891 -
892 -
893 893  {{id name="fixedAlignment"/}}
894 894  
869 +
870 +
895 895  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.
896 896  
897 897  This option should usually be left alone.
... ... @@ -898,10 +898,10 @@
898 898  
899 899  == Interactive Reference Point ==
900 900  
901 -
902 -
903 903  {{id name="interactiveReferencePoint"/}}
904 904  
879 +
880 +
905 905  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:
906 906  
907 907  * TOP_LEFT
... ... @@ -911,10 +911,10 @@
911 911  
912 912  == Layer Constraint ==
913 913  
914 -
915 -
916 916  {{id name="layerConstraint"/}}
917 917  
892 +
893 +
918 918  The 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.
919 919  
920 920  [[image:attach:layer_constraints.png]]
... ... @@ -925,10 +925,10 @@
925 925  
926 926  == Linear Segments Deflection Dampening ==
927 927  
928 -
929 -
930 930  {{id name="deflectionDampening"/}}
931 931  
906 +
907 +
932 932  {{note}}
933 933  This is a very advanced layout option that you normally shouldn't worry about.
934 934  {{/note}}
... ... @@ -937,18 +937,18 @@
937 937  
938 938  == Maximal Iterations ==
939 939  
940 -
941 -
942 942  {{id name="maximalIterations"/}}
943 943  
918 +
919 +
944 944  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.
945 945  
946 946  == Merge Edges ==
947 947  
948 -
949 -
950 950  {{id name="mergeEdges"/}}
951 951  
926 +
927 +
952 952  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.
953 953  
954 954  [[image:attach:merging.png]]
... ... @@ -955,10 +955,10 @@
955 955  
956 956  == Merge Hierarchy-Crossing Edges ==
957 957  
958 -
959 -
960 960  {{id name="mergeHierarchyEdges"/}}
961 961  
936 +
937 +
962 962  If 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.
963 963  
964 964  [[image:attach:merge_hierarchy_edges.png]]
... ... @@ -965,10 +965,10 @@
965 965  
966 966  == Node Layering ==
967 967  
968 -
969 -
970 970  {{id name="nodeLayering"/}}
971 971  
946 +
947 +
972 972  Decides which algorithm is used to compute the layer each node is placed in. We have different algorithms available, with different optimization goals:
973 973  
974 974  * NETWORK_SIMPLEX
... ... @@ -980,10 +980,10 @@
980 980  
981 981  == Node Placement ==
982 982  
983 -
984 -
985 985  {{id name="nodePlacement"/}}
986 986  
961 +
962 +
987 987  Decides 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:
988 988  
989 989  * BRANDES_KOEPF
... ... @@ -995,22 +995,10 @@
995 995  * SIMPLE
996 996  Minimizes the area at the expense of... well, pretty much everything else.
997 997  
998 -== Port Anchor Offset ==
999 -
1000 -
1001 -
1002 -{{id name="portAnchor"/}}
1003 -
1004 -Since ports have a size, we need a concrete point inside the port that edges should start or end in. In KLay Layered, this is referred to as the //port anchor//. By default, the center of each port is used as its port anchor, but this behavior can be overridden by setting an explicit port anchor.
1005 -
1006 -In the following example, the port anchor of the left port was moved upwards, while the port anchor of the second port was moved downwards:
1007 -
1008 -[[image:attach:port_anchors.png]]
1009 -
1010 1010  == Thoroughness ==
1011 1011  
1012 -
1013 -
1014 1014  {{id name="thoroughness"/}}
1015 1015  
978 +
979 +
1016 1016  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.
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -10751024
1 +10751224
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/10751024/KLay Layered Layout Options
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/10751224/KLay Layered Layout Options

Navigation

Quick Links

KIELER on GitHub
RTSYS Homepage