This document contains links to solvers, instance sets, and tools for treewidth computation. It is a collection of products of the treewidth implementation challenges at The Parameterized Algorithms and Computational Experiments Challenge PACE 2017 and PACE 2016.

• Problem description
• List of Treewidth Solvers
• List of Treewidth Instance Sets
• Validity checker
• Input format
• Output format
• Mirrors

The objective is to compute a tree-decomposition of minimum width.

• Input: An undirected graph.
• Output: A minimum-width tree-decomposition of the graph.

The theory and complexity of treewidth has been intensely study in graph minor theory and fixed-parameter tractability (FPT). Given a graph G and an integer k, it is NP-complete to determine whether the treewidth of G is at most k, but there is an n^(k 2)-time algorithm (Arnborg, Corneil, and Proskurowski 1987). The problem can also be solved in FPT-time exp(k^3) n (Bodlaender 1996), and a factor-5 approximation can be obtained in time exp(k) n (Bodlaender, Drange, Dregi, Fomin, Lokshtanov, and Pilipczuk 2013). It is unknown whether the problem has a polynomial-time approximation scheme (PTAS).

Treewidth implementations are used in various contexts. For example, compilers allocate registers by computing proper colorings on control flow graphs, which turn out to have small treewidth in practice (e.g., Thorup 1998). Data structures for shortest path queries can use tree decompositions in a preprocessing phase (e.g., Chatterjee, Ibsen-Jensen, and Pavlogiannis 2016). Graph theory can be guided by treewidth implementations when attempting to rigorously determine the treewidth of specific graph families (e.g., Kiyomi, Okamoto, and Otachi 2015). Finally, many problems in probabilistic inference use tree decompositions in a preprocessing phase (e.g., Otten, Ihler, Kask, and Dechter 2011).

• twalgor by Hiaso Tamaki (2022)
• tamaki-2017 by Hisao Tamaki, Hiromu Ohtsuka, Takuto Sato, and Keitaro Makii
• tdlib by Lukas Larisch and Felix Salfelder
• Jdrasil by Max Bannach, Sebastian Berndt, and Thorsten Ehlers
• tamaki-2016 by Hisao Tamaki

• Flow-Cutter by Ben Strasser
• htd by Michael Abseher, Nysret Musliu, and Stefan Woltran
• tamaki-2017 by Tamaki, Hiromu Ohtsuka, Takuto Sato, and Keitaro Makii
• Jdrasil by Max Bannach, Sebastian Berndt, and Thorsten Ehlers
• Minfill_mrs and Minfillbg_mrs by Philippe Jégou, Hanan Kanso, and Cyril Terrioux
• tdlib by Lukas Larisch and Felix Salfelder

• PACE 2017 bonus instances – this should be a fresh challenge even for the PACE 2017 winning solvers
• PACE 2017 competition instances
• Named graphs contributed by Lukas Larisch
• Control flow graphs contributed by Lukas Larisch

• PACE 2017 competition instances
• UAI 2014 probabilistic inference competition graphs
• SAT competition graphs
• Transit graphs contributed by Johannes Fichte
• Road graphs contributed by Ben Strasser
• treedecomposition.com (now defunct)

The validity checker td-validate verifies that a given tree decomposition (specified in the .td file format) is indeed a valid tree decomposition of a given graph (specified in the .gr format).

The validity checker also comes with an automatic tester autotest-tw-solver.py that can automatically test a given exact treewidth solver by running it on all graphs with min-degree 3 and at most 8 vertices.

We describe the file format .gr, which is similar to the format used by DIMACS challenges.

Lines are separated by the character ‘\n’. Each line that starts with the character c is considered to be a comment line. The first non-comment line must be a line starting with p followed by the problem descriptor tw and the number of vertices n and edges m (separated by a single space each time). No other line may start with p. Every other line indicates an edge, and must consist of two decimal integers from 1 to n separated by a space; moreover, graphs are considered undirected (though they may contain isolated vertices, multiple edges, and loops). For example, a path with four edges can be defined as follows:

c This file describes a path with five vertices and four edges.
p tw 5 4
1 2
2 3
c we are half-way done with the instance definition.
3 4
4 5

Recall the definition of a tree decomposition of a graph G: It is a tree T such that every vertex x in V(T) has an associated bag B(x) that is a subset of V(G). Every edge e in E(G) must be a subset of at least one bag B(x). Moreover, for every vertex v in V(G), the set of tree vertices whose bags contain v induce a connected subtree of T. The width of T is the maximum size of its bags minus one. The goal is to compute a tree decomposition of minimum width.

We define the file format .td. As above, c lines are comments and can occur throughout the file. Instead of a p-line, we now expect a unique solution line s as the first non-comment line, which contains the string td, followed by the number N of bags of the tree decomposition, the width of the tree decomposition plus one (i.e., the largest bag size), as well as the number of vertices of the original input graph. The next non-comment lines we expect start with b and specify the contents of each bag; for example, b 4 3 4 6 7 specifies that bag number 4 contains the vertices 3, 4, 6, and 7 of the original graph. Bags may be empty. For every bag i, there must be exactly one line starting with b i. All remaining non-comment lines indicate an edge in the tree decomposition, so it must consist of two decimal integers from 1 and N where the first integer is smaller than the second, and the graph described this way must be a tree. For example, the following is a suboptimal tree decomposition of the path with four edges.

c This file describes a tree decomposition with 4 bags, width 2, for a graph with 5 vertices
s td 4 3 5
b 1 1 2 3
b 2 2 3 4
b 3 3 4 5
b 4
1 2
2 3
2 4