IbexSolve¶
This documentation is for using IbexSolve with the command prompt.
To use IbexSolve in C++ or program your own solver with Ibex, see the programmer guide.
Getting started¶
The very basic idea¶
IbexSolve solves systems of equation in a complete and validated way.
If you have an equation, say,
and you ask a traditional numerical algorithm to solve it, you will get an answer like:
or maybe something close to the other root 1. But you will not get both roots and you will not know exactly how far the returned value is from the actual root.
IbexSolve will give you the following answer:
First, all solutions are returned: this is what we mean by completeness.
Second, each actual solution is rigorously enclosed in an interval: this is what validation means.
First example (wellconstrained)¶
Open a terminal (move to the bin
subfolder if necessary) and run IbexSolve with, for example, the problem named Kin1.bch located at the specified path:
ibexsolve [ibexlibpath]/benchs/solver/nonpolynom/Kin1.bch
After a short delay, the following result should be displayed:
solving successful!
number of solution boxes: 16
number of boundary boxes: 
number of unknown boxes: 
number of pending boxes: 
cpu time used: 0.122523s
number of cells: 47
You see that IbexSolve has found 16 solutions. To obtain the solutions, just run the same command with the option s
. You will have each solution
displayed as a list of thin intervals enclosing the components of the true solution:
solution n°1 = ([0.3999964622870867, 0.3999964622870879] ; [0.819005889921108, 0.8190058899211153] ; ...)
Also are reported here the CPU time (around a tenth of second in this case) and the number of “cells” required. This number basically corresponds to the total number of hypothesis (bisections) that was required to solve the problem. It gives an indication of its complexity.
The file Kin1.bch is a plain text file, you can open it with any editor. You will see that it is a problem with 6 variables and 6 nonlinear constraints, with sine and cosine operators. The file is written in the Minibex syntax.
Second example (underconstrained)¶
One important originality of IbexSolve (compared to the other interval tools) is that it is not limited to square (wellconstrained) systems as in the previous example.
Open your editor and type the following text in a circle.mbx file:
variables
x,y;
constraints
x^2+y^2=1;
end
The solution set in this case is a full curve in the plane, the unit circle.
Then run IbexSolve to solve it:
ibexsolve circle.mbx
You may expect to obtain a bunch of boxes in return enclosing the curve, like in the picture below (we have superimposed the circle (in red) for clarity):
IbexSolve can calculate that. But this means that you expect a fine description of the curve and that you accept to pay the inevitable price of a voluminous output (especially in higher dimension).
A different and opposite strategy would be to expect in return a single box enclosing the curve, that is, the square [0,1]x[0,1]. You would then have a minimal output but a very coarse description of the curve.
The default behavior of IbexSolve is somehow a best compromise between these two extreme strategies. It tries to return a minimal number of boxes while capturing the “topology” of the solution set.
In the circle example, IbexSolve will just produce 11 solutions. They are depicted below:
As you can seen, the paving with the boxes is a rough description of the circle. Still, we see that the overall shape is captured. This paving clearly looks differently than if we had solve, say, a linear equation.
In more precise terms, each solution box has the property to be crossed by the curve in a regular way. Look for instance at the gray box. The curve makes no loop or uturn whatsoever inside the box and crosses it from side to side along the yaxis.
Formally, it is proven for this box that for all values y in [y] there exists x in [x], and a single one, such that (x,y) is a point of the curve. More exactly, we have:
where \(\mathring{\cdot}\) stands for the interior of.
All the 11 boxes have this property except that the roles of x and y can be switched, depending whether the box is more horizontal or vertical. This information is given in the output data.
Of course, all this generalizes to any dimension.
If you need to refine the paving, that is, to have boxes of smaller size, use for this the epsmax parameter.
For instance, if we run IbexSolve using E 0.5
(or equivalently, epsmax=0.5
) we obtain the following paving:
Third example (inequalities)¶
Let us now turn to a single inequality. Just change the “=” sign of the previous example by “<=”:
variables
x,y;
constraints
x^2+y^2<=1;
end
Now the result is:
number of solution boxes: 11629
number of boundary boxes: 
number of unknown boxes: 8941
number of pending boxes: 
cpu time used: 2.38774s
number of cells: 41139
Below is the plot of all solution boxes (on the left), the plot of all unknown boxes (on the right).
Here is a zoom on a fraction of unknown boxes:
This times, the solution boxes are all entirely inside the disk and the socalled unknown boxes enclose the boundary.
The choice of this terminology, and its consistency with the previous example, is justified further.
Just notice that the full disk is covered by the union of solution and unknown boxes.
It is possible to set the thickness of the boundary using the epsmin parameter.
For instance, if you IbexSolve using e 0.1
(or equivalently, epsmin=0.1
), you obtain:
Scope and limits¶
As illustrated by our previous examples, IbexSolve can solve any system of nonlinear equations and inequalities in a complete and validated way, including underconstrained systems.
All usual operators are allowed, including trigonometric functions but also sign, absolute value and min/max operators.
Furthermore, IbexSolve is a enduser program cooked by the ibex team, that resorts to a unique blackbox strategy (whatever the input problem is) and with a very limited number of parameters. Needless to say, this strategy is a kind of compromise and not the best one for a specific problem.
For programmers, the core library actually offers a generic solver, a C++ class that allows to easily build your own solver.
The main shortcoming of IbexSolve is that time is not bounded. This solver is not appropriate for online computations. You may typically expect some seconds or minutes of computing for smallscaled problems (less than 10 variables). But, beyond, it can takes hours or more.
The output of IbexSolve¶
Let us first formally define what a system is. We call a system the given of
1 m equations
\[\forall i\in\{1,\ldots,m\}, \quad f_i(x)=0\]or, in short, f(x)=0, with \(f:\mathbb{R}^n\to\mathbb{R}^m\). If m=0 then \(\{1,\ldots,m\}=\emptyset\) so the relation f(x)=0 becomes a tautology and can be omitted.
2 p inequalities
\[\forall i\in\{1,\ldots,p\}, \quad g_i(x)\leq0\]or, in short, g(x)<=0, with \(g:\mathbb{R}^n\to\mathbb{R}^p\). If p=0 then g(x)<=0 is a tautology and can be omitted.
In the sequel:
 n will denote the number of variables
 m the number of equations (can be zero)
 p the number of inequalities (can be zero).
We call manifold the set M of solution points of a given system.
IbexSolve produces 4 different types of boxes:
 the set S of solution boxes
 the set B of boundary boxes
 the set U of unknown boxes
 the set P of pending boxes
The first important property is that the manifold is covered by these sets:
The properties of each type of boxes are detailed right below and the solver strategy further.
Solution boxes¶
In the case of a square system of equations, a solution box corresponds to the usual meaning, i.e., a box that is proved to contain a solution.
We shall give here a more general definition that also embraces the case of underconstrained systems.
In the general case, and as illustrated in the circle example, the idea behind IbexSolve is to compute boxes that capture the local “topology” of the manifold.
More precisely, we consider a box as solution when there exists an homeomorphism between the part of the manifold enclosed by a box and the unit open ball
So, [x] is a solution box only if:
where \(\mathring{[x]}\) denotes the interior of [x]. Note that this definition imposes [x] to have a nonnull radius on each of its components.
Parametrization¶
When IbexSolve finds a solution, it does not only supply the box but also give an information on how the homeomorphism can be built. This is also illustrated with the gray box of our circle example where, roughly speaking, one of the variable is identified as the leading direction of the curve.
More generally, IbexSolve will give you a partition of the vector x into two subset of variables u (called parameters) and v. The size of u is nm and the size of v is m.
For simplicity, we assume that f(u,v) stands for f(x).
Now, this partition must be interpreted as follows. First, because [x] (hence [u]) has a nonempty interior, there is an homeomorphism \(\phi_1:B\to\mathring{[u]}\). Second, for every point u* in \(\mathring{[u]}\) a (classical) Newton iteration applied to f(u*,.)=0 starting for some value v in [v] will converge to some v* such that (u*,v*) is a point of M inside [x]. This is another homeomorphism \(\phi_2:\mathring{[u]}\to \mathring{[x]}\cap M\).
The sought homeomorphism is \(\varphi_1 \circ \varphi_2\).
This homeomorphism corresponds to the usual concept of chart and our partition gives indeed a local parametrization of the manifold. However, the parametrization involves a numerical algorithm (the Newton iteration) so it is only an implicit definition. But this makes sense from a practical standpoint. For instance, if one wants to plot the manifold, he/she knows that this can be easily done by sampling values in the parameter vector and compute corresponding point using a Newton iteration.
In a sense, we can say that in a solution box the manifold is processable.
Case of n=m¶
In the case of a wellconstrained system (n=m), v=x and our definition of solution box boils down to
so that our definition of solution box in this case exactly matches the usual meaning of “solution box” in the interval community.
Case of n=0¶
In the case of a system without equation (m=0), u=x and our definition of solution box boils down to
so that our definition of solution box in this case exactly matches the usual meaning of “inner box” in the interval community.
This explains why the solution boxes in our introduction example are inside the disk.
Boundary boxes¶
A boundary box intuitively corresponds to a box which intersects an inequality boundary. This should not be confused with the boundary of the manifold. For instance, in the circle example in introduction, there is no inequality hence no boundary box.
We may require additional properties on such boxes; for instance, that the inequality surface is not tangential to the boundaryfree manifold f(x)=0. But checking such properties has a computational price. Sometimes, like in our disk example, we have a large number of boundary boxes and we prefer a weaker but cheaper boundary test.
For this reason, we have introduced in IbexSolve different boundary policies. The policy is set thanks to the boundary
option.
So far, the following policies exist:
true
: any box is considered as a boundary. This policy is set by default for underconstrained systems, see the solver strategy.false
: all boxes are considered as boundary. This policy is set by default for inequalities, see the solver strategy.fullrank
: some inequalities are potentially active and the gradients of all constraints (equations and potentially activated inequalities) are linearly independent.This situation typically corresponds to constraint qualification in the realm of optimization. However, in the current state of development the inequality activation is not proved (we don’t certify that f=0 and \(g_i=0\) are simultaneously satisfied inside the box). This is still in development.
halfball
: this option is not available yet. This policy means that the manifold inside the box is homeomorphic to the halfunit ball: \[B^+:=\{x \in\mathbb{R}^{nm}, \x\<1, \x_1\\geq 0\}.\]
This is still in development.
Unknown and pending boxes¶
The goal of IbexSolve is to describe a manifold with solution and boundary boxes. To this end, solution and boundary tests are used. These tests may however not apply on large boxes. Of course, one reason is that a large box may simply neither be a solution nor a boundary box. Another reason is that tests are just sufficient conditions. So the program splits recursively the initial box until one test succeeds. This leads to a classical binary search tree.
However, it is frequent that no test will ever succeed in the vicinity of some points, whatever the size of the box is. This typically happens when f is singular. For this reason, the user has to fix a parameter value \(\varepsilon_{min}\) to stop bisection. This parameter allows to prevent bisecting again, although no test has succeeded yet. A box [x] is not split anymore if all the components of [x] has a radius smaller than \(\varepsilon_{min}\).
But it is also possible to control the search by fixing some time limit T.
As said before, when the process terminates successfully, only solution and boundary boxes are issued. Otherwise, socalled unknown or pending boxes can appear, depending on the failure reason:
 If both the solution and boundary tests do not apply on a box which cannot be split anymore (the precision \(\varepsilon_{min}\) being reached), the latter is classified as an unknown box.
 If a box has not been processed because of the timeout, it is classified as a pending box.
The two types of boxes are distinguished as their semantic is quite different: a pending box can potentially be successfully processed providing a longer time limit, or even within the same time limit using a different exploration strategy. On the contrary, an unknown box cannot be processed successfuly whatever the time limit is. The only way is by decreasing \(\varepsilon_{min}\).
Solving strategy¶
The solving strategy depends on the type of systems
 inequalities only (m=0).
For this type of systems, IbexSolve will try to cover the manifold with either solution or boundary boxes, indifferently. We don’t try
to prioritize one type because they are not comparable. Indeed, solution boxes fully satisy inequalities g(x)<0 while boundary boxes crosses
g(x)=0. We may be more interested in either one. However, the default boundary policy is
false
, which means that, by default, we prioritize solution boxes. In fact, we even refuse to consider a box as boundary with this policy which means that the paving will finely cover the manifold boundary with unknown boxes, as shown in our disk example. Note that for this type of problems, the epsmax parameter applies to both boxes.  underconstrained systems (0<m<n).
Note that this type of systems include at least one equality. IbexSolve will try to cover the manifold with as many solution boxes as possible.
So it will bisect boxes until either a solution is found or the minimal precision epsmin parameter is reached.
This is only at this point that the solver will try to eventually enforce a boundary test. And if it fails, the box is marked as unknown.
So, for this type of problems, the epsmax parameter does not apply to boundary boxes.
The default boundary policy is
true
(no time wasted to check boundary property).  wellconstrained systems (m=n).
For this type of systems, we don’t expect boundaries. If a solution of f(x)=0 also matches g(x)=0, the resulting box will be marked as unknown.
In this case, the default boundary policy is
false
(no time wasted to check boundary property). The reason why it is nottrue
as in the previous case is precisely because a boundary is now unexpected.
Options¶
The epsmin parameter¶
This parameter basically allows to control the solution accuracy.
It imposes the minimal width of validated boxes (boundary or solution) or, said differently, the maximal width of nonvalidated boxes. So this is a criterion to stop bisection: a nonvalidated box will not be larger than \(\varepsilon_{min}\).
Default value is 1e3.
The epsmax parameter¶
This parameter is the maximal width of validated boxes (boundary or solution). So this is a criterion to force bisection: a validated box will not be larger than \(\varepsilon_{max}\) (unless there is no equality and it is fully inside inequalities). Default value is +oo (none).
The effect of the epsmax parameter is best illustrated in the case of pure inequalities, where solution and boundary boxes have equivalent roles (cf. the solver strategy).
So let us get back again to our disk example.
If we use the boundary=true
option, the program immediately stops with one boundary box. This is OK because the first box handled by the solver satisfies one of the criterion (either solution or boundary) and since \(\varepsilon_{max}\) is set by default to +oo, the size of this box is less than \(\varepsilon_{max}\), so the search is over.
Now, if we set \(\varepsilon_{max}\) to 1 we obtain graphically the following result:
Note that by setting the boundary policy to true
, no property at all is checked. This explains why the boundary boxes are bigger here than in the picture of
the circle example. Indeed, no bisection are required to enforce the boundary property. This is just governed by the \(\varepsilon_{max}\) parameter.
If we run IbexSolve using E 0.5
, we obtain:
and using E 0.1
:
You can control this way the accuracy of the description. Of course, as before, the more accurate, the more boxes you have and the longer it takes.
In the case of a system with both equations and inequalities, the parameter \(\varepsilon_{max}\) will apply for both inner and boundary boxes. If we consider now the following Minibex code:
variables
x,y;
constraints
x^2+y^2=1;
y+x>=0;
end
we obtain the following figures by using decreasing values of \(\varepsilon_{max}\) (namely 1, 0.5 and 0.1):
Overview¶
e<float>, –epsmin=<float>  Minimal width of output boxes. This is a criterion to stop bisection: a nonvalidated box will not be larger than ‘epsmin’. Default value is 1e3. 
E<float>, –epsmax=<float>  Maximal width of output boxes. This is a criterion to force bisection: a validated box will not be larger than ‘epsmax’ (unless there is no equality and it is fully inside inequalities). Default value is +oo (none) 
t<float>, –timeout=<float>  Timeout (time in seconds). Default value is +oo (none). 
–simpl=…  Expression simplification level. Possible values are:
Default value is : 1. 
i<filename>, –input=<filename>  COV input file. The file contains a (intermediate) description of the manifold with boxes in the COV (binary) format. 
o<filename>, –output=<filename>  COV output file. The file will contain the description of the manifold with boxes in the COV (binary) format. 
–format  Give a description of the COV format used by IbexSolve 
–bfs  Perform breadthfirst search (instead of depthfirst search, by default) 
–trace  Activate trace. “Solutions” (output boxes) are displayed as and when they are found. 
–stopatfirst  Stop at first solution/boundary/unknown box found. 
–boundary=…  Boundary policy. Possible values are:

s, –sols  Display the “solutions” (output boxes) on the standard output. 
–randomseed=<float>  Random seed (useful for reproducibility). Default value is 1. 
q, –quiet  Print no report on the standard output. 
–forcedparams=<string>  Force some variables to be parameters in the parametric proofs, separated by ‘+’. Example: –forcedparams=x+y 