biconnected_component_edges(G)
Biconnected components are maximal subgraphs such that the removal of a node (and all edges incident on that node) will not disconnect the subgraph. Note that nodes may be part of more than one biconnected component. Those nodes are articulation points, or cut vertices. However, each edge belongs to one, and only one, biconnected component.
Notice that by convention a dyad is considered a biconnected component.
The algorithm to find articulation points and biconnected components is implemented using a non-recursive depth-first-search (DFS) that keeps track of the highest level that back edges reach in the DFS tree. A node :None:None:`n` is an articulation point if, and only if, there exists a subtree rooted at :None:None:`n` such that there is no back edge from any successor of :None:None:`n` that links to a predecessor of :None:None:`n` in the DFS tree. By keeping track of all the edges traversed by the DFS we can obtain the biconnected components because all edges of a bicomponent will be traversed consecutively between articulation points.
An undirected graph.
If the input graph is not undirected.
Generator of lists of edges, one list for each bicomponent.
Returns a generator of lists of edges, one list for each biconnected component of the input graph.
>>> G = nx.barbell_graph(4, 2)
... print(nx.is_biconnected(G)) False
>>> bicomponents_edges = list(nx.biconnected_component_edges(G))
... len(bicomponents_edges) 5
>>> G.add_edge(2, 8)
... print(nx.is_biconnected(G)) True
>>> bicomponents_edges = list(nx.biconnected_component_edges(G))See :
... len(bicomponents_edges) 1
The following pages refer to to this document either explicitly or contain code examples using this.
networkx.algorithms.components.biconnected.is_biconnected
networkx.algorithms.components.biconnected.articulation_points
networkx.algorithms.components.biconnected.biconnected_component_edges
networkx.algorithms.components.biconnected.biconnected_components
Hover to see nodes names; edges to Self not shown, Caped at 50 nodes.
Using a canvas is more power efficient and can get hundred of nodes ; but does not allow hyperlinks; , arrows or text (beyond on hover)
SVG is more flexible but power hungry; and does not scale well to 50 + nodes.
All aboves nodes referred to, (or are referred from) current nodes; Edges from Self to other have been omitted (or all nodes would be connected to the central node "self" which is not useful). Nodes are colored by the library they belong to, and scaled with the number of references pointing them