mirror of
https://github.com/clearml/clearml-docs
synced 2025-06-26 18:17:44 +00:00
Small edits (#325)
This commit is contained in:
@@ -2,11 +2,12 @@
|
||||
title: ClearML Modules
|
||||
---
|
||||
|
||||
- **ClearML Python Package** (clearml) for integrating ClearML into your existing code-base.
|
||||
- **ClearML Server** (clearml-server) storing experiment, model, and workflow data, and supporting the Web UI experiment manager. It is also the control plane for the MLOps.
|
||||
- **ClearML Agent** (clearml-agent) The MLOps orchestration agent. Enabling experiment and workflow reproducibility, and scalability.
|
||||
- **ClearML Data** (clearml-data) data management and versioning on top of file-systems/object-storage.
|
||||
- **ClearML Session** (clearml-session) Launch remote instances of Jupyter Notebooks and VSCode.
|
||||
- [**ClearML Python Package**](../getting_started/ds/ds_first_steps.md#install-clearml) (`clearml`) for integrating ClearML into your existing code-base.
|
||||
- [**ClearML Server**](../deploying_clearml/clearml_server.md) (`clearml-server`) for storing experiment, model, and workflow data, and supporting the Web UI experiment manager. It is also the control plane for the MLOps.
|
||||
- [**ClearML Agent**](../clearml_agent.md) (`clearml-agent`), the MLOps orchestration agent. Enabling experiment and workflow reproducibility, and scalability.
|
||||
- [**ClearML Data**](../clearml_data/clearml_data.md) (`clearml-data`) data management and versioning on top of file-systems/object-storage.
|
||||
- [**ClearML Serving**](../clearml_serving/clearml_serving.md) (`clearml-serving`) for model deployment and orchestration.
|
||||
- [**ClearML Session**](../apps/clearml_session.md) (`clearml-session`) for launching remote instances of Jupyter Notebooks and VSCode.
|
||||
Solutions combined with the clearml-server control plane.
|
||||
|
||||

|
||||
|
||||
@@ -61,7 +61,7 @@ new_dataset.tags = ['latest']
|
||||
|
||||
We passed the `parents` argument when we created v2 of the Dataset, which inherits all the parent's version content.
|
||||
This not only helps trace back dataset changes with full genealogy, but also makes our storage more efficient,
|
||||
since it only store the changed and / or added files from the parent versions.
|
||||
since it only stores the changed and / or added files from the parent versions.
|
||||
When we access the Dataset, it automatically merges the files from all parent versions
|
||||
in a fully automatic and transparent process, as if the files were always part of the requested Dataset.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user