Versions Compared

Old Version 4

changes.mady.by.user Dave Trier

Saved on

compared with

New Version 5

changes.mady.by.user Dave Trier

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents

Table of Contents

What’s New in v2.1:

  1. Including “Model Functions” definition feature to “Add Model” wizard.

    1. Inspects the code searching for functions to include as options of the dropdown.

    2. Read “smart comments” and pre-sets functions.

    3. Include help about “Model Functions” and “Smart Tags” in information icon.

  2. Editing existing model.

    1. Basic Model Info.

    2. Model Functions (same way).

    3. Platform summary.

    4. Catches unsaved changes in code before saving.

  3. ModelOp toolbar update.

    1. Get rid of “Model Details” button (it was for debugging purposes).

    2. The “Asset Details” button lets you edit the asset name and repo info.

  4. Include Live Search on the “Load Model” screen.

    1. Allow search by model name

    2. Allow search by tag

  5. Support for external parameterized ModelOp Center base URL.

    1. Environment variable setup.

    2. Parameter in NBextensions config.

    3. Enable CORS support to invoke REST API from Jupyter external host.

    4. Enable external libraries compatibility when running on an custom instance.

    5. Add support for Jupyter versions prior to 5.7.0, incompatibility between jquery 3+ and jquery-ui <1.12

  6. Validating file extension to source code asset filename (when creating model and when editing asset file name)

  7. Visualizing ModelOp Jupyter plugin version in all dialogs

  8. Visual feedback on the attachments file upload status

  9. Support for asset role definition on the attachments (during model creation and during file upload).

  10. Enable plugin for Jupyterhub notebook.

  11. Bug Fixes:

    1. When a model was just created the “submit” screen didn’t show the last changes (the initial commit).

    2. Update local cell metadata when saving a model (to avoid keeping outdated data).

    3. Validate to include only code cells in the model creation

    4. Include the model summary in the ‘Save’ screen.

    5. Updating a model overwrote MOC with the current (modified) local copy. That got fixed on “Model Save”, “Model functions editing”, “Asset button edit”

...