Product Updates

Resolved AIMMS Issues Using an element of a Calendar in the function Val or FormatString could lead to a crash when the calendar was using a string parameter for its time format. The two-arguments version of the function Ord could lead to a crash when the ordering of the set that is specified as the second argument was still out-of-date.

Resolved AIMMS Issues Sensitivity ranges were not calculated for LP problems if the barrier algorithm with multiple threads was used.

AIMMS 4.67.2 Release The AIMMS 4.67.2 Release was released on May 29, 2019 (build 4.67.2.0). Changes made in this release are listed below. A high level overview can be found at the AIMMS New Features Page. Looking for best practices on how to use AIMMS? Check out the AIMMS Knowledge Center. Resolved AIMMS Issues A so-called GUI-expression in the WinUI could cause a serious bug when the compilation of that expression was triggering two or more warnings (for example warnings on non-initialized identifiers). AIMMS ended up in an endless loop that was just consuming more and more memory. The syntax highlighting could give some unexpected coloring in deeply nested language constructs. Having a domain condition which resulted in an empty domain, could sometimes lead to a severe internal error when used in the left hand side of an assignment statement. Resolved WebUI Issues It could happen that incorrect expressions used for the Display Domain option of a widget did not lead to an error message (and, as a result, to unexpected data being displayed in the widget).

There has been quite some discussions on the Totals of a table in the AIMMS WebUI. At this moment, you can select out of 5 options (Sum, Mean, Count, Min and Max) and AIMMS will calculate the respective row/column totals. However, the totals are based on all values that exist in the identifier, so filters and/or display domain settings are not considered (so it's not a 'subtotal', a termed used in Excel). In many situations this is either unclear or unwanted, in some it is fine. We now wonder if we should: Add a set of new totals that are the actual totals of what is displayed based on filtering and display domain setting (hence the subtotal). Benefit, you can also show the comparison between the totals of values seen and all value. Adjust the current set of totals to be actually the subtotals of what is displayed. If we would do 2, the only thing that would change is the value we calculate. If we would do 1, we would need to find a proper header for both totals (e.g. 'sum' and 'sum (all)' for respectively the total sum of what is visible and the total sum of the dense identifier for that slice). In the example below, the subtotal sum for Portland column should be 62.70 and subtotal count 2. Any thoughts on PREFERENCE (replace existing or add new) and on NAMING the total operators in case we extend the set so it display nicely in the table? Please comment below.

Main features are the single JSON structure and Gantt Chart improvements for the WebUI. AIMMS Improvements A new intrinsic procedure GarbageCollectStrings has been added to AIMMS. Calling this procedure may help in reducing the memory in use by AIMMS, when somehow the automatic garbage collect of unused strings does not seem to be triggered. See also the documentation in the Function Reference. The function CopyRange has been added to the AIMMSXLLibrary. WebUI Improvements We made a fundamental change in the storage of WebUI pages and widgets. For details, see the New Features page. Minimum and Maximum Resource Height have been introduced for the Gantt Chart. The Minimum Resource Height option adjusts the resource height such that when the height of all resources exceeds the height of the Gantt Chart widget, a vertical scroll bar appears on the right and the user can scroll down in order to see the resources below. When a batch is dragged down, the chart automatically scrolls to reveal the resources below. The Maximum Resource Height option will condense the resources to the set value such that the batches are not spread to fit the size of the Gantt Chart. As of this release, Gantt Chart jobs can now also be resized from the left side in case the duration of the job is editable (i.e. changing the start time while keeping the end time the same). A special cursor will appear if you hover on the sides of the job to signal that you can adjust its duration. There is a new option that allows developers to automatically open the WebUI upon project startup. It can be found in the AIMMS Options dialog in the category Project - Startup & Authorization, and is called Open_WebUI_on_startup. Resolved AIMMS Issues In a statement like MySet += myElementParameter, the set MySet could incorrectly be modified if myElementParameter contained inactive data. This could happen if myElementParameter had been assigned a certain element but that same element was later removed from the range set of myElementParameter. When using such an element parameter with inactive data in any expression, the element parameter should behave as if it is empty. When running a procedure from the WinUI that ended in a Halt statement, a strange empty error message dialog box popped up. CPLEX errors could be generated if the model contained indicator constraints and the CPLEX option 'Check solution' was switched on. AIMMS crashed if the ShadowPriceRange property was specified for a constraint in a multi-objective optimization model. (Note: sensitivity information is not available for multi-objective optimization models.) The (deprecated) Math Program suffices modelstat and solverstat were no longer updated. Resolved WebUI Issues If no value was set for the procedure column in the WidgetActions string parameter identifier, none of the widget actions were listed in the widget. Widget actions, bar chart settings, line chart settings and store focus options were not displayed in the Options editor when running a WebUI app on an iPad. After editing a cell in a Table involving a vertical scrollbar, the focus on the current element could be lost (i.e. on a row which scrolled out of focus as a result of the edit).

AIMMS 4.66.2 Release The AIMMS 4.66.2 Release was released on May 17, 2019 (build 4.66.2.6). Changes made in this release are listed below. A high level overview can be found at the AIMMS New Features Page. Resolved AIMMS Issues CPLEX errors could be generated if the model contained indicator constraints and the CPLEX option 'Check solution' was switched on. Sometimes an incorrect unit analysis warning was triggered, when the units involved unit parameters. Using the loopcount in the condition of a For statement could lead to a severe compilation error. The specification ">t8i" in the FormatString caused an error when the actual value to display was equal to 0. When a multi-dimensional identifier was written without parentheses where that was not expected, AIMMS would sometimes crash instead of raising a compilation error. In rare cases, when the WebUI was open, AIMMS would hang during compilation (showing the 'Scanning' status). High dimensional identifiers leaked memory when closing the model (but not AIMMS). Resolved WebUI Issues Sometimes identifiers which should display were hidden on a page. Zooming in the map widget using the mouse would sometimes also scroll the whole page. Earlier, if the node size for a set of nodes was the same, the map would consider the value in the set with node radius ranging from 3 to 10, i.e any value 3 and below would take node radius as 3, 10 and above as 10 and the rest the absolute value 4-9. We have now increased the max size to 21.25, so node size 3 and below will be radius 3, 4 to 21 that absolute value and 21 and above radius 21.25. Having a domain condition which only involved an element parameter, could lead to the associated identifier not being displayed in the WebUI. Using custom widget positions could lead to unexpected rendering of your WebUI when resizing the screen. In the Selection box widget, the order of the elements displayed in the selection list was not always as expected. When running a procedure (by pressing a button on the WebUI) and having the Data Manager still open, could lead to a message stating that 'another procedure is already running'.

A new version of AIMMS PRO has been released (AIMMS PRO 2.31.3 (2.31.3.3)). AIMMS PRO 2.31.3 Release On May 21, 2019, we released AIMMS PRO 2.31.3 (2.31.3.3). Changes made in this release are listed below. Improvements DB Tunnel App: Provides easy and occasional access to the AIMMS Cloud App database running in VPN. Please see the documentation for more details. Resolved Issues On-Premise: Fixed an issue where installation or upgrade to AIMMS PRO 2.30 or higher could fail on some Windows Servers due to the incorrect version detection check by AIMMS PRO. Release notes for AIMMS PRO

AIMMS PRO 2.31.1 (2.31.1.4) has just been released. For more details please visit https://aimms.com/english/developers/downloads/download-aimms-pro/pro-release-notes/ Starting with this version we provide secure VPN connection to the Application Databases for Cloud Customers. For details please visit https://manual.aimms.com/cloud/db-config.html

In light of our Workflow improvement project, we had defined 4 new user stories that we have been developing and releasing over the last few months. At this moment, we are about to release the Widget Actions (4.66) after having released the Side Panels and Dialog Page concepts (see https://aimms.com/english/developers/downloads/product-information/new-features). Our next task ahead is a new UI concept to help end users to go through a particular workflow; we call this the Workflow Menu. Below you can find the most current (illustrative) design sketches we created to be able to discuss our ideas with stakeholders. I like to use this forum to collect some feedback from you. My current ask is what you prefer, assuming you have the choice between 2 ideas, what would you choose? Horizontal (left to right) or Vertical (top to bottom). Please use the poll below. BTW: you also see some visualization ideas on the state of a step in a workflow (state options are active, inactive, incomplete, complete, and error). Of course, any other feedback is welcome!

We have started with the integration of scripting language a while back (our 1st language was R, see https://manual.aimms.com/rlink). Currently, we are working on integrating Python. Our first step is to have it available for AIMMS App Developers such they can integrate Python scripts into their models with the purpose to improve your overall application. The idea is to do this is a (more) general way such that other scripting languages can follow. Also, we want to assure developers can debug the scripts during development and integrations before deploying them (step 2). Our second step is to enable you to deploy models on your AIMMS Cloud, or your AIMMS PRO on premise platform. This to assure we are empowering the end users of the Apps. We foresee a number of use cases, for example Use of specific Python functions not available in AIMMS s.a. ML algorithms to e.g. create better forecasts to feed the model Ability to fetch and process data from other sources that is needed for your model .. What use cases do you see for AIMMS with a Python integration? We love to hear from you.

AIMMS 4.65.1, including the Dialog Pages feature, has just been released. Also CPLEX 12.9 has been added. Please read complete release notes here

Today (29 March 2019) we released AIMMS PRO Hotfix Release 2.30.3 (2.30.3.0), which is mainly needed for On-premise Customers. For more details please visit, https://aimms.com/english/developers/downloads/download-aimms-pro/pro-release-notes/ Starting with this PRO version Audit logs can be available for on-premise customers. For new installation ‘AUDIT_LOG_LEVEL’ property will be there into AimmsPROServerlog.xml file with the default value ‘OFF”. For existing installation, you can do ‘Restore all to Defaults’ in log management then AimmsPROServerlog.xml file will be altered with this settings.