Blog Post

FICO® Xpress Optimization Blog
2 MIN READ

Xpress Update 9.4.3

FICO's avatar
FICO
Community Manager
2 years ago
Xpress Update 9.4.3 is now available on the client area for Windows, Linux and MacOS on x86-64, and Linux and MacOS on AArch64, from

https://clientarea.xpress.fico.com/download_patch.php#943

These are the latest updates for the Xpress 9.4 release branch, and requires a matching license. Please note that these archives must be extracted over a prior installation of FICO Xpress 9.4.

Release Notes for 9.4.3

Xpress Optimizer 43.01.04
  • Fixed an issue that could result in MIP callbacks being fired from a different thread than the main thread when setting CALLBACKFROMMASTERTHREAD=1 and THREADS=1.
  • Fixed an issue with presolving of MIPs with indicator constraints that could result in invalid tightenings.
  • Fixed an issue when setting OBJSCALEFACTOR for MIQPs that could result in a sub-optimal solution being returned.
  • In multi-objective problems, the beforeobjective and afterobjective callbacks are now fired for empty objectives with non-zero weight. Objectives with zero weight are considered disabled and will continue to be skipped.

Xpress Nonlinear 43.01.04
  • The TIMELIMIT control is now also forwarded to Knitro and both TIMELIMIT and XSLP_MAXTIME include both the presolve and Knitro time.
  • Fixed a potential crash on nonlinear problems with binary rows with only a few repeating coefficients (where the configuration presolver would have been applied).
  • Fixed an issue with reading in .lp files with nonlinear coefficients like y * { x ^ 2 } <= 1 .
  • Fixed an issue that could lead to a wrong value for the objective transfer column when the objective coefficient was not +1.
  • Fixed an issue with the TIME attribute not including all of nonlinear presolve.

Xpress Interfaces 43.01.04 (Python, R, Matlab, .NET, Java)
  • Fixed an issue that caused API calls that change nonlinear formulas to be recorded incorrectly when API recording is enabled.
  • In Java and C# object based API any object information is now correctly dropped if the problem is reloaded via readProb() or loadLp() and friends. Previously, that information was not dropped which could lead to stale information being present.
Updated 2 years ago
Version 3.0
No CommentsBe the first to comment