operations
assemble.network_data
¶
Documentation | Create a 'network_data' instance from one or two tables. This module needs at least one table as input, providing the edges of the resulting network data set. If no further table is created, basic node information will be automatically created by using unique values from the edges source and target columns. If no |
|||||||||||||||||||||||||||||||||||||||||||||
Inputs |
|
|||||||||||||||||||||||||||||||||||||||||||||
Outputs |
|
create.network_data.from.file
¶
Documentation | Create a table from a file, trying to auto-determine the format of said file. Supported file formats (at the moment):
|
||||||||||
Inputs |
|
||||||||||
Outputs |
|
export.network_data.as.adjlist_file
¶
Documentation | Export network data as adjacency list file. |
|||||||||||||||||||||||||
Inputs |
|
|||||||||||||||||||||||||
Outputs |
|
export.network_data.as.edgelist_file
¶
Documentation | Export network data as edgelist file. |
|||||||||||||||||||||||||
Inputs |
|
|||||||||||||||||||||||||
Outputs |
|
export.network_data.as.gexf_file
¶
Documentation | Export network data as gexf file. |
|||||||||||||||||||||||||
Inputs |
|
|||||||||||||||||||||||||
Outputs |
|
export.network_data.as.graphml_file
¶
Documentation | Export network data as graphml file. |
|||||||||||||||||||||||||
Inputs |
|
|||||||||||||||||||||||||
Outputs |
|
export.network_data.as.multiline_adjlist_file
¶
Documentation | Export network data as multiline adjacency list file. |
|||||||||||||||||||||||||
Inputs |
|
|||||||||||||||||||||||||
Outputs |
|
export.network_data.as.network_text_file
¶
Documentation | Export network data as network text file (with a '.network' extension). |
|||||||||||||||||||||||||
Inputs |
|
|||||||||||||||||||||||||
Outputs |
|
network_data.extract_components
¶
Documentation | Extract the largest connected component from this network data. This module analyses network data and checks if it contains clusters, and if so, how many. If all nodes are connected, all nodes will have '0' as value in the component_id field. Otherwise, the nodes will be assigned 'component_id'-s according to the component they belong to, with the largest component having '0' as component_id, the second largest '1' and so on. If two components have the same size, who gets the higher component_id is not determinate. |
||||||||||||||||||||
Inputs |
|
||||||||||||||||||||
Outputs |
|
network_data.extract_cut_points
¶
Documentation | Create a list of nodes that are cut-points. Cut-points are any node in a network whose removal disconnects members of the network, creating one or more new distinct components. Uses the rustworkx.articulation_points function. |
||||||||||
Inputs |
|
||||||||||
Outputs |
|
network_data.redefine_edges
¶
Documentation | Redefine edges by merging duplicate edges and applying aggregation functions to certain edge attributes. |
|||||||||||||||
Inputs |
|
|||||||||||||||
Outputs |
|
network_data_filter.component
¶
Documentation | Retrieve a single sub-component from a network data object. |
||||||||||||||||||||
Inputs |
|
||||||||||||||||||||
Outputs |
|