Ipopt

Introduction

Ipopt (Interior Point OPTimizer, pronounced eye-pea-Opt) is a software package for large-scale nonlinear optimization. It is designed to find (local) solutions of mathematical optimization problems of the form

   min     f(x)
  x ∈ Rⁿ

s.t.       g_L ≤ g(x) ≤ g_U
           x_L ≤  x   ≤ x_U

where f(x): Rⁿ --> R is the objective function, and g(x): Rⁿ --> Rᵐ are the constraint functions. The vectors g_L and g_U denote the lower and upper bounds on the constraints, and the vectors x_L and x_U are the bounds on the variables x. The functions f(x) and g(x) can be nonlinear and nonconvex, but should be twice continuously differentiable. Note that equality constraints can be formulated in the above formulation by setting the corresponding components of g_L and g_U to the same value.

Ipopt is part of the COIN-OR Initiative. The Ipopt project webpage is https://github.com/coin-or/Ipopt.

Background

Ipopt is written in C++ and is released as open source code under the Eclipse Public License (EPL). The code has been written by Andreas Wächter and Carl Laird. The COIN-OR project managers for Ipopt are Andreas Wächter und Stefan Vigerske. For a list of all contributors, see the AUTHORS file.

The C++ version has first been released on Aug 26, 2005 as version 3.0.0. The previously released pre-3.0 Fortran version is no longer maintained.

The Ipopt distribution can be used to generate a library that can be linked to one's own C++, C, Fortran, or Java code, as well as a solver executable for the AMPL modeling environment. The package includes an interface to the R programming environment. IPOPT can be used on Linux/UNIX, macOS, and Windows platforms.

As open source software, the source code for Ipopt is provided without charge. You are free to use it, also for commercial purposes. You are also free to modify the source code (with the restriction that you need to make your changes public if you decide to distribute your version in any way, e.g. as an executable); for details see the EPL license. And we are certainly very keen on feedback from users, including contributions!

In order to compile Ipopt, certain third party code is required (such as some linear algebra routines). Those are available under different conditions/licenses.

If you want to learn more about Ipopt, you can find references in the bibliography of the documentation.

For information on projects or papers that use Ipopt, refer to the Ipopt usage stories and papers discussion.

Getting Started

Please consult the detailed installation instructions in the Ipopt documentation. In the following, we only summarize some main points.

Dependencies

Ipopt requires at least one of the following solvers for systems of linear equations:

• MA27, MA57, HSL_MA77, HSL_MA86, or HSL_MA97 from the Harwell Subroutines Library (HSL). It is recommended to use project ThirdParty-HSL to build a HSL library for use by Ipopt. Alternatively, prebuild libraries are available from JuliaHSL, see the Ipopt installation instruction.
• Parallel Sparse Direct Linear Solver (Pardiso). Note, that the Intel Math Kernel Library (MKL) also includes a version of Pardiso, but the one from Pardiso Project often offers better performance.
• Sparse Parallel Robust Algorithms Library (SPRAL).
• MUltifrontal Massively Parallel sparse direct Solver (MUMPS). It is highly recommended to use project ThirdParty-Mumps to build a MUMPS library for use by Ipopt.
• Watson Sparse Matrix Package

A fast implementation of BLAS and LAPACK is required by Ipopt.

To build the AMPL interface of Ipopt, the AMPL Solver Library (ASL) is required. It is recommended to use project ThirdParty-ASL to build a ASL library for use by Ipopt.

Build

After installation of dependencies, an Ipopt build and installation follows these 4 steps:

1. Run ./configure. Use ./configure --help to see available options.

2. Run make to build the Ipopt libraries. If ASL was made available, also Ipopt executables will be build.

3. Run make test to test the Ipopt build.

4. Run make install to install Ipopt (libraries, executables, and header files).

It is suggested to use the same installation prefix (--prefix option of configure) when configuring the build of ThirdParty-ASL, ThirdParty-HSL, ThirdParty-MUMPS, and Ipopt.

Using coinbrew

An alternative to the above steps is to use the coinbrew script from https://coin-or.github.io/coinbrew/. coinbrew automates the download of the source code for ASL, MUMPS, and Ipopt and the sequential build and installation of these three packages.

After obtaining the coinbrew script, run

/path/to/coinbrew fetch Ipopt --no-prompt
/path/to/coinbrew build Ipopt --prefix=/dir/to/install --test --no-prompt --verbosity=3
/path/to/coinbrew install Ipopt --no-prompt

More details on using coinbrew can be found at the instructions on Getting Started with the COIN-OR Optimization Suite.

Precompiled binaries

Some precompiled binaries of Ipopt are also available:

• Ipopt releases page provides libraries and executables for Windows
• JuliaBinaryWrappers provides libraries and executables; JuliaHSL provides prebuild HSL libraries
• IDEAS provides executables; these executables include HSL solvers

Getting Help

• Ipopt Documentation with installation instructions, options reference, and more
• Issue tracking system: If you believe you found a bug in the code, please use the issue tracking system. Please include as much information as possible, and if possible some (ideally simple) example code so that we can reproduce the error.
• Discussions: ask questions, share ideas, engage with the Ipopt community
• Mailing list archive (2002-2020): predecessor of Discussions
• External resources:
  • short Ipopt tutorial

Please Cite Us

We provide this program in the hope that it may be useful to others, and we would very much like to hear about your experience with it. If you found it helpful and are using it within our software, we encourage you to add your feedback to the Ipopt usage stories and papers discussion.

Since a lot of time and effort has gone into Ipopt's development, please cite the following publication if you are using Ipopt for your own research:

• A. Wächter and L. T. Biegler, On the Implementation of a Primal-Dual Interior Point Filter Line Search Algorithm for Large-Scale Nonlinear Programming, Mathematical Programming 106(1), pp. 25-57, 2006 (preprint)

Versioning

Ipopts version numbers have the form x.y.z. x.y specifies the major and minor version number of Ipopt. An increase in x or y can mean the addition or removal of features, backward-incompatible API changes, etc. Increases in y indicate less severe changes than increases in x. For example, the change from Ipopt 2 to Ipopt 3 came due to a complete rewrite of Ipopt in a different programming language. z specifies the release number of Ipopt. An increase in z usually means bugfixes or additions of small feature. Changes to the API, if any, are done in a backward-compatible way. However, the ABI may changed in a backward-incompatible way.

Source code is organized in branches named stable/x.y. Development towards a next x.y.z release is happening on the stable/x.y branch. The code on branch stable/x.y already caries a x.y.z version number, which can correspond to the next x.y.z release that will be made from this branch. The default branch of the repository is the latest stable/x.y branch, even if x.y is still in beta testing.

An Ipopt x.y.z release is associated with a tag releases/x.y.z on branch stable/x.y. Releases are fixed and don't change.

Additional branches may exist where development of bugfixes or features is taking place. A branch devel may collect development for the next Ipopt x.y version. It will be renamed to stable/x.y when it is considered stable enough for beta testing.

If you want to contribute a bugfix or small feature, please create a pull-request to the latest stable/x.y branch. If you want to contribute a larger feature or something else that changes the API, please create a pull-request to branch devel, if existing, and latest stable/x.y otherwise.