Model Versions vs. Model Variations
Model Version
- A model version represents a specific iteration or generation of a model. It is typically a snapshot of the model at a particular point in its lifecycle, often marked by significant changes or improvements made to the model's architecture, training data, or hyperparameters. Each model version encapsulates the complete setup needed to replicate the model's performance.
- Example: Consider a facial recognition model. The initial release, trained on a limited dataset, is designated as Version 1.0. Over time, as the training dataset is expanded with more diverse images, the model is retrained to improve accuracy and robustness, resulting in Version 2.0.
- Use Case: Model versions are used to track the evolution of a model over time. This allows developers and data scientists to deploy specific versions based on performance, compliance with regulations, or compatibility with specific applications.
Model Variation
- A model variation refers to different configurations or customizations of a given model version within a specific framework. Variations might include changes in configuration settings, use of different layers or activation functions, or adjustments specific to deployment environments. Each variation within a version/framework combination is identified by a unique variation name.
- Example: Continuing with the facial recognition model in Version 2.0, you might have different variations to address different operational needs:
- Variation A: Configured for real-time processing on mobile devices, with a focus on speed over accuracy.
- Variation B: Optimized for high accuracy in controlled environments, suitable for security systems.
- Use Case: Model variations allow for fine-tuning and optimizing a model version to meet specific requirements or constraints of different deployment scenarios. They enable organizations to leverage the same underlying model architecture and training, while adapting to diverse needs and conditions.
Supported Frameworks
- A model version can have multiple frameworks, and each framework might consist of multiple variations with different configurations or customizations.
- The platform currently facilitates a few frameworks, with additional ones currently in development and slated for imminent release. The frameworks list is:
- Pytorch
- Keras - Tensorflow
- Scikit Learn [Coming Soon]
- Transformers [Coming Soon]
- Fastai [Coming Soon]
- LightGBM [Coming Soon]
- XGBoost [Coming Soon]
- Prophet [Coming Soon]
Add model versions
Add versions using client library: Please note, the creation of model versions is supported solely via our proprietary library or client library tool.
Add model variations
Add variations using client library: Please note, the creation of model variations is supported solely via our proprietary library or client library tool.
Add model variation tags
- Under the Model Version section, expand the Model Variation Configuration section.
- Click on Manage tags
- To add multiple tags, use the Add tag button. If any tag is not needed you can delete it by clicking on the delete button on the right side of the tag.
- Finally, click on Submit to add the tags in a model.
Remove model variation tags
- Once the tags are removed from the model variation, you will no longer be able to categorize, search or filter that variation in relation to the tag key or values. Before deleting the tags make sure you no longer need those tags.
- To remove model tags, simply click on the cross icon (X) of a tag.
- To remove all model tags at once, click on the Remove all tags button.
- Confirm the removal process and click on Confirm
Delete Model Variation
- Select the variant to delete from the dropdown. Then click on the Delete variant button.
- Confirm the deletion process and click on Confirm.
Delete Model Version
- Select the version to delete from the dropdown. Then click on the Delete version button.
- Confirm the deletion process and click on Confirm