Release notes

GAMS MIRO 1.0

New features

  • New deployment environment for configured MIRO applications. You can find more information about this here. The --mkapp=1 option (shortcut creation) is no longer supported.
  • MIRO now comes as an independent installer on the platforms Windows, MacOS and Linux. The installation is independent from the GAMS system. All GAMS versions 30.2 or later support GAMS MIRO.
  • [MIRO:table] syntax for pivoting a table column in MIRO is no longer supported. Instead, a symbol can now simply be declared as a table. Read more here.
  • Added ability to pivot tables in MIRO via the Configuration mode. Unlike the table statement in the GAMS model itself, this option does not affect the data contract between GAMS and MIRO resulting in variable columns.
  • Full dark mode support.
  • Added miro log option for custom logs and input validation
  • Added support for an individual README starting page (markdown document) which is displayed in the input section. The Readme file can be added/edited in Configuration mode.
  • Added support for own custom scripts for analysis purposes in Base and Hypercube mode.
  • New widget type: numeric Input.
  • One-dimensional sets can now be configured as dropdown menu.
  • New widget type: Multi-dropdown menu for one-dimensional, dynamic sets.
  • Added support for custom input widgets.
  • Added support for remote data import and export: users can import/export data from/to external sources via REST API.
  • Symbol links: Data of output symbols can now be used to populate tables of input symbols.
  • Sandbox scenarios:
    • The MIRO user interface can be seen as a sandbox. Data that is loaded into the interface is therefore located in this sandbox as a sandbox scenario. The data of the sandbox scenario can be come from the MIRO database, external databases, GDX containers, excel files, or can be entered manually.
    • File attachments are part of a scenario. If attachments are added to a sandbox scenario, they are included when saving this scenario.
    • Sandbox scenarios can be loaded in scenario comparison via load active button.
  • Added filter option for graphs: One dimension of a symbol visualized as a graphic can be configured as a filter dimension. Its elements can then be selected via a (multi-)drop-down menu. Only the data belonging to this selection is displayed in the graphic.

Minor new features and improvements

  • Bug fixes
  • New MIRO logo (Thank you Melina Klöckner!)
  • Full chinese language support (Thank you Ying Deng!)
  • Completely restructured Hypercube mode. This includes the change from CSV to GDX file format for scenario input and output data. This is espacially relevant for the manual job submission.
  • Changed directory name for custom renderers from customRenderer to renderer_<modelname>
  • Changed directory name for configuration files from conf to conf_<modelname>
  • Improved performance on startup of MIRO Base/Hypercube mode
  • Added Link to GAMS World Forum in help section.
  • Stop button in GAMS interaction now with soft kill first, then hard kill.
  • Scenario comparison: input and output symbol tabs are now displayed in different colors.
  • Added option to edit scenario access permissions.
  • When creating new scenario via Save as dialog, attachments of currently active scenario can now be duplicated. This does not apply to scenario access permissions.
  • Element text of singleton sets can now be appended with a double pipe ("||") and will be aggregated/disaggregated when loaded/stored from GDX. The value and/or the element text of a singleton Set can be used in the eval.Set option to evaluate the value/text at compile time and place it into a scoped compile-time variable. This is useful any information about double-dash parameters and GAMS options configured via Configuration mode gets lost when exporting a scenario as a GDX file. Read more here.
  • Changed prefix for double-dash parameters and GAMS options from GMSPAR_ / GMSOPT_ to _gmspar_ / _gmsopt_.
  • Double-dash parameters and GAMS options can now have the same name as GAMS symbols.
  • Maximum number of symbol tabs visible in Inpupt/Output section set to 5 (rest available via dropdown).
  • Bootstrap dropdown menus are now right aligned per default. They will be left-aligned when space on left is not sufficient.
  • "More" dropdown menu (visible when more than 5 input or output tabs are shown in MIRO) will now show currently active tab.
  • First two columns (symbol name and symbol text) of scalar input table are now automatically set to readonly.
  • Import data via spreadsheet: Added possibility to use a sheet dedicated to a single scalar with the sheet name being the name of the scalar and its value being in column A1.
  • When importing scenarios from data_<modelname> folder, these scenarios can now be read and executed by all users within the same user group as the user importing them. Before, only the user importing them could read and execute them.
  • Adding/removing rows is now no longer allowed when at least one column is readonly.
  • Variables and equations can now be exported via GDX.
  • Changed handling of NAs, zeros and EPS. Numeric NAs are not converted to 0 anymore; Zeros are now written to GDX as 0 instead of being squeezed out.
  • Increased precision of numeric values input tables to maximum precision.
  • Custom renderer functions are now extended with ellipsis arguments to make sure they are compatible with future MIRO versions.
  • Configuration mode:
    • New structure and design.
    • Added option to rename tab titles and symbol headers.
    • Added option to change the application title.
    • Added option to reorder symbol tabs.
    • Removed option to (de)activate the scenario functionality (e.g. save scenarios in database). Is always activated now.
    • Removed comment functionality in input tables.
    • Input scalars can now be used in charts as well.
    • Charts configuration has now access to MIRO database. Previously saved scenario data can now be used for the graphics configuration (besides the local file upload).
    • Added option to display graphic and table in split-screen for pie charts, maps and gantt charts.
    • Added option to remove invalid widget/graph configuration in Configuration mode
    • Added custom renderer option for graphics.
    • Added support for multiple pie charts via subplots
    • Added support for heatmaps (input tables).
    • Bar chart, Line chart, Scatter, plot, Bubble chart: Order logic of axis elements can now be adjusted.
    • Map: Markers can now be customized (icon, icon color, marker color).
    • Added option to set a fixed height and/or width for pie chart, donut chart, bar chart, histogram, scatter plot, line chart, bubble chart.
    • Added option to render a static picture instead of an interactive plot for pie chart, donut chart, bar chart, histogram, scatter plot, line chart, bubble chart.
    • Added option to set the axis scale ratio for line chart, scatter plot, bubble chart.
    • Added option 'area' and 'diameter' for bubble chart size measurement
    • Valuebox: Number of boxes in a row can now be customized.
    • Added option to configure number of decimal places for numericInput
    • Removed remote Execution setting from configuration mode. Moved to preferences that are accessible via the MIRO library.

GAMS MIRO 0.6

  • MIRO Configuration mode: The GAMS MIRO Configuration mode can be used to change the settings of your MIRO app as well as to generate new widgets and charts. When configuring your widgets and charts, you get a live preview so that you immediately see the results of your configuration. You don't need to touch JSON code anymore.
  • New data import mechanism: Instead of creating an Excel file that the user then has to upload in order to get the first data into MIRO, data relevant to MIRO is automatically extracted from your model and stored in the MIRO database.
  • Tab grouping: Group multiple input tabs and output tabs together.
  • Automated loading of data on startup: Automatically load data when your MIRO app launches, so tables won’t start out empty.
  • Automated scenario import into DB: GDX files that you place in the data_<modelname> folder of your MIRO app will be automatically imported into the MIRO database the next time you launch your app.
  • Improved UTF-8 support: You can now use non-ASCII characters throughout MIRO
  • Chinese language support (note that the MIRO Configuration mode is not yet translated, though).
  • Import and export of GDX files: Besides Excel spreadsheets you can now also import and export GDX containers.
  • GAMS Studio toolbar to launch MIRO.
  • Experimental support for Gantt charts.
  • Bug fixes and performance improvements.

GAMS MIRO 0.4

Initial release