- Release Notes
- Before you begin
- Getting started
- Projects
- Datasets
- ML packages
- Pipelines
- ML Skills
- ML Logs
- Document Understanding in AI Center
- Licensing
- How To
- Basic Troubleshooting Guide
Managing ML packages
Before uploading packages, make sure they are built as specified here.
class, break, from, finally, global, None, etc. Make sure to choose another name. The listed examples are not complete since package name is used for class <pkg-name> and import <pck-name>.
Follow these steps to upload an already created package:
- In the ML Packages page, click the Upload zip file button. The Create New Package page is displayed.
- In the Create New Package page, enter a name for your package.
- Click Upload Package to select the desired
.zipfile or drag & drop the package.zipfile into the Upload package field. - (Optionally) Provide a clear description of the model.
The description is displayed while deploying a new skill based on this model, as well as on the ML Packages page.
- Select the input type from the drop-down. The possible options are:
- json
- file
- files
- (Optionally) Enter a clear description of the input expected by the model.
- (Optionally) Enter a clear description of the output returned by the model.
These descriptions are visible to RPA developers using the ML Skill Activity in UiPath Studio. As a good practice, we recommended showing an example of the input and output formats to facilitate communication between data scientists and developers.
- Select the development language of the model from the drop-down. The possible options are:
- Python 3.7
- Python 3.8
- Select whether the machine learning model requires a GPU, by default it is set to No. This information is surfaced as a suggestion to when a skill is created from this package.
- Select whether to enable training for your model. This is what happens if you enabled it:
- The package can be used in any pipeline.
- The validation step checks if the train.py file is implemented in the package, otherwise, the validation fails.
- Click Create to upload the package or Cancel to abort the process. The Create New Package window is closed and the package is uploaded and displayed along with its details in the ML Packages > [ML Package Name] page. It may take a few minutes before your upload is propagated.
class, break, from,
finally, global, None,
etc. Make sure to choose another name. The listed examples are not complete
since package name is used for class <pkg-name> and
import <pck-name>.
Use this procedure to upload an already created package:
- Private packages:
- The imported package will have the same name as in the export environment, taken from the metadata file. If a package with
the same name already exists, the
versionfield from the metadata will be checked next. If the version is the same, a new minor version will be created. For example, if you import a package namedNew Package, version7, and you already have a package with the same name, but version7.3exists, the new imported package will be version7.4. If there is no version, the created package will have the next available major version. - If the name from the imported package metadata does not exist in the destination environment, the new package name is created in the destination environment.
- The imported package will have the same name as in the export environment, taken from the metadata file. If a package with
the same name already exists, the
- Public packages:
- The imported package will have the same name as in the export environment, taken from the metadata file. If a package with
the same name already exists, the
sourcePackageVersionfield from the metadata will be checked next for thesourcePackageVersionin the destination environment. After this, the next minor version will be uploaded. Make sure to either change the version in the destination environment, or change thesourcePackageVersionfield in the metadata file to the available version in the destination environment. - If the name from the imported package metadata does not exist in the destination environment, the new package name is created in the destination environment.
- The imported package will have the same name as in the export environment, taken from the metadata file. If a package with
the same name already exists, the
- In case of private packages, if the major version of the imported package is different than the already existing one, an error is displayed.
.zip file against the requirements described here. The following three checks are performed:
- A non-empty root folder exists.
- A requirements.txt file exists.
- A file named main.py exists in the root folder which implements a class Main. The class is further validated to implement an
__init__and apredictfunction.
Success or failure along with any errors that caused it are shown in the ML Logs page.
.zip file against the requirements described here. For these packages the following two checks are performed:
- A non-empty root folder exists.
- A file named train.py exists in the root folder which implements a class Main. The class is further validated to implement an
__init__function and the following functions:train,evaluate, andsave.
Success or failure along with any errors that caused it are shown in the ML Logs page.
Click a package in the list to navigate to its ML Package > [ML Package Name] page.
In the Version tab, view its details: package version, creation time, change log, status, and arguments.
In the Pipeline runs tab, view the details related to the package's pipeline runs: package name, type, version, status, creation time, duration, score, and additional details.
AI Center also supports versioning and version management of packages. When a package is uploaded, it's displayed as version 1.0 of that package (we say it's Major Version is 1, and Minor Version is 0). This helps with differentiating between packages uploaded by users, and packages retrained via pipelines, the latter only changing their minor version.
Follow these steps to upload a new version for an already uploaded package:
- In the ML Packages page, click ⁝ next to a package and select the Upload new version option.
Alternatively, in the ML Package > [ML Package Name] page, click Upload new version. The Upload New Package Version for > [ML Package Name] window is displayed, with most of the fields prefilled with the information you provided at the time when you first uploaded that package.
- Click Upload Package to select the desired
.zipfile, or drag & drop the file above this field. - (Optionally) Update the existing information in the following fields:
- Input description
- Output description
- Language
- (Optionally) In the ChangeLog field, enter what has changed.
- Select whether the model requires a GPU, by default it is set to No.
- Select whether to enable training for your model.
- Click Create to upload the new version for the existing uploaded package or Cancel to abort the process. The Upload Package window is closed and the new version of the package is uploaded. It may take a few minutes before your upload is propagated.
The new version of the package is not visible directly in the ML Packages page. You can view its information within the ML Package Details page for that package.
When a training pipeline or a full pipeline executes successfully on a package version, a new minor version is created. For example, if I have uploaded a package (version 1.0), and start a training pipeline, version 1.1 is displayed after completion in the ML Package Details page as below:
In the ML Package > [ML Package Name] page Version tab, click :fa-info-circle: next to a package version. The Arguments for > [ML Package Name] > [ML Package Version] window is displayed.
The input type, and the input and output descriptions of the selected package version are displayed. Please note that you cannot edit the values.
Follow the steps from this procedure to download an already created package.
- A
zipfile containing the package - A
jsonfile containing the package metadata, such as name, version, and other information.
Packages can only be deleted if they are not deployed within a skill and no pipelines are currently running on those packages.
- In the ML Packages page, click ⁝ next to a package and select Delete undeployed versions. A confirmation window is displayed.
- In the confirmation window, click OK to delete all undeployed versions of the selected package. If a package version is part of a skill (it is active), it is NOT going to be deleted. If all the versions are inactive, they are all deleted.
OR
- In the ML Package > [ML Package Name] page Version tab, click ⁝ next to a package version and select Delete. A confirmation window is displayed.
- In the confirmation window, click OK to delete the selected version of the package. If a package version is part of a skill (it is active), it is NOT going to be deleted. If this is the only version for the selected package, the package itself is also deleted.
