v1.48 Release Notes
Release Date: 4/8/2017
New Features
Stella Support. Epicenter now supports models written in Stella. Upload your
.stmx
file to your project's Model folder, then use the Interface Builder (or Epicenter.js) to create your user interface. See the Stella page for additional information.Interface Builder. The Interface Builder (Beta) includes several new features:
- Global Settings - Themes: You can select from one of six pre-built themes for your project.
- Global Settings - Project Defaults: You can now globally configure number formats for charts and variables.
- Global Settings - Header/Footer Settings: You can now add a logo image to the header for all pages.
- Support for Stella. You can use Interface Builder with your
.stmx
model files.
Improvements
When using a Powersim or Stella model, you can now ask for the variable
Step
to get the current step.When using a Powersim or Stella model, you can now ask for the value of a variable at the current step in two ways. Previously, you could retrieve this value by using an array index of the current step (
Sales[3]
). New in this release, you can also retrieve this value by asking for the "point in time" of the variable:Sales.POINT_IN_TIME
.When arrayed variables from Powersim or Stella are returned, the format is now an object, whose fields are the subscripts (ranges) and whose values are arrayed over time. For example, given:
Sales, Apples Sales, Oranges Step 80 180 0 100 200 1 120 220 2 130 230 3 140 240 4 a request for the "Sales" variable now returns:
{ "apples": [ 80, 100, 120, 130, 140 ], "oranges": [ 180, 200, 220, 230, 240 ] }
This format is easier to parse if you are looking for the values from a specific dimension of your array. See more details, including examples of requesting alternate formats (
.POINT_IN_TIME
and.COLLAPSED_ARRAY
), on the Powersim and Stella pages.All end users can now retrieve user name information from the Member API (REST) or Member API Adapter (Epicenter.js), given the user id of another end user. Previously, only end users who were facilitators could do this. This change makes it easier for multiplayer projects to display information for end users about other end users in the group or world — for example, the names of everyone in the world who is currently online.
The result of calling "introspect" on a model, either through the Epicenter.js Introspection Service or the RESTful Model Introspect API, now includes additional information. Specifically, the
ranges
section describes the enumerated ranges used in arrayed variables. Additionally, for each variable, a newaccess
field describes whether the variable canNEVER
be set, can be set onlyBEFORE
the run is advanced, or canALWAYS
be set.
Bug Fixes
In some cases, accessing information about end users who belonged to groups that had been deleted was causing an error. This has been corrected.
Documentation updates, including:
- Changes to the Model Context page to answer common questions about how and why to provide model context information.
- Additional background about channels for when you're working with the Epicenter.js Epicenter Channel Manager.
- A new How To article on using Flow.js to update your user interface when a model operation is called.
Other minor fixes for performance and stability.