Nextmv Docs

When defining managed options for your model with the app manifest, you now have the ability to set a display name for the option. Before the actual option’s name would be the value that was displayed, but sometimes internal model options do not always translate to the most user-friendly names in a UI.

To define a display name for an option, you just add a display_name property in the ui definition block, like so:

- name: model.constraints.disable.maximumstops
  option_type: bool
  default: false
  required: false
  ui:
    display_name: Disable maximum stops

Then, when the option is loaded in Console, the name for the option field will be the display_name value rather than the name value.

You can read more about the display_name option in the UI section of the managed options docs.

You can now delete shadown and switchback tests directly from Console using the UI. On any experiment details view, click the Edit button in the header, then delete in the lower right, and then finally confirm the delete action.

When you delete a shadow test, all of the associated shadow runs are deleted as well. However, baseline runs are left in place as those runs are not tied to the experiment. Deleting a switchback test will not affect any of the runs associated with a switchback test, however, the switchback test information will be removed from those runs.

Note that once the experiment and its associated runs or run data has been deleted they cannot be recovered.

You now have the ability to delete runs in Console. On the run details view, click the “Edit” button in the header, and then click the “Delete” button in the lower right. A confirmation message will appear; click “Delete run” to delete the run. Note that once the run is deleted it cannot be recovered.

The ability to clone ensemble definitions has been added to Console. If you go to any existing ensemble definition and click the create button, there will be an option to clone that definition.

Clicking the clone button will take you to the create ensemble definition view with the fields pre-filled with the values from the ensemble definition that is being cloned. Once the cloned create ensemble definition view has loaded, you can further edit the new definition as needed.

The flow for creating a new app in Nextmv Console has been updated with a user-friendly walk-through that helps you get your app connected to your model. It closely follows the flow of the new user on-boarding screens for repeated use. Also, at anytime you can close the walk-through screens and go directly to your app.

The ID of the input input_id used for a scenario test run has been added to the scenario test result view’s pivot table. You can now use inputs as a basis for comparison and analysis in a scenario test result.

When you are creating a new entity in Nextmv Console, an ID is automatically generated based on the name. Before, if your name included a period (e.g. v1.1.2), the period would be converted to a hyphen which would lead to indecorous IDs like v1-1-2.

This auto-convert function has been updated to allow periods so now your IDs will better reflect standard naming practices. And you can always change the ID of an entity, it does not have to be based on the name.