Reductions¶
A Reduction is a transformation
from one problem to an equivalent problem. Two problems are equivalent
if a solution of one can be converted to a solution of the other with no
more than a moderate amount of effort. CVXPY uses reductions to rewrite
problems into forms that solvers will accept.
Disclaimer¶
The majority of users do not need to know anything about CVXPY’s reduction system. Indeed, most users need not even know that reductions exist!
In order to make sure that we have flexibility to improve CVXPY’s speed and capabilities while preserving backwards-compatibility, we have determined that the reduction system will not be considered part of CVXPY’s public API. As such, aspects of this system can change without notice in future releases.
We provide this documentation for CVXPY contributors, for the curious, and for those who are okay with building on an API that may not be available in future versions of CVXPY. Please contact us if you have an interesting application which requires direct access to the Reduction system and if you care about forward compatibility with future versions of CVXPY.
Types of Reductions¶
Reductions allow CVXPY to support different problem classes such as convex and log-log convex programming. They also help CVXPY target different categories of solvers, such as quadratic programming solvers and conic solvers.
Appropriating terminology from software compilers, we classify reductions as either middle-end reductions or back-end reductions. A reduction that simplifies a source problem without regard to the targeted solver is called a middle-end reduction, whereas a reduction that takes a source problem and converts it to a form acceptable to a category of solvers is called a back-end reduction. Each solver (along with the mode in which it is invoked) is called a back-end or target.
Here’s a breakdown of CVXPY’s reductions:
Core classes¶
Reductions exchange data and operate by way of the following classes. Other data structures can be used, such as dicts keyed by strings, but these are the main classes which define the Reduction system.
Solution¶
- class cvxpy.reductions.solution.Solution(status, opt_val, primal_vars, dual_vars, attr)[source]¶
A solution to an optimization problem.
Reduction¶
-
class cvxpy.reductions.reduction.Reduction(problem=
None)[source]¶ Abstract base class for reductions.
A reduction is an actor that transforms a problem into an equivalent problem. By equivalent we mean that there exists a mapping between solutions of either problem: if we reduce a problem \(A\) to another problem \(B\) and then proceed to find a solution to \(B\), we can convert it to a solution of \(A\) with at most a moderate amount of effort.
A reduction that is instantiated with a non-None problem offers two key methods: reduce and retrieve. The reduce() method converts the problem the reduction was instantiated with to an equivalent problem. The retrieve() method takes as an argument a Solution for the equivalent problem and returns a Solution for the problem owned by the reduction.
Every reduction offers three low-level methods: accepts, apply, and invert. The accepts method of a particular reduction specifies the types of problems that it is applicable to; the apply method takes a problem and reduces it to an equivalent form, and the invert method maps solutions from reduced-to problems to their problems of provenance.
-
__init__(problem=
None)[source]¶ Construct a reduction for reducing problem.
If problem is not None, then a subsequent invocation of reduce() will reduce problem and return an equivalent one.
- abstractmethod apply(problem)[source]¶
Applies the reduction to a problem and returns an equivalent problem.
- abstractmethod invert(solution, inverse_data)[source]¶
Returns a solution to the original problem given the inverse_data.
-
__init__(problem=
Chain¶
-
class cvxpy.reductions.chain.Chain(problem=
None, reductions=None)[source]¶ Bases:
ReductionA logical grouping of multiple reductions into a single reduction.
- accepts(problem) bool[source]¶
A problem is accepted if the sequence of reductions is valid.
In particular, the i-th reduction must accept the output of the i-1th reduction, with the first reduction (self.reductions[0]) in the sequence taking as input the supplied problem.
-
apply(problem, verbose: bool =
False)[source]¶ Applies the chain to a problem and returns an equivalent problem.
- invert(solution, inverse_data)[source]¶
Returns a solution to the original problem given the inverse_data.
SolvingChain¶
-
class cvxpy.reductions.solvers.solving_chain.SolvingChain(problem=
None, reductions=None)[source]¶ Bases:
ChainA reduction chain that ends with a solver.
- Parameters:¶
- prepend(chain) SolvingChain[source]¶
Create and return a new SolvingChain by concatenating chain with this instance.
- solve(problem, warm_start: bool, verbose: bool, solver_opts)[source]¶
Solves the problem by applying the chain.
Applies each reduction in the chain to the problem, solves it, and then inverts the chain to return a solution of the supplied problem.
-
solve_via_data(problem, data, warm_start: bool =
False, verbose: bool =False, solver_opts={})[source]¶ Solves the problem using the data output by the an apply invocation.
The semantics are:
data, inverse_data = solving_chain.apply(problem) solution = solving_chain.invert(solver_chain.solve_via_data(data, ...))which is equivalent to writing
solution = solving_chain.solve(problem, ...)