# Kernelization

In computer science, a **kernelization** is a technique for designing efficient algorithms that achieve their efficiency by a preprocessing stage in which inputs to the algorithm are replaced by a smaller input, called a "kernel". The result of solving the problem on the kernel should either be the same as on the original input, or it should be easy to transform the output on the kernel to the desired output for the original problem.

Kernelization is often achieved by applying a set of reduction rules that cut away parts of the instance that are easy to handle. In parameterized complexity theory, it is often possible to prove that a kernel with guaranteed bounds on the size of a kernel (as a function of some parameter associated to the problem) can be found in polynomial time. When this is possible, it results in a fixed-parameter tractable algorithm whose running time is the sum of the (polynomial time) kernelization step and the (non-polynomial but bounded by the parameter) time to solve the kernel. Indeed, every problem that can be solved by a fixed-parameter tractable algorithm can be solved by a kernelization algorithm of this type.

## Example: vertex cover

A standard example for a kernelization algorithm is the kernelization of the vertex cover problem by S. Buss.^{[1]}
In this problem, the input is an undirected graph together with a number . The output is a set of at most vertices that includes the endpoint of every edge in the graph, if such a set exists, or a failure exception if no such set exists. This problem is NP-hard. However, the following reduction rules may be used to kernelize it:

- If and is a vertex of degree greater than , remove from the graph and decrease by one. Every vertex cover of size must contain since otherwise too many of its neighbors would have to be picked to cover the incident edges. Thus, an optimal vertex cover for the original graph may be formed from a cover of the reduced problem by adding back to the cover.
- If is an isolated vertex, remove it. An isolated vertex cannot cover any edges, so in this case cannot be part of any minimal cover.
- If more than edges remain in the graph, and neither of the previous two rules can be applied, then the graph cannot contain a vertex cover of size . For, after eliminating all vertices of degree greater than , each remaining vertex can only cover at most edges and a set of vertices could only cover at most edges. In this case, the instance may be replaced by an instance with two vertices, one edge, and , which also has no solution.

An algorithm that applies these rules repeatedly until no more reductions can be made necessarily terminates with a kernel that has at most edges and (because each edge has at most two endpoints and there are no isolated vertices) at most vertices. This kernelization may be implemented in linear time. Once the kernel has been constructed, the vertex cover problem may be solved by a brute force search algorithm that tests whether each subset of the kernel is a cover of the kernel. Thus, the vertex cover problem can be solved in time for a graph with vertices and edges, allowing it to be solved efficiently when is small even if and are both large.

Although this bound is fixed-parameter tractable, its dependence on the parameter is higher than might be desired. More complex kernelization procedures can improve this bound, by finding smaller kernels, at the expense of greater running time in the kernelization step. In the vertex cover example, kernelization algorithms are known that produce kernels with at most vertices.
One algorithm that achieves this improved bound exploits the half-integrality of the linear program relaxation of vertex cover due to Nemhauser and Trotter.^{[2]} Another kernelization algorithm achieving that bound is based on what is known as the crown reduction rule and uses alternating path arguments.^{[3]} The currently best known kernelization algorithm in terms of the number of vertices is due to Template:Harvtxt and achieves vertices for any fixed constant .

It is not possible, in this problem, to find a kernel of size , unless P = NP, for such a kernel would lead to a polynomial-time algorithm for the NP-hard vertex cover problem. However, much stronger bounds on the kernel size can be proven in this case: unless coNP NP/poly (believed unlikely by complexity theorists), for every it is impossible in polynomial time to find kernels with edges.^{[4]}
It is unknown for vertex cover whether kernels with vertices for some would have any unlikely complexity-theoretic consequences.

## Definition

In the literature, there is no clear consensus on how kernelization should be formally defined and there are subtle differences in the uses of that expression.

### Downey-Fellows Notation

In the Notation of Template:Harvtxt, a *parameterized problem* is a subset describing a decision problem.

A **kernelization** for a parameterized problem is an algorithm that takes an instance and maps it in time polynomial in and to an instance such that

- is in if and only if is in ,
- the size of is bounded by a computable function in , and
- is bounded by a function in .

The output of kernelization is called a kernel. In this general context, the *size* of the string just refers to its length.
Some authors prefer to use the number of vertices or the number of edges as the size measure in the context of graph problems.

### Flum-Grohe Notation

In the Notation of Template:Harvtxt, a *parameterized problem* consists of a decision problem and a function , the parameterization. The *parameter* of an instance is the number .

A **kernelization** for a parameterized problem is an algorithm that takes an instance with parameter and maps it in polynomial time to an instance such that

Note that in this notation, the bound on the size of implies that the parameter of is also bounded by a function in .

The function is often referred to as the size of the kernel. If , it is said that admits a polynomial kernel. Similarly, for , the problem admits linear kernel.

## Kernelizability and fixed-parameter tractability are equivalent

A problem is fixed-parameter tractable if and only if it is kernelizable and decidable.

That a kernelizable and decidable problem is fixed-parameter tractable can be seen from the definition above: First the kernelization algorithm, which runs in time for some c, is invoked to generate a kernel of size . The kernel is then solved by the algorithm that proves that the problem is decidable. The total running time of this procedure is , where is the running time for the algorithm used to solve the kernels. Since is computable, e.g. by using the assumption that is computable and testing all possible inputs of length , this implies that the problem is fixed-parameter tractable.

The other direction, that a fixed-parameter tractable problem is kernelizable and decidable is a bit more involved. Assume that the question is non-trivial, meaning that there is at least one instance that is in the language, called , and at least one instance that is not in the language, called ; otherwise, replacing any instance by the empty string is a valid kernelization. Assume also that the problem is fixed-parameter tractable, ie., it has an algorithm that runs in at most steps on instances , for some constant and some function . To kernelize an input, run this algorithm on the given input for at most steps. If it terminates with an answer, use that answer to select either or as the kernel. If, instead, it exceeds the bound on the number of steps without terminating, then return itself as the kernel. Because is only returned as a kernel for inputs with , it follows that the size of the kernel produced in this way is at most . This size bound is computable, by the assumption from fixed-parameter tractability that is computable.

## More Examples

**Vertex Cover:**The vertex cover problem has kernels with at most vertices and edges.^{[5]}Furthermore, for any , vertex cover does not have kernels with edges unless .^{[4]}The vertex cover problems in -uniform hypergraphs has kernels with edges using the sunflower lemma, and it does not have kernels of size unless .^{[4]}**Feedback Vertex Set:**The feedback vertex set problem has kernels with vertices and edges.^{[6]}Furthermore, it does not have kernels with edges unless .^{[4]}**k-Path:**The k-path problem is to decide whether a given graph has a path of length at least . This problem has kernels of size exponential in , and it does not have kernels of size polynomial in unless .^{[7]}**Bidimensional problems:**Many parameterized versions of bidimensional problems have linear kernels on planar graphs, and more generally, on graphs excluding some fixed graph as a minor.^{[8]}

## Notes

- ↑ This unpublished observation is acknowledged in a paper of Template:Harvtxt
- ↑ Template:Harvtxt
- ↑ Template:Harvtxt give a kernel based on the crown reduction that has vertices. The vertex bound is a bit more involved and folklore.
- ↑
^{4.0}^{4.1}^{4.2}^{4.3}Template:Harvtxt - ↑ Template:Harvtxt
- ↑ Template:Harvtxt
- ↑ Template:Harvtxt
- ↑ Template:Harvtxt

## References

- {{#invoke:citation/CS1|citation

|CitationClass=citation }}.

- {{#invoke:citation/CS1|citation

|CitationClass=citation }}.

- {{#invoke:citation/CS1|citation

|CitationClass=citation }}.

- {{#invoke:citation/CS1|citation

|CitationClass=citation }}.

- {{#invoke:citation/CS1|citation

|CitationClass=citation }}.

- {{#invoke:citation/CS1|citation

|CitationClass=citation }}.

- {{#invoke:citation/CS1|citation

|CitationClass=citation }}.

- {{#invoke:citation/CS1|citation

|CitationClass=citation }}.

- {{#invoke:citation/CS1|citation

|CitationClass=citation }}.

- {{#invoke:citation/CS1|citation

|CitationClass=citation }}.

- {{#invoke:citation/CS1|citation

|CitationClass=citation }}.