<p>Here's how you could come up with tree-width concept yourself.</p>

<p>Suppose you want to count the number of independent sets in the following graph.</p>

<p><a href="https://i.sstatic.net/pG5Yw.png" rel="noreferrer"><img src="https://i.sstatic.net/pG5Yw.png" alt=""></a></p>

<p>Independent sets can be partitioned into ones where top node is occupied, and ones where it is unoccupied</p>

<p><a href="https://i.sstatic.net/b8w5d.png" rel="noreferrer"><img src="https://i.sstatic.net/b8w5d.png" alt=""></a></p>

<p>Now, notice that knowing whether top node is occupied, you can count number of independent sets in each subproblem separately, and multiply them. Repeating this process recursively gives you an algorithm to count independent sets based on graph separators.</p>

<p><a href="https://i.sstatic.net/tlTNO.png" rel="noreferrer"><img src="https://i.sstatic.net/tlTNO.png" alt=""></a></p>

<p>Now, suppose you no longer have a tree. This means separators are bigger, but you can use the same idea. Consider counting independent sets in the following graph.</p>

<p><a href="https://i.sstatic.net/X25y0.png" rel="noreferrer"><img src="https://i.sstatic.net/X25y0.png" alt=""></a></p>

<p>Use the same idea of breaking the problem into subproblems on the separator you get the following</p>

<p><a href="https://i.sstatic.net/qVNCA.png" rel="noreferrer"><img src="https://i.sstatic.net/qVNCA.png" alt=""></a></p>

<p>Like in the previous example, each term in the sum decomposes into two smaller counting tasks across the separator.</p>

<p><a href="https://i.sstatic.net/BXltm.png" rel="noreferrer"><img src="https://i.sstatic.net/BXltm.png" alt=""></a></p>

<p><a href="https://i.sstatic.net/fhBJY.png" rel="noreferrer"><img src="https://i.sstatic.net/fhBJY.png" alt=""></a></p>

<p>Note that we have more terms in the sum than in the previous example because we have to enumerate over all configurations on our separator, which can potentially grow exponentially with size of the separator (size 2 in this case).</p>

<p>Tree decomposition is a data-structure to compactly store these recursive partitioning steps. Consider the following graph and its tree decomposition</p>

<p><a href="https://i.sstatic.net/S1iqR.png" rel="noreferrer"><img src="https://i.sstatic.net/S1iqR.png" alt=""></a></p>

<p><a href="https://i.sstatic.net/3LVX9.png" rel="noreferrer"><img src="https://i.sstatic.net/3LVX9.png" alt=""></a></p>

<p>To count using this decomposition you'd first fix values in nodes 3,6 which breaks it into 2 subproblems. In the first subproblem you'd additionally fix node 5, which breaks its part into two smaller subparts.</p>

<p>Size of the largest separator in an optimal recursive decomposition is precisely the tree width. For larger counting problems, size of the largest separator dominates the runtime, which is why this quantity is so important.</p>

<p>As to the notion of tree-width measuring how close graph is to a tree, one way to make it intuitive is to look at the alternative derivation of tree decomposition -- from correspondence with chordal graphs. First triangulate the graph by traversing vertices in order and interconnecting all "higher ordered" neighbors of each vertex.</p>

<p><a href="https://i.sstatic.net/cAjYt.png" rel="noreferrer"><img src="https://i.sstatic.net/cAjYt.png" alt=""></a></p>

<p>Then construct tree decomposition by taking maximal cliques and connecting them iff their intersection is a maximal separator.</p>

<p><a href="https://i.sstatic.net/lafkF.png" rel="noreferrer"><img src="https://i.sstatic.net/lafkF.png" alt=""></a></p>

<p>Recursive separator and triangulation based approaches of constructing tree decomposition are equivalent. Tree width+1 is the size of the largest clique in optimal triangulation of the graph, or if the graph is already triangulated, just size of the largest clique.</p>

<p>So in a sense, chordal graphs of treewidth tw can be thought of as trees where instead of single nodes we have overlapping cliques of size at most tw+1. Non-chordal graphs are such "clique trees" with some clique edges missing</p>

<p>Here are some chordal graphs and their tree-width. </p>

<p><a href="https://i.sstatic.net/cQ3kC.png" rel="noreferrer"><img src="https://i.sstatic.net/cQ3kC.png" alt=""></a></p>

CC BY-SA 2.5
2011-02-21T00:05:54.480Z
Very nice explanation Yaroslav...Thanks a lot
Akash Kumar
CC BY-SA 2.5
2011-02-21T02:05:13.787Z
A quick question Yaroslav..How did you draw such nice pictures? You made me recollect how inefficient I am at using resources. Did not know you can do stuff this cool on a theory forum :-). Mind sharing how did you do such amazing stuff? Thanks
Akash Kumar
CC BY-SA 2.5
2011-02-21T02:13:01.030Z
I have a collection of Mathematica scripts for generating diagrams like this...to get code for a specific diagram type, find an example of it on http://yaroslavvb.blogspot.com or http://mathematica-bits.blogspot.com/ and follow "Notebook" link on that post
Yaroslav Bulatov
CC BY-SA 2.5
2011-02-24T21:12:36.733Z
This answer is so awesome. wow.
toto
CC BY-SA 4.0
2019-05-06T15:47:30.570Z
is edge 7-10 necessary in the chordal graph?
J. Schmidt
CC BY-SA 4.0
2011-02-20T23:27:32.907Z
2019-01-10T09:44:57.117Z
2019-01-10T09:44:57.117Z
Yaroslav Bulatov
<p>I believe treewidth itself started with the Robertson Seymour paper already given. But some earlier precursors appear to be:</p>

<ul>
<li><p>The concept of a "dimension" of a graph that would control the behavior of dynamic proogramming algorithms on it, from Bertelé, Umberto; Brioschi, Francesco (1972), <em>Nonserial Dynamic Programming</em>.</p></li>
<li><p>The concept of pursuit-evasion games on graphs, from Parsons, T. D. (1976). "Pursuit-evasion in a graph". <em>Theory and Applications of Graphs</em>. Springer-Verlag. pp. 426–441. One variant of this was much later shown to be equivalent to treewidth: Seymour, Paul D.; Thomas, Robin (1993), "Graph searching and a min-max theorem for tree-width", <em>Journal of Combinatorial Theory, Series B</em> 58 (1): 22–33, <a href="http://dx.doi.org/10.1006/jctb.1993.1027">doi:10.1006/jctb.1993.1027</a>.</p></li>
<li><p>Separator hierarchies for planar graphs, starting from Ungar, Peter (1951), "A theorem on planar graphs", Journal of the London Mathematical Society 1 (4): 256, <a href="http://dx.doi.org/10.1112/jlms/s1-26.4.256">doi:10.1112/jlms/s1-26.4.256</a>, and continuing with several papers by Lipton and Tarjan in 1979–1980. The size of the largest separator in a hierarchy of this type is closely related to the treewidth.</p></li>
</ul>

<p>Moving forward to a time when the Robertson–Seymour ideas might have already started to float around, there is also a paper earlier than Graph Minors II that explicitly connects the pursuit-evasion and separation ideas, and that defines a notion of width equivalent to pathwidth: Ellis, J. A.; Sudborough, I. H.; Turner, J. S. (1983), "Graph separation and search number", Proc. 1983 Allerton Conf. on Communication, Control, and Computing.</p>

CC BY-SA 2.5
2011-02-25T21:59:35.840Z
I think that this is not true: apparently Halin discovered the concept some ten years earlier, but that remained largely unnoticed until Robertson and Seymour's rediscovery. See the answer below for details.
Hermann Gruber
CC BY-SA 2.5
2011-02-19T17:13:48.607Z
2011-02-19T18:20:32.647Z
2011-02-19T18:20:32.647Z
David Eppstein
<p>In his monograph on graph theory, Reinhard Diestel traces the concept of treewidth and tree decompositions back to a <strong>1976 paper by Halin</strong> (albeit not using these names). He also attributes to this paper the result that planar grid graphs have unbounded treewidth. Of course, he also mentions the later paper by Robertson and Seymour, who "rediscovered the concept, obviously unaware of Halin's work" (sorry if my translation is poor).</p>

<ul>
<li>Rudolf Halin. $S$-functions for graphs, <em>J. Geometry</em> 8 (1976):171&ndash;186</li>
<li>Reinhard Diestel. <em>Graphentheorie</em>, 3rd German edition, Notizen zu Kapitel 10. (Some English edition of the book is available online for free download.)</li>
</ul>

CC BY-SA 2.5
2011-02-25T23:46:53.303Z
Seems pretty accurate.  From Diestel 3rd (English) edition pp.354–355: "The notions of tree-decomposition and tree-width were ﬁrst introduced (under different names) by R. Halin, S-functions for graphs, J. Geometry 8 (1976), 171–186. Among other things, Halin showed that grids can have arbitrarily large tree-width. Robertson & Seymour reintroduced the two concepts, apparently unaware of Halin’s paper, with direct reference to K. Wagner, Über eine Eigenschaft der ebenen Komplexe, Math. Ann. 114 (1937), 570–590. (This is the seminal paper that introduced simplicial tree-decompositions"
András Salamon
CC BY-SA 3.0
2011-04-10T03:42:21.787Z
Sorry Mr. Gruber for this super-late reaction. I saw your answer long time back, was not sure if I could make other answers accepted after I had accepted one already. Your response is pretty accurate and looks dead on as noted by Mr. Salamon as well
Akash Kumar
CC BY-SA 2.5
2011-02-24T19:48:14.700Z
2011-02-24T19:48:14.700Z
Hermann Gruber
<p>The notion of <em>tree-width</em> [1] (and the similar notion <em>branch-width</em>) has been introduced by Robertson and Seymour in their seminal papers on <strong>Graph Minors</strong>.</p>

<p>They initially introduced <em>tree-width</em> in order to obtain a polynomial-time algorithm testing if a graph $G$ has a subgraph contractible to a fixed planar graph $H$.</p>

<p>See: <a href="http://dx.doi.org/10.1016/0196-6774%2886%2990023-4">N. Robertson, P.D. Seymour. <em>Graph Minors. II. Algorithmic aspects of tree-width</em>. JCT Series B (1986)</a></p>

CC BY-SA 2.5
2011-02-19T17:41:52.167Z
Thanks for bringing up this reference. But I was already aware of this reference (I just knew that it was some paper by Robertson/Seymour -- had never read it). Just was not sure what led Robertson, Seymour to come up with this notion. Thanks for pointing that out. But I was looking for something along the lines of what Prof Eppstein said, so marking that as the accepted answer.
Akash Kumar
CC BY-SA 2.5
2011-02-19T20:34:16.720Z
Ow, no problem! The goal of this site is to get the best answer to a question, and Prof. Eppstein's answer matches far better!
Mathieu Chapelle
CC BY-SA 2.5
2011-02-19T15:55:26.597Z
2011-02-19T15:55:26.597Z
Mathieu Chapelle
<p>If you really want to know what led Neil Robertson and me to tree-width, it wasn't algorithms at all. We were trying to solve Wagner's conjecture that in any infinite set of graphs, one of them is a minor of another, and we were right at the beginning. We knew it was true if we restricted to graphs with no k-vertex path; let me explain why. We knew all such graphs had a simple structure (more exactly, every graph with no k-vertex path has this structure, and every graph with this structure has no 2^k-vertex path); and we knew that in every infinite set of graphs all with this structure, one of them was a minor of another. So Wagner's conjecture was true for graphs with a bound on their maximum path length.</p>

<p>We also knew it was true for graphs with no k-star as a minor, again because we had a structure theorem for such graphs. We tried to look for more general minors that had corresponding structure theorems that we could use to prove Wagner's conjecture, and that led us to path-width; exclude ANY tree as a minor and you get bounded path-width, and if you have bounded path-width then there are trees you can't have as a minor. (That was a hard theorem for us; we had a tremendously hard proof in the first Graph Minors paper, don't read it, it can be made much easier.) But we could prove Wagner's conjecture for graphs with bounded path-width, and that meant it was true for graphs not containing any fixed tree as a minor; a big generalization of the path and star cases I mentioned earlier. </p>

<p>Anyway, with that done we tried to get further. We couldn't do general graphs, so we thought about planar graphs. We found a structure theorem for the planar graphs that did not contain any fixed planar graph as a minor (this was easy);
it was bounded tree-width. We proved that for any fixed planar graph, all the planar graphs that did not contain it as a minor had bounded tree-width. As you can imagine, that was really exciting; by coincidence, the structure theorem for excluding planar graphs (inside bigger planar graphs) was a natural twist on the structure theorem for excluding trees (inside general graphs). We felt we were doing something right. And that let us prove Wagner's conjecture for all planar graphs, because we had this structure theorem. </p>

<p>Since tree-width worked for excluding planar graphs inside bigger planar graphs, it was a natural question whether it worked for excluding planar graphs inside non-planar graphs -- was it true that for every fixed planar graph, all graphs not containing it as a minor had bounded tree-width? This we couldn't prove for a long time, but that's how we got to thinking about tree-width of general graphs. And once we had the concept of tree-width, it was pretty clear that it was good for algorithms. (And yes, we had no idea that Halin had thought about tree-width already.)</p>

CC BY-SA 3.0
2014-11-03T17:48:05.480Z
Welcome to cstheory, and thanks for the great answer !
Suresh Venkat
CC BY-SA 3.0
2014-11-04T15:35:08.687Z
Thanks a lot for taking the time Professor Seymour. This answer is full of reveling insights and covers the historical part that the question originally intended. So marking this as the accepted answer :)
Akash Kumar
CC BY-SA 3.0
2014-11-03T17:28:04.637Z
2014-11-03T17:28:04.637Z
Paul Seymour
<p>My question today is (as usual) a bit silly; but I would request you to kindly consider it.</p>

<p>I wanted to know about the genesis and/or motivation behind the treewidth concept. I sure understand that it is used in FPT algorithms, but I do not think that that was the reason why this notion was defined.</p>

<p>I have written up the <a href="http://people.math.gatech.edu/~thomas/TEACH/7015/0124.pdf">scribe notes</a> on this topic in the class of <a href="http://people.math.gatech.edu/~thomas/">Prof Robin Thomas</a>. I think I understand some of the applications of this concept (as in it transfers separation properties of the tree to the graph decomposed), but for some reason I am not really convinced that the reason this concept was developed was to measure closeness of a graph to a tree.</p>

<p>I will try to make myself more clear (I am not sure if I can, please let me know if the question is not clear). I would like to know if similar notions existed elsewhere in some other branch of mathematics from where this notion was supposedly "borrowed". My guess will be topology -- but owing to my lack of background, I cannot say anything.</p>

<p>The primary reason as to why I am curious about this would be -- the first time I read its definition, I was not sure why and how would anyone conceive of it and to what end. If the question is not still clear I would finally try stating it this way - Let us pretend the notion of treewidth did not exist. What natural questions (or extensions of some mathematical theorems/concepts) to discrete settings will lead one to conceive of a definition (let me use the word involved) as treewidth's. </p>

CC BY-SA 3.0
2013-08-19T16:09:33.273Z
fyi the scribe notes link gets error 403 forbidden.
vzn
<graph-theory><co.combinatorics><big-picture><ho.history-overview><treewidth>
The origin of the notion of treewidth
Akash Kumar
# The origin of the notion of treewidth

(Asked by: username_0 on 2011-02-19)

My question today is (as usual) a bit silly; but I would request you to kindly consider it.

I wanted to know about the genesis and/or motivation behind the treewidth concept. I sure understand that it is used in FPT algorithms, but I do not think that that was the reason why this notion was defined.

I have written up the [scribe notes](http://people.math.gatech.edu/~thomas/TEACH/7015/0124.pdf) on this topic in the class of [Prof Robin Thomas](http://people.math.gatech.edu/~thomas/). I think I understand some of the applications of this concept (as in it transfers separation properties of the tree to the graph decomposed), but for some reason I am not really convinced that the reason this concept was developed was to measure closeness of a graph to a tree.

I will try to make myself more clear (I am not sure if I can, please let me know if the question is not clear). I would like to know if similar notions existed elsewhere in some other branch of mathematics from where this notion was supposedly "borrowed". My guess will be topology -- but owing to my lack of background, I cannot say anything.

The primary reason as to why I am curious about this would be -- the first time I read its definition, I was not sure why and how would anyone conceive of it and to what end. If the question is not still clear I would finally try stating it this way - Let us pretend the notion of treewidth did not exist. What natural questions (or extensions of some mathematical theorems/concepts) to discrete settings will lead one to conceive of a definition (let me use the word involved) as treewidth's.

**Tags:** graph-theory, co.combinatorics, big-picture, ho.history-overview, treewidth
> **Comments:**
> **username_1**: fyi the scribe notes link gets error 403 forbidden.  

---

## 5 answers

### Answer by username_9 on 2014-11-03. Score: 73 | Accepted answer

If you really want to know what led Neil Robertson and me to tree-width, it wasn't algorithms at all. We were trying to solve Wagner's conjecture that in any infinite set of graphs, one of them is a minor of another, and we were right at the beginning. We knew it was true if we restricted to graphs with no k-vertex path; let me explain why. We knew all such graphs had a simple structure (more exactly, every graph with no k-vertex path has this structure, and every graph with this structure has no 2^k-vertex path); and we knew that in every infinite set of graphs all with this structure, one of them was a minor of another. So Wagner's conjecture was true for graphs with a bound on their maximum path length.

We also knew it was true for graphs with no k-star as a minor, again because we had a structure theorem for such graphs. We tried to look for more general minors that had corresponding structure theorems that we could use to prove Wagner's conjecture, and that led us to path-width; exclude ANY tree as a minor and you get bounded path-width, and if you have bounded path-width then there are trees you can't have as a minor. (That was a hard theorem for us; we had a tremendously hard proof in the first Graph Minors paper, don't read it, it can be made much easier.) But we could prove Wagner's conjecture for graphs with bounded path-width, and that meant it was true for graphs not containing any fixed tree as a minor; a big generalization of the path and star cases I mentioned earlier.

Anyway, with that done we tried to get further. We couldn't do general graphs, so we thought about planar graphs. We found a structure theorem for the planar graphs that did not contain any fixed planar graph as a minor (this was easy);
it was bounded tree-width. We proved that for any fixed planar graph, all the planar graphs that did not contain it as a minor had bounded tree-width. As you can imagine, that was really exciting; by coincidence, the structure theorem for excluding planar graphs (inside bigger planar graphs) was a natural twist on the structure theorem for excluding trees (inside general graphs). We felt we were doing something right. And that let us prove Wagner's conjecture for all planar graphs, because we had this structure theorem.

Since tree-width worked for excluding planar graphs inside bigger planar graphs, it was a natural question whether it worked for excluding planar graphs inside non-planar graphs -- was it true that for every fixed planar graph, all graphs not containing it as a minor had bounded tree-width? This we couldn't prove for a long time, but that's how we got to thinking about tree-width of general graphs. And once we had the concept of tree-width, it was pretty clear that it was good for algorithms. (And yes, we had no idea that Halin had thought about tree-width already.)

> **Comments:**
> **username_10**: Welcome to cstheory, and thanks for the great answer !  
> **username_0**: Thanks a lot for taking the time Professor Seymour. This answer is full of reveling insights and covers the historical part that the question originally intended. So marking this as the accepted answer :)  

---

### Answer by username_2 on 2011-02-20. Score: 70

Here's how you could come up with tree-width concept yourself.

Suppose you want to count the number of independent sets in the following graph.

[![](https://i.sstatic.net/pG5Yw.png)](https://i.sstatic.net/pG5Yw.png)

Independent sets can be partitioned into ones where top node is occupied, and ones where it is unoccupied

[![](https://i.sstatic.net/b8w5d.png)](https://i.sstatic.net/b8w5d.png)

Now, notice that knowing whether top node is occupied, you can count number of independent sets in each subproblem separately, and multiply them. Repeating this process recursively gives you an algorithm to count independent sets based on graph separators.

[![](https://i.sstatic.net/tlTNO.png)](https://i.sstatic.net/tlTNO.png)

Now, suppose you no longer have a tree. This means separators are bigger, but you can use the same idea. Consider counting independent sets in the following graph.

[![](https://i.sstatic.net/X25y0.png)](https://i.sstatic.net/X25y0.png)

Use the same idea of breaking the problem into subproblems on the separator you get the following

[![](https://i.sstatic.net/qVNCA.png)](https://i.sstatic.net/qVNCA.png)

Like in the previous example, each term in the sum decomposes into two smaller counting tasks across the separator.

[![](https://i.sstatic.net/BXltm.png)](https://i.sstatic.net/BXltm.png)

[![](https://i.sstatic.net/fhBJY.png)](https://i.sstatic.net/fhBJY.png)

Note that we have more terms in the sum than in the previous example because we have to enumerate over all configurations on our separator, which can potentially grow exponentially with size of the separator (size 2 in this case).

Tree decomposition is a data-structure to compactly store these recursive partitioning steps. Consider the following graph and its tree decomposition

[![](https://i.sstatic.net/S1iqR.png)](https://i.sstatic.net/S1iqR.png)

[![](https://i.sstatic.net/3LVX9.png)](https://i.sstatic.net/3LVX9.png)

To count using this decomposition you'd first fix values in nodes 3,6 which breaks it into 2 subproblems. In the first subproblem you'd additionally fix node 5, which breaks its part into two smaller subparts.

Size of the largest separator in an optimal recursive decomposition is precisely the tree width. For larger counting problems, size of the largest separator dominates the runtime, which is why this quantity is so important.

As to the notion of tree-width measuring how close graph is to a tree, one way to make it intuitive is to look at the alternative derivation of tree decomposition -- from correspondence with chordal graphs. First triangulate the graph by traversing vertices in order and interconnecting all "higher ordered" neighbors of each vertex.

[![](https://i.sstatic.net/cAjYt.png)](https://i.sstatic.net/cAjYt.png)

Then construct tree decomposition by taking maximal cliques and connecting them iff their intersection is a maximal separator.

[![](https://i.sstatic.net/lafkF.png)](https://i.sstatic.net/lafkF.png)

Recursive separator and triangulation based approaches of constructing tree decomposition are equivalent. Tree width+1 is the size of the largest clique in optimal triangulation of the graph, or if the graph is already triangulated, just size of the largest clique.

So in a sense, chordal graphs of treewidth tw can be thought of as trees where instead of single nodes we have overlapping cliques of size at most tw+1. Non-chordal graphs are such "clique trees" with some clique edges missing

Here are some chordal graphs and their tree-width.

[![](https://i.sstatic.net/cQ3kC.png)](https://i.sstatic.net/cQ3kC.png)

> **Comments:**
> **username_0**: Very nice explanation Yaroslav...Thanks a lot  
> **username_0**: A quick question Yaroslav..How did you draw such nice pictures? You made me recollect how inefficient I am at using resources. Did not know you can do stuff this cool on a theory forum :-). Mind sharing how did you do such amazing stuff? Thanks  
> **username_2**: I have a collection of Mathematica scripts for generating diagrams like this...to get code for a specific diagram type, find an example of it on http://yaroslavvb.blogspot.com or http://mathematica-bits.blogspot.com/ and follow "Notebook" link on that post  
> **username_3**: This answer is so awesome. wow.  
> **username_4**: is edge 7-10 necessary in the chordal graph?  

---

### Answer by username_5 on 2011-02-19. Score: 29

I believe treewidth itself started with the Robertson Seymour paper already given. But some earlier precursors appear to be:

* The concept of a "dimension" of a graph that would control the behavior of dynamic proogramming algorithms on it, from Bertelé, Umberto; Brioschi, Francesco (1972), *Nonserial Dynamic Programming*.
* The concept of pursuit-evasion games on graphs, from Parsons, T. D. (1976). "Pursuit-evasion in a graph". *Theory and Applications of Graphs*. Springer-Verlag. pp. 426–441. One variant of this was much later shown to be equivalent to treewidth: Seymour, Paul D.; Thomas, Robin (1993), "Graph searching and a min-max theorem for tree-width", *Journal of Combinatorial Theory, Series B* 58 (1): 22–33, [doi:10.1006/jctb.1993.1027](http://dx.doi.org/10.1006/jctb.1993.1027).
* Separator hierarchies for planar graphs, starting from Ungar, Peter (1951), "A theorem on planar graphs", Journal of the London Mathematical Society 1 (4): 256, [doi:10.1112/jlms/s1-26.4.256](http://dx.doi.org/10.1112/jlms/s1-26.4.256), and continuing with several papers by Lipton and Tarjan in 1979–1980. The size of the largest separator in a hierarchy of this type is closely related to the treewidth.

Moving forward to a time when the Robertson–Seymour ideas might have already started to float around, there is also a paper earlier than Graph Minors II that explicitly connects the pursuit-evasion and separation ideas, and that defines a notion of width equivalent to pathwidth: Ellis, J. A.; Sudborough, I. H.; Turner, J. S. (1983), "Graph separation and search number", Proc. 1983 Allerton Conf. on Communication, Control, and Computing.

> **Comments:**
> **username_6**: I think that this is not true: apparently Halin discovered the concept some ten years earlier, but that remained largely unnoticed until Robertson and Seymour's rediscovery. See the answer below for details.  

---

### Answer by username_6 on 2011-02-24. Score: 23

In his monograph on graph theory, Reinhard Diestel traces the concept of treewidth and tree decompositions back to a **1976 paper by Halin** (albeit not using these names). He also attributes to this paper the result that planar grid graphs have unbounded treewidth. Of course, he also mentions the later paper by Robertson and Seymour, who "rediscovered the concept, obviously unaware of Halin's work" (sorry if my translation is poor).

* Rudolf Halin. $S$-functions for graphs, *J. Geometry* 8 (1976):171–186
* Reinhard Diestel. *Graphentheorie*, 3rd German edition, Notizen zu Kapitel 10. (Some English edition of the book is available online for free download.)

> **Comments:**
> **username_7**: Seems pretty accurate.  From Diestel 3rd (English) edition pp.354–355: "The notions of tree-decomposition and tree-width were ﬁrst introduced (under different names) by R. Halin, S-functions for graphs, J. Geometry 8 (1976), 171–186. Among other things, Halin showed that grids can have arbitrarily large tree-width. Robertson & Seymour reintroduced the two concepts, apparently unaware of Halin’s paper, with direct reference to K. Wagner, Über eine Eigenschaft der ebenen Komplexe, Math. Ann. 114 (1937), 570–590. (This is the seminal paper that introduced simplicial tree-decompositions"  
> **username_0**: Sorry Mr. Gruber for this super-late reaction. I saw your answer long time back, was not sure if I could make other answers accepted after I had accepted one already. Your response is pretty accurate and looks dead on as noted by Mr. Salamon as well  

---

### Answer by username_8 on 2011-02-19. Score: 16

The notion of *tree-width* [1] (and the similar notion *branch-width*) has been introduced by Robertson and Seymour in their seminal papers on **Graph Minors**.

They initially introduced *tree-width* in order to obtain a polynomial-time algorithm testing if a graph $G$ has a subgraph contractible to a fixed planar graph $H$.

See: [N. Robertson, P.D. Seymour. *Graph Minors. II. Algorithmic aspects of tree-width*. JCT Series B (1986)](http://dx.doi.org/10.1016/0196-6774%2886%2990023-4)

> **Comments:**
> **username_0**: Thanks for bringing up this reference. But I was already aware of this reference (I just knew that it was some paper by Robertson/Seymour -- had never read it). Just was not sure what led Robertson, Seymour to come up with this notion. Thanks for pointing that out. But I was looking for something along the lines of what Prof Eppstein said, so marking that as the accepted answer.  
> **username_8**: Ow, no problem! The goal of this site is to get the best answer to a question, and Prof. Eppstein's answer matches far better!  

---

