Apex graph

In graph theory, a branch of mathematics, an apex graph is a graph that can be made planar by the removal of a single vertex. The deleted vertex is called an apex of the graph. It is an apex, not the apex because an apex graph may have more than one apex; for example, in the minimal nonplanar graphs Template:Math or Template:Math, every vertex is an apex. The apex graphs include graphs that are themselves planar, in which case again every vertex is an apex. The null graph is also counted as an apex graph even though it has no vertex to remove.
Apex graphs are closed under the operation of taking minors and play a role in several other aspects of graph minor theory: linkless embedding,[1] Hadwiger's conjecture,[2] YΔY-reducible graphs,[3] and relations between treewidth and graph diameter.[4]
Characterization and recognition
Apex graphs are closed under the operation of taking minors: contracting any edge, or removing any edge or vertex, leads to another apex graph. For, if Template:Mvar is an apex graph with apex Template:Mvar, then any contraction or removal that does not involve Template:Mvar preserves the planarity of the remaining graph, as does any edge removal of an edge incident to Template:Mvar. If an edge incident to Template:Mvar is contracted, the effect on the remaining graph is equivalent to the removal of the other endpoint of the edge. And if Template:Mvar itself is removed, any other vertex may be chosen as the apex.[5]
By the Robertson–Seymour theorem, because they form a minor-closed family of graphs, the apex graphs have a forbidden graph characterization. There are only finitely many graphs that are neither apex graphs nor have another non-apex graph as a minor. These graphs are forbidden minors for the property of being an apex graph. Any other graph Template:Mvar is an apex graph if and only if none of the forbidden minors is a minor of Template:Mvar. These forbidden minors include the seven graphs of the Petersen family, three disconnected graphs formed from the disjoint unions of two of Template:Math and Template:Math, and many other graphs. However, a complete description of them remains unknown.[5]Template:Sfnp
Despite the complete set of forbidden minors remaining unknown, it is possible to test whether a given graph is an apex graph, and if so, to find an apex for the graph, in linear time. More generally, for any fixed constant Template:Mvar, it is possible to recognize in linear time the Template:Mvar-apex graphs, the graphs in which the removal of some carefully chosen set of at most Template:Mvar vertices leads to a planar graph.[6] If Template:Mvar is variable, however, the problem is NP-complete.[7]
Chromatic number
Every apex graph has chromatic number at most five: the underlying planar graph requires at most four colors by the four color theorem, and the remaining vertex needs at most one additional color. Template:Harvtxt used this fact in their proof of the case Template:Math of the Hadwiger conjecture, the statement that every 6-chromatic graph has the complete graph Template:Math as a minor: they showed that any minimal counterexample to the conjecture would have to be an apex graph, but since there are no 6-chromatic apex graphs such a counterexample cannot exist.
Template:Unsolved Template:Harvtxt conjectured that every 6-vertex-connected graph that does not have Template:Math as a minor must be an apex graph. If this were proved, the Robertson–Seymour–Thomas result on the Hadwiger conjecture would be an immediate consequence.[2] Jørgensen's conjecture remains unproven.[8] However, if false, it has only finitely many counterexamples.Template:Sfnp
Local treewidth
A graph family Template:Mvar has bounded local treewidth if the graphs in Template:Mvar obey a functional relationship between diameter and treewidth: there exists a function Template:Mvar such that the treewidth of a diameter-Template:Mvar graph in Template:Mvar is at most Template:Math. The apex graphs do not have bounded local treewidth: the apex graphs formed by connecting an apex vertex to every vertex of an Template:Math grid graph have treewidth Template:Mvar and diameter 2, so the treewidth is not bounded by a function of diameter for these graphs. However, apex graphs are intimately connected to bounded local treewidth: the minor-closed graph families Template:Mvar that have bounded local treewidth are exactly the families that have an apex graph as one of their forbidden minors.[4] A minor-closed family of graphs that has an apex graph as one of its forbidden minors is known as apex-minor-free. With this terminology, the connection between apex graphs and local treewidth can be restated as the fact that apex-minor-free graph families are the same as minor-closed graph families with bounded local treewidth.
The concept of bounded local treewidth forms the basis of the theory of bidimensionality, and allows for many algorithmic problems on apex-minor-free graphs to be solved exactly by a polynomial-time algorithm or a fixed-parameter tractable algorithm, or approximated using a polynomial-time approximation scheme.[9] Apex-minor-free graph families obey a strengthened version of the graph structure theorem, leading to additional approximation algorithms for graph coloring and the travelling salesman problem.[10] However, some of these results can also be extended to arbitrary minor-closed graph families via structure theorems relating them to apex-minor-free graphs.[11]
Embeddings
If Template:Mvar is an apex graph with apex Template:Mvar, and Template:Math is the minimum number of faces needed to cover all the neighbors of Template:Mvar in a planar embedding of Template:Math then Template:Mvar may be embedded onto a two-dimensional surface of genus Template:Math: simply add that number of bridges to the planar embedding, connecting together all the faces into which Template:Mvar must be connected. For instance, adding a single vertex to an outerplanar graph (a graph with Template:Math) produces a planar graph. When Template:Math is 3-connected, his bound is within a constant factor of optimal: every surface embedding of Template:Mvar requires genus at least Template:Math. However, it is NP-hard to determine the optimal genus of a surface embedding of an apex graph.[12]
By using SPQR trees to encode the possible embeddings of the planar part of an apex graph, it is possible to compute a drawing of the graph in the plane in which the only crossings involve the apex vertex, minimizing the total number of crossings, in polynomial time.[13] However, if arbitrary crossings are allowed, it becomes NP-hard to minimize the number of crossings, even in the special case of apex graphs formed by adding a single edge to a planar graph.[14]
Apex graphs are also linklessly embeddable in three-dimensional space: they can be embedded in such a way that each cycle in the graph is the boundary of a disk that is not crossed by any other feature of the graph.[15] A drawing of this type may be obtained by drawing the planar part of the graph in a plane, placing the apex above the plane, and connecting the apex by straight-line edges to each of its neighbors. Linklessly embeddable graphs form a minor-closed family with the seven graphs in the Petersen family as their minimal forbidden minors;[1] therefore, these graphs are also forbidden as minors for the apex graphs. However, there exist linklessly embeddable graphs that are not apex graphs.
YΔY-reducibility

A connected graph is YΔY-reducible if it can be reduced to a single vertex by a sequence of steps, each of which is a Δ-Y or Y-Δ transform, the removal of a self-loop or multiple adjacency, the removal of a vertex with one neighbor, and the replacement of a vertex of degree two and its two neighboring edges by a single edge.[3]
Like the apex graphs and the linkless embeddable graphs, the YΔY-reducible graphs are closed under graph minors. And, like the linkless embeddable graphs, the YΔY-reducible graphs have the seven graphs in the Petersen family as forbidden minors, prompting the question of whether these are the only forbidden minors and whether the YΔY-reducible graphs are the same as the linkless embeddable graphs. However, Neil Robertson provided an example of an apex graph that is not YΔY-reducible. Since every apex graph is linkless embeddable, this shows that there are graphs that are linkless embeddable but not YΔY-reducible and therefore that there are additional forbidden minors for the YΔY-reducible graphs.[3]
Robertson's apex graph is shown in the figure. It can be obtained by connecting an apex vertex to each of the degree-three vertices of a rhombic dodecahedron, or by merging two diametrally opposed vertices of a four-dimensional hypercube graph. Because the rhombic dodecahedron's graph is planar, Robertson's graph is an apex graph. It is a triangle-free graph with minimum degree four, so it cannot be changed by any YΔY-reduction.[3]
Nearly planar graphs

If a graph is an apex graph, it is not necessarily the case that it has a unique apex. For instance, in the minor-minimal nonplanar graphs K5 and K3,3, any of the vertices can be chosen as the apex. Template:Harvs defined a nearly planar graph to be a nonplanar apex graph with the property that all vertices can be the apex of the graph; thus, K5 and K3,3 are nearly planar. He provided a classification of these graphs into four subsets, one of which consists of the graphs that (like the Möbius ladders) can be embedded onto the Möbius strip in such a way that the single edge of the strip coincides with a Hamiltonian cycle of the graph. Prior to the proof of the four color theorem, he proved that every nearly planar graph can be colored with at most four colors, except for the graphs formed from a wheel graph with an odd outer cycle by replacing the hub vertex with two adjacent vertices, which require five colors. Additionally, he proved that, with a single exception (the eight-vertex complement graph of the cube) every nearly planar graph has an embedding onto the projective plane.
However, the phrase "nearly planar graph" is highly ambiguous: it has also been used to refer to apex graphs,[16] graphs formed by adding one edge to a planar graph,[17] and graphs formed from a planar embedded graph by replacing a bounded number of faces by "vortexes" of bounded pathwidth,[18] as well as for other less precisely-defined sets of graphs.
Related graph classes
An abstract graph is said to be n-apex if it can be made planar by deleting n or fewer vertices. A 1-apex graph is also said to be apex.
According to Template:Harvtxt, a graph is edge-apex if there is some edge in the graph that can be deleted to make the graph planar. A graph is contraction-apex if there is some edge in the graph that can be contracted to make the graph planar.
In general, if X is a class of graphs, an "apex-X" graph is a graph that can be brought into the class X by deleting some one vertex. For example, an apex-cograph is a graph G that has a vertex v such that G―v is a cograph.
See also
- Polyhedral pyramid, a 4-dimensional polytope whose vertices and edges form an apex graph, with the apex adjacent to every vertex of a polyhedral graph
Notes
References
- Template:Citation.
- Template:Citation.
- Template:Citation.
- Template:Citation.
- Template:Citation.
- Template:Citation.
- Template:Citation.
- Template:Citation.
- Template:Citation.
- Template:Citation.
- Template:Citation.
- Template:Citation. As cited by Template:Harvs.
- Template:Citation.
- Template:Citation.
- Template:Citation.
- Template:Citation.
- Template:Citation.
- Template:Citation.
- Template:Citation.
- Template:Citation.
- Template:Citation.
- Template:Citation.
- Template:Citation.
- Template:Citation.
- ↑ 1.0 1.1 Template:Harvtxt.
- ↑ 2.0 2.1 Template:Harvtxt.
- ↑ 3.0 3.1 3.2 3.3 Template:Harvtxt.
- ↑ 4.0 4.1 Template:Harvtxt; Template:Harvtxt.
- ↑ 5.0 5.1 Template:Harvtxt.
- ↑ Template:Harvtxt.
- ↑ Template:Harvtxt.
- ↑ Template:Citation.
- ↑ Template:Harvtxt; Template:Harvtxt; Template:Harvtxt.
- ↑ Template:Harvtxt.
- ↑ Template:Harvtxt.
- ↑ Template:Harvtxt.
- ↑ Template:Harvtxt.
- ↑ Template:Harvtxt.
- ↑ Template:Harvtxt.
- ↑ Template:Harvtxt; Template:Harvtxt.
- ↑ Template:Harvtxt.
- ↑ Template:Harvtxt.