nextmv-v0.26.0
May 8, 2025What's Changed
- Methods for updating batch-exp, scenario test. Support writing with
BaseModel
class. by @sebastian-quintero in #89
v0.2.1
May 7, 2025What's Changed
- Aligns nextmv write_local, fixes preprocess example by @merschformann in #14
- Uses write over write_local by @merschformann in #15
- Fixes 'running' status not being emitted by @merschformann in #16
Full Changelog: v0.2.0...v0.2.1
nextmv-scikit-learn-v0.2.0
May 7, 2025What's Changed
- Update scikit-learn and gurobi with latest Option declaration by @sebastian-quintero in #88
nextmv-v0.25.0
May 7, 2025What's Changed
- Associate a tracked run with an Instance ID.
nextmv-v0.24.0
May 7, 2025What's Changed
- Add
nextmv.Option
and deprecatenextmv.Parameter
by @sebastian-quintero in #82 - Introduce write, load and deprecate write_local, load_local by @sebastian-quintero in #83
- Add console_url to run information and result by @sebastian-quintero in #84
- Adds options to the Manifest by @sebastian-quintero in #85
- Make adjustments to tracked run by @sebastian-quintero in #86
- Add scenario tests to the application by @sebastian-quintero in #87
Human-friendly metrics
May 6, 2025
Applications can write custom metrics to the run output file using the standard Statistics convention. These custom metrics live under the top-level statistics
property of the run output and are extracted and displayed in the run details view in Nextmv Console.
These metrics were displayed in a technical manner using their full data path as the name of the metric. For example, if a custom metric tracking total waste was named total_waste
and was a property of the custom
object which in turn was a property of the result
object, the name of this metric would be displayed as result.custom.total_waste
.
These object data paths were obscuring the meaningful parts of the metric names, and the end user often only cares about the metric and its value, not where it’s stored in the output JSON file. For these reasons, the metrics are now displayed without the data paths and also are presented with a more human-friendly title casing.
Before
After
Updated acceptance tests
April 24, 2025
When creating a new acceptance test you can now specify a tolerance level for the pass/fail rules. Prior to this, you were only able to set hard rules on how a test would pass or fail. When setting the tolerance, you can define it as an absolute value (specific number) or as a relative value (percentage-based).
This tolerance will be reflected in the final chart visuals as well.
v0.2.0
April 23, 2025What's Changed
- Customizable polling options on app run by @sebastian-quintero in #13
New Contributors
- @sebastian-quintero made their first contribution in #13
Full Changelog: v0.1.5...v0.2.0
nextmv-v0.23.0
April 23, 2025What's Changed
- Add run queueing constructs by @sebastian-quintero in #81
Archive file downloads
April 23, 2025
A small update to the behavior for downloading run input and output ZIP files was made. Before, when you downloaded a ZIP file from the run (input or output), the files within the ZIP file would be automatically extracted and downloaded individually.
This auto-extraction has been disabled and now the ZIP file is downloaded as a single file that you can then extract as needed via your operating system (e.g. double click the file). This keeps all of the files in a single directory rather than spreading them out wherever they were downloaded.
Column pinning in table views
April 22, 2025
A new column pinning feature for table views has been added to Nextmv Console. Now when viewing table data you can select certain columns to be pinned by hovering over the column header cell and then clicking the pin icon.
To unpin the column, just click on the filled-in pin icon and the column will return to its normal location in the table. You can pin as many columns as needed.
nextmv-v0.22.0
April 21, 2025What's Changed
- Support running with nextmv.Input and nextmv.Options by @sebastian-quintero in #79
- Adds stop condition to polling mechanism by @sebastian-quintero in #80
Manage secrets in Console
April 21, 2025
The ability to manage secrets in Nextmv Console is now available. You can add new secret collections and assign them to instances or individual runs, as well as edit and delete existing secret collections.
Read more about how to use secret collections to enhance your app and workflow functionality in the Secrets collection reference section in Nextmv Docs.
nextmv-v0.21.1
April 17, 2025What's Changed
- Adds support for exist_ok on new app by @merschformann in #77
- Improves order of checking whether app exists by @merschformann in #78
Share view and other actions
April 8, 2025
You can now share a run URL with someone on your team and it will preserve the particular view that was shared. Before, if you were, say, on the Result view of a run and copied the URL to share with someone on your team, when they opened that URL they would land on the Details view. This produced a confusing experience when trying to share views.
Now, when you click the share view button, your current run view is copied as part of the URL and will open the run on the same view from which it was shared. Further, the URL will preserve the specific data and layout selections for that view if applicable. For instance, if you are viewing the result of a routing run with a split table and run visual, when you copy the link to share the URL, it will open on the Result view with the same split table and run visualization displayed.
In addition to this new share action, the create new and clone existing run action has been given a small makeover, and download input and output have been consolidated into a single download menu.
Create/clone new run
The ability to create a new run and clone an existing one was already in place, but it has been revamped with a universal +
action button that opens the menu of create options. This will also serve as a place for any future create new actions for runs and other entities.
Download input and output
The ability to download a run’s input and output file existed prior as well, but the UI to do so was only available on the Input and Result view respectively. And depending on the type of application or the run size, the UI to download the input or output could vary slightly. This update consolidates the download actions into a single menu that is always accessed from the same place and from any view.
Tabular data view for runs
April 3, 2025
All JSON-based application runs now have an automatic tabular view into the data. For a run result, the solution is extracted and presented in a tabular view; for the input view the full input data is used for the tabular view.
How the data is presented (code and table) can be toggled with a new control at the bottom of the page as well, so you can easily switch between JSON and tabular views of the data. The code view displays the input or output for a run like it did before, there is no change there, so at any point you can view the exact input or output for the run.
This update has been applied to new and past runs. Also, the view control will remember your last selection for the app, so each app can have its own default view into the data for each individual user.