layout_network
Compute a force-directed graph layout with a fast forceAtlas2 implementation.
Usage
The following example shows how the step can be used in a recipe.
Examples
Examples
For a weighted layout provide both input columns, e.g.
For a weighted layout provide both input columns, e.g.
General syntax for using the step in a recipe. Shows the inputs and outputs the step is expected to receive and will produce respectively. For futher details see sections below.
Inputs & Outputs
The following are the inputs expected by the step and the outputs it produces. These are generally
columns (ds.first_name
), datasets (ds
or ds[["first_name", "last_name"]]
) or models (referenced
by name e.g. "churn-clf"
).
Inputs
Inputs
Outputs
Outputs
Configuration
The following parameters can be used to configure the behaviour of the step by including them in
a json object as the last “input” to the step, i.e. step(..., {"param": "value", ...}) -> (output)
.
Parameters
Parameters
Attracts nodes to the center. Prevents islands from drifting away.
Examples
Examples
- 0.05
The amount of repulsion. Greater values lead to a larger and more sparse graph.
Examples
Examples
- 0.8
Algorithmic “resolution”. Greater values lead to faster execution at the expense of less precise calculations.
Values must be in the following range:
Prefer authorities over hubs. Prefer “authorities” (nodes with a high indegree) over hubs (nodes with a high outdegree). Authorities will have more central and hubs more peripheral positions. (default=false).
Examples
Examples
- False
Usually produces tighter clusters. Enabling it may also require adjusting the scalingRatio.
Examples
Examples
- False
Try to avoid overlap between nodes.
Examples
Examples
- False
The more the better, though it will take longer.
Examples
Examples
- 300
How much space to (try and) give each node in the final layout.
Values must be in the following range:
Links with weights below this value will be ignored.
Values must be in the following range:
Normalize weights to the range [0, 1].