Nextmv Docs

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.

The defined options interface has been enhanced for scenario tests to allow specifying multiple values for a single option. A + button next to the defined option control allows you to add as many controls (i.e. values) for a single option as needed. And like before, these multiple values are used to create a cross-product of runs for that scenario.

Nextmv Console supports the new managed options feature for defining model options. When you push your model to Nextmv Cloud, the defined (or managed) options will be surfaced with versions that use the model binary.

Also note that the options are made available for the app’s most recently pushed binary (active executable) and thus are able to be used immediately by the app’s managed devint and Latest instances.

When you assign a version to an instance, the options associated with that version (by way of the model binary that was attached to it) are passed through and made available on the instance. The UI displays all of the available options with their relevant controls with the default values selected if those were defined. You can accept all of the default options for the instance or add overrides for one or more options if desired (you can reset an option to its default value at any time). This method allows you to specify option overrides as defaults for certain instances.

When an instance is selected for a run, that instance’s defined options are passed through to the run. If the instance had overridden a default configuration value, that new value is shown as the option’s default value for the run. Like with an instance, you can override any of the option’s default values for the run. After the run has been created, you can view the Run configuration summary table to see which options were applied and where they came from.

Managed options shown in the create run view.