Gump: Approximate Clique Solver
This work builds upon Gump: A Good Approximation for Cliques.
The Maximum Clique Problem: Overview
Description
The Maximum Clique Problem (MCP) is a classic NP-hard problem in graph theory and computer science. Given an undirected graph $G = (V, E)$, a clique is a subset of vertices $C \subseteq V$ where every two distinct vertices are connected by an edge. The goal of MCP is to find the largest possible clique in $G$.
Key Definitions
- Clique: A complete subgraph (all possible edges exist between vertices).
- Maximum Clique: The largest clique in the graph.
- Clique Number ($\omega(G)$): The size of the maximum clique in $G$.
Theoretical Background
- MCP is NP-Hard, meaning no known polynomial-time algorithm solves all cases unless $P = NP$.
- It is closely related to other problems like the Independent Set Problem (complement graph) and Graph Coloring.
- Decision version: "Does a clique of size $k$ exist?" is NP-Complete.
Approaches to Solve MCP
Exact Algorithms
- Brute Force: Check all possible subsets (exponential time $O(2^n)$).
- Branch and Bound: Prune search space by eliminating branches where clique size cannot exceed the current maximum.
- Integer Programming (IP): Formulate as an optimization problem with binary variables and constraints.
- Bron-Kerbosch Algorithm: A recursive backtracking method for listing all maximal cliques.
Heuristic & Approximation Methods
- Greedy Algorithms: Iteratively add vertices with the highest degree or most connections to the current clique.
- Local Search: Improve existing solutions via vertex swaps or perturbations.
- Metaheuristics:
- Genetic Algorithms: Evolve candidate solutions via selection, crossover, and mutation.
- Simulated Annealing: Probabilistic technique inspired by thermodynamics.
- Tabu Search: Avoid revisiting solutions using a "tabu list."
Advanced Techniques
- Reduction Rules: Simplify the graph by removing vertices that cannot be part of the maximum clique.
- Parallel & GPU Computing: Speed up exhaustive searches using parallel processing.
- Machine Learning: Learn graph features to guide heuristic choices (emerging area).
Applications
- Social Network Analysis: Identifying tightly connected groups (communities).
- Bioinformatics: Protein interaction networks, gene regulatory networks.
- Computer Vision: Object recognition, pattern matching.
- Wireless Networks: Resource allocation, interference modeling.
- Combinatorial Optimization: Scheduling, coding theory, cryptography.
Challenges & Open Problems
- Scalability for large graphs (millions of vertices).
- Improving approximation guarantees (best-known is $O(n / \log^2 n)$).
- Hybrid approaches combining exact and heuristic methods.
Conclusion
The Maximum Clique Problem remains a fundamental challenge in computational complexity with broad practical implications. While exact methods are limited to small graphs, heuristic and hybrid approaches enable solutions for real-world applications.
Problem Statement
Input: A Boolean Adjacency Matrix $M$.
Answer: Find a Maximum Clique.
Example Instance: 5 x 5 matrix
| c1 | c2 | c3 | c4 | c5 | |
|---|---|---|---|---|---|
| r1 | 0 | 0 | 1 | 0 | 1 |
| r2 | 0 | 0 | 0 | 1 | 0 |
| r3 | 1 | 0 | 0 | 0 | 1 |
| r4 | 0 | 1 | 0 | 0 | 0 |
| r5 | 1 | 0 | 1 | 0 | 0 |
The input for undirected graph is typically provided in DIMACS format. In this way, the previous adjacency matrix is represented in a text file using the following string representation:
p edge 5 4
e 1 3
e 1 5
e 2 4
e 3 5
This represents a 5x5 matrix in DIMACS format such that each edge $(v,w)$ appears exactly once in the input file and is not repeated as $(w,v)$. In this format, every edge appears in the form of
e W V
where the fields W and V specify the endpoints of the edge while the lower-case character e signifies that this is an edge descriptor line.
Example Solution:
Clique Found 1, 3, 5: Nodes 1, 3, and 5 constitute an optimal solution.
The Algorithm Overview
The find_clique algorithm offers a practical solution by approximating a large clique. It processes each connected component of the graph, using a fast triangle-finding method (from the aegypti package) to identify dense regions. It iteratively selects vertices involved in many triangles, reduces the graph to their neighbors, and builds a clique, returning the largest one found. This approach is efficient and often finds near-optimal cliques in real-world graphs, making it valuable for practical applications. This novel approach guarantees improved efficiency and accuracy over current method:
For details, see:
📖 The Aegypti Algorithm
Compile and Environment
Prerequisites
- Python ≥ 3.12
Installation
pip install gump
Execution
-
Clone the repository:
git clone https://github.com/frankvegadelgado/gump.git cd gump
-
Run the script:
fate -i ./benchmarks/testMatrix1
utilizing the
fatecommand provided by Gump's Library to execute the Boolean adjacency matrixgump\benchmarks\testMatrix1. The filetestMatrix1represents the example described herein. We also support.xz,.lzma,.bz2, and.bzip2compressed text files.Example Output:
testMatrix1: Clique Found 1, 3, 5This indicates nodes
1, 3, 5form a clique.
Clique Size
Use the -c flag to count the nodes in the clique:
fate -i ./benchmarks/testMatrix2 -c
Output:
testMatrix2: Clique Size 4
Command Options
Display help and options:
fate -h
Output:
usage: fate [-h] -i INPUTFILE [-a] [-b] [-c] [-v] [-l] [--version]
Compute the Approximate Clique for undirected graph encoded in DIMACS format.
options:
-h, --help show this help message and exit
-i INPUTFILE, --inputFile INPUTFILE
input file path
-a, --approximation enable comparison with a polynomial-time approximation approach within a polynomial factor
-b, --bruteForce enable comparison with the exponential-time brute-force approach
-c, --count calculate the size of the clique
-v, --verbose anable verbose output
-l, --log enable file logging
--version show program's version number and exit
Batch Execution
Batch execution allows you to solve multiple graphs within a directory consecutively.
To view available command-line options for the batch_fate command, use the following in your terminal or command prompt:
batch_fate -h
This will display the following help information:
usage: batch_fate [-h] -i INPUTDIRECTORY [-a] [-b] [-c] [-v] [-l] [--version]
Compute the Approximate Clique for all undirected graphs encoded in DIMACS format and stored in a directory.
options:
-h, --help show this help message and exit
-i INPUTDIRECTORY, --inputDirectory INPUTDIRECTORY
Input directory path
-a, --approximation enable comparison with a polynomial-time approximation approach within a polynomial factor
-b, --bruteForce enable comparison with the exponential-time brute-force approach
-c, --count calculate the size of the clique
-v, --verbose anable verbose output
-l, --log enable file logging
--version show program's version number and exit
Testing Application
A command-line utility named test_fate is provided for evaluating the Algorithm using randomly generated, large sparse matrices. It supports the following options:
usage: test_fate [-h] -d DIMENSION [-n NUM_TESTS] [-s SPARSITY] [-a] [-b] [-c] [-w] [-v] [-l] [--version]
The Gump Testing Application using randomly generated, large sparse matrices.
options:
-h, --help show this help message and exit
-d DIMENSION, --dimension DIMENSION
an integer specifying the dimensions of the square matrices
-n NUM_TESTS, --num_tests NUM_TESTS
an integer specifying the number of tests to run
-s SPARSITY, --sparsity SPARSITY
sparsity of the matrices (0.0 for dense, close to 1.0 for very sparse)
-a, --approximation enable comparison with a polynomial-time approximation approach within a polynomial factor
-b, --bruteForce enable comparison with the exponential-time brute-force approach
-c, --count calculate the size of the clique
-w, --write write the generated random matrix to a file in the current directory
-v, --verbose anable verbose output
-l, --log enable file logging
--version show program's version number and exit
Code
- Python implementation by Frank Vega.
License
- MIT License.
Metadata
Release files for gump 0.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| gump-0.0.3.tar.gz | 17.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gump-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 35.1 kB
Release files / gump-0.0.3.tar.gz
| Download URL | gump-0.0.3.tar.gz |
|---|---|
| Size | 17.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7e717ca484f59d896f395645ada8954af6ab9ed2e2cf0aa099d912aca5eb8919
|
|
BLAKE2b-256 checksum How to use checksums |
cc5adcc4514dcabe6e2da66e97a7c2b90f7719e4fcdc1c0875317cfe4a9c3510
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 28, 2025.
Transparency logRelease files / gump-0.0.3-py3-none-any.whl
| Download URL | gump-0.0.3-py3-none-any.whl |
|---|---|
| Size | 17.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ba5954a601215c32edac1bbff1d5a5987c288473cacaa292cd4002123ad748c2
|
|
BLAKE2b-256 checksum How to use checksums |
51471130e03a249d3f0173e4924346836342b40f730c89d0d9aca1dfe7868992
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 28, 2025.
Transparency log