Analytica 4.3 beta Release Notes/Changes in 4.3.1.2

This page details changes in the 4.3.1.2 build, the final release build, since the previously announced beta 4.3.0.25 build. Numerous bugs, including several crashes that were found during beta testing, were fixed but not included here in this listing.

Licensing and Installation

• This is now a release build, rather than a beta build. Hence, a release license is required.
  • For users with active support, a valid 4.2 license installed and internet connectivity, the installer will automatically acquire a valid 4.3 license at installation time.

Optimizer

• When you double click on a «LP», «NLP», etc., object (the result of DefineOptimization):
  • The status is now included in the list of items displayed. This may save you from having to include an OptStatusText node.
  • Fields, Extrinsic indexes and Intrinsic indexes are shown. When you click on the «ref» cell for these fields, it shows you where each extrinsic or intrinsic index originated from. When you are debugging your model formulation, trying to figure out why a particular index is showing up as extrinsic (or intrinsic), this leads you to the source -- the particular decision(s), constraint(s) or objective.

• The local indexes returned by OptInfo which index the vector of scalar decisions has been renamed from .Vars to .DecisionVector. Similarly, the local index for the vector of scalar constraints has been renamed from .Constraints to .ConstraintVector.

• Local decision variables were not appearing in the result of OptInfo(..,item:'decisions') but now are.

• OptWrite has been sped up. It was slow on extremely large models.

• OptRead, OptWrite and OptWriteIIS functions now infer the format from the file extension when you don't specify the «format» parameter. Specifically, *.lp, *.mps and *.lpfml map to the formats "LP", "MPS", and "LPFML".

Optimizer Manual

• New chapter covering use of Dynamic and uncertainty in the context of optimization models.

• Substantial edits on content there previously.

Domain

• A domain bounds warning is now issued (and was not previously) for a variable with a boolean domain that evaluates to a text value. Similarly, when you're model logic contains a comparison of a boolean-domain variable to a text value, it also issues a warning about a potential error in your modeling logic.