ortools-clone/ortools/graph

Graph and Network Flows

This directory contains data structures and algorithms for graph and network flow problems.

It contains in particular:

• well-tuned algorithms (for example shortest, paths and Hamiltonian paths).
• hard-to-find algorithms (Hamiltonian paths, push-relabel flow algorithms).
• other, more common algorithm, that are useful to use with EbertGraph.

Graph representations:

• ebert_graph.h: entry point for a directed graph class. Deprecated. Prefer using //util/graph/graph.h.

Paths:

• shortest_paths.h: entry point for shortest paths. Includes Dijkstra and Bellman-Ford algorithms.

• hamiltonian_path.h: entry point for computing minimum Hamiltonian paths and cycles on directed graphs with costs on arcs, using a dynamic-programming algorithm. (It does not need ebert_graph.h or digraph.h.)

Graph decompositions:

• connected_components.h: entry point for computing connected components in an undirected graph. (It does not need ebert_graph.h or digraph.h.)

• strongly_connected_components.h: entry point for computing the strongly connected components of a directed graph.

• cliques.h: entry point for computing maximum cliques and clique covers in a directed graph, based on the Bron-Kerbosch algorithm. (It does not need ebert_graph.h or digraph.h.)

Flow algorithms:

• linear_assignment.h: entry point for solving linear sum assignment problems (classical assignment problems where the total cost is the sum of the costs of each arc used) on directed graphs with arc costs, based on the Goldberg-Kennedy push-relabel algorithm.

• max_flow.h: entry point for computing maximum flows on directed graphs with arc capacities, based on the Goldberg-Tarjan push-relabel algorithm.

• min_cost_flow.h: entry point for computing minimum-cost flows on directed graphs with arc capacities, arc costs, and supplies/demands at nodes, based on the Goldberg-Tarjan push-relabel algorithm.

Wrappers

• python: the SWIG code that makes the wrapper available in Python and its unit tests.

• java: the SWIG code that makes the wrapper available in Java and its unit tests.

• csharp: the SWIG code that makes the wrapper available in C# and its unit tests.

Samples

You can find some canonical examples in samples