Update an Existing Model
This article describes how to update an existing model using Jupyter or the ModelOp Command Center.
Table of Contents
Â
Update an existing model using git
Changes made to the remote branch from which the model was imported into ModelOp Center will automatically sync with ModelOp Center. See Integrate with Git for more information.
Update an existing model using Jupyter
Update an Existing Model Using the ModelOp UI
Â
To update a model in the ModelOp UI:
Navigate to the ModelOp UI.
In the left column, click Inventory.
Change the drop-down to Implementations
Select the model you want to modify from the list. This opens the Model Implementation page.
Use the tabs to modify the appropriate section (Assets, Repository, Schema), as required
Â
(Advanced) Switching between Use Cases and Model Implementations
Upon upgrade to ModelOp v3.3 or for other reasons, a user may want to change a model implementation to a Use Case.
Â
Note: This is advanced functionality, so please proceed with caution.
Â
To do so, please follow these steps:
Identify the StoredModel id to be convertedÂ
In this example, we are converting a StoredModel type USE_CASE
to a PYTHON3
Implementation.
Â
Â
Define destination type to be used, from the next list of valid types.
PYTHON
PYTHON3
R
PFA
C
CPP
CC
JUPYTER
PFA_YAML
PFA_PPFA
JAVA
OCTAVE
DMN
CMMN
SAGEMAKER
DATAIKU
PYSPARK
USE_CASE
EXCEL
SAS
ENSEMBLE
VENDOR
MLFLOW
UNKNOWN
Any other value different than the list above wont work
In swagger find the PATCH section inside StoredModel Entities, and input StoredModel ID to be converted.
Â
Â
Identify the type of conversion to execute.
Scenario: to translate from USE_CASE
→ Implementation of type PYTHON3
{
"modelMetaData":{
"type" : "PYTHON3"
}
}
Â
Â
Scenario: to translate from Implementation typePYTHON3
→ USE_CASE
{
"modelMetaData":{
"type" : "USE_CASE"
}
}
Â
Hit Execute and confirm response HttpStatus is 200.
Â
Â
Edit
Â
Next Article: https://modelopdocs.atlassian.net/wiki/spaces/dv33/pages/1978435029 >
Â