Aegypti: Triangle-Free Solver
This work builds upon The Aegypti Algorithm.
Triangle-Free Problem
The Triangle-Free problem is a fundamental decision problem in graph theory. Given an undirected graph, the problem asks whether it's possible to determine if the graph contains no triangles (cycles of length 3). In other words, it checks if there exists a configuration where no three vertices are connected by edges that form a closed triangle.
This problem is important for various reasons:
- Graph Analysis: It's a basic building block for more complex graph algorithms and has applications in social network analysis, web graph analysis, and other domains.
- Computational Complexity: It serves as a benchmark problem in the study of efficient algorithms for graph properties. While the naive approach has a time complexity of $O(n^3)$, there are more efficient algorithms with subcubic complexity.
Understanding the Triangle-Free problem is essential for anyone working with graphs and graph algorithms.
Problem Statement
Input: A Boolean Adjacency Matrix $M$.
Question: Does $M$ contain no triangles?
Answer: True / False
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:
Triangle Found (1, 3, 5): In Rows 3 & 5 and Columns 1 & 3
Compile and Environment
Install Python >=3.12.
Install Aegypti's Library and its Dependencies with:
pip install aegypti
Execute
- Go to the package directory to use the benchmarks:
git clone https://github.com/frankvegadelgado/finlay.git
cd finlay
- Execute the script:
triangle -i .\benchmarks\testMatrix1
utilizing the triangle command provided by Aegypti's Library to execute the Boolean adjacency matrix finlay\benchmarks\testMatrix1. The file testMatrix1 represents the example described herein. We also support .xz, .lzma, .bz2, and .bzip2 compressed text files.
The console output will display:
Smart Algorithm for testMatrix1: Triangle Found (1, 3, 5)
which implies that the Boolean adjacency matrix finlay\benchmarks\testMatrix1 contains a triangle combining the nodes (1, 3, 5).
Command Options
To display the help message and available options, run the following command in your terminal:
triangle -h
This will output:
usage: triangle [-h] -i INPUTFILE [-b] [-c] [-v] [-l] [--version]
Solve the Triangle-Free Problem for an undirected graph encoded in DIMACS format.
options:
-h, --help show this help message and exit
-i INPUTFILE, --inputFile INPUTFILE
input file path
-b, --bruteForce compare with a brute-force approach using matrix multiplication
-c, --combinatorial compare with the classical Chiba-Nishizeki O(n + m^{3/2}) adjacency-intersection baseline
-v, --verbose enable verbose output
-l, --log enable file logging
--version show program's version number and exit
This output describes all available options.
Batch Execution
Batch execution allows you to solve multiple graphs within a directory consecutively.
To view available command-line options for the batch_triangle command, use the following in your terminal or command prompt:
batch_triangle -h
This will display the following help information:
usage: batch_triangle [-h] -i INPUTDIRECTORY [-b] [-c] [-v] [-l] [--version]
Solve the Triangle-Free Problem 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
-b, --bruteForce compare with a brute-force approach using matrix multiplication
-c, --combinatorial compare with the classical Chiba-Nishizeki O(n + m^{3/2}) adjacency-intersection baseline
-v, --verbose enable verbose output
-l, --log enable file logging
--version show program's version number and exit
The Finlay Testing Application
A command-line tool, test_triangle, has been developed for testing algorithms on randomly generated, large sparse matrices. It accepts the following options:
usage: test_triangle [-h] -d DIMENSION [-n NUM_TESTS] [-s SPARSITY] [-b] [-c] [-w] [-v] [-l] [--version]
The Finlay 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)
-b, --bruteForce compare with a brute-force approach using matrix multiplication
-c, --combinatorial compare with the classical Chiba-Nishizeki O(n + m^{3/2}) adjacency-intersection baseline
-w, --write write the generated random matrix to a file in the current directory
-v, --verbose enable verbose output
-l, --log enable file logging
--version show program's version number and exit
This tool is designed to benchmark algorithms for sparse matrix operations.
It generates random square matrices with configurable dimensions (-d), sparsity levels (-s), and number of tests (-n). While a comparison with a brute-force matrix multiplication approach is available, it's recommended to avoid this for large datasets due to performance limitations. Additionally, the generated matrix can be written to the current directory (-w), and verbose output or file logging can be enabled with the (-v) or (-l) flag, respectively, to record test results.
Code
- Python code by Frank Vega.
License
- MIT.
Release files for aegypti 0.4.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| aegypti-0.4.7.tar.gz | 15.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aegypti-0.4.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 31.8 kB
Release files / aegypti-0.4.7.tar.gz
| Download URL | aegypti-0.4.7.tar.gz |
|---|---|
| Size | 15.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
be41ff6aa5e773496bb99bd32b4ae798af4b9278a8eb2a2fb63137ba85a6faad
|
|
BLAKE2b-256 checksum How to use checksums |
a1cb516fc7fb7eccba4ca8d5cd072c1d8eb4690b73e39851b089d2202e6871bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 27, 2026.
Transparency logRelease files / aegypti-0.4.7-py3-none-any.whl
| Download URL | aegypti-0.4.7-py3-none-any.whl |
|---|---|
| Size | 16.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e798ff4bb1fc2bbe5bf059ccc8445b6418366503898b0a1c1ae6c5cf97850f5a
|
|
BLAKE2b-256 checksum How to use checksums |
0bfe27d2616ab01f5a27a67cf48bf5ebbee08b8663592827553d0d07b9b5049c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 27, 2026.
Transparency log