minfx SVN archive

Minfx version 1.0.12.

This is a release preparing for future numpy changes. From numpy >= 1.9, a FutureWarning is emitted
whenever the comparison operators '==' and '!=' are used. The behaviour of the operators will
change for numpy objects in the future, and therefore these were replaced with 'is' and 'is not'.

Updated minfx to protect against future changes occurring in the numpy Python package.

From numpy version 1.9, the FutureWarning "__main__:1: FutureWarning: comparison to `None` will
result in an elementwise object comparison in the future." is seen in a number of minfx's
optimisation algorithms, and in all of the constraint algorithms.

The issue is that the behaviour of the comparison operators '==' and '!=' will change with future
numpy versions. These have been replaced with 'is' and 'is not' throughout.

Updated the API documentation for minfx 1.0.11.

Updated the version numbers to 1.0.11.

Backported the 1.0.11 tag CHANGES file to trunk.

The command used was:
svn merge -r180:181 svn+ssh://bugman@.../svn/minfx/tags/1.0.11 .

Updated the CHANGES file for minfx version 1.0.11.

Minfx version 1.0.11.

This is a major feature release. Finally infinite target function values are handled. When
infinite values are encountered, the main optimisation loop is terminated. This also occurs in the
main outer loop of the Method of Multipliers and log-barrier constraint algorithms. This
termination condition prevents optimisation from continuing forever.

Missing import of numpy.inf used to terminate optimisation when infinite function values occur.

This should have been part of r177.

Added a check for an infinite target function value to the logarithmic barrier main loop.

The check in the optimisation main loop for infinite values is not sufficient for stopping the
constraint algorithms. The log-barrier constraint algorithm will continue forever even if the
optimisation sub loop terminates.

Added a check for an infinite target function value to the Method of Multiplers main loop.

The check in the optimisation main loop for infinite values is not sufficient for stopping the
constraint algorithms. The Augmented Lagrangian or Method of Multiplers algorithm will continue
forever even if the optimisation sub loop terminates.