Merge branch 'main' of https://github.com/allegroai/clearml-docs
@ -169,7 +169,7 @@ clearml-session --upload-files /mnt/data/stuff
|
||||
You can upload your files in conjunction with the `--store-workspace` option to easily move workloads between local
|
||||
development machines and remote machines with persistent workspace synchronization. See [Storing and Synchronizing Workspace](#storing-and-synchronizing-workspace).
|
||||
|
||||
### Starting a Debugging Session
|
||||
### Starting a Debugging Session
|
||||
You can debug previously executed tasks registered in the ClearML system on a remote interactive session.
|
||||
Input into `clearml-session` the ID of a Task to debug, then `clearml-session` clones the task's git repository and
|
||||
replicates the environment on a remote machine. Then the code can be interactively executed and debugged on JupyterLab / VS Code.
|
||||
|
@ -11,10 +11,11 @@ In Machine Learning, you are very likely dealing with a gargantuan amount of dat
|
||||
which you then need to be able to share, reproduce, and track.
|
||||
|
||||
ClearML Data Management solves two important challenges:
|
||||
- Accessibility - Making data easily accessible from every machine,
|
||||
- Accessibility - Making data easily accessible from every machine
|
||||
- Versioning - Linking data and tasks for better **traceability**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
**We believe Data is not code**. It should not be stored in a git tree, because progress on datasets is not always linear.
|
||||
Moreover, it can be difficult and inefficient to find on a git tree the commit associated with a certain version of a dataset.
|
||||
|
@ -253,7 +253,8 @@ task's status. If a task failed or was aborted, you can view how much progress i
|
||||
|
||||
<div class="max-w-50">
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
</div>
|
||||
|
||||
|
@ -3,7 +3,7 @@ title: Executable Task Containers
|
||||
---
|
||||
|
||||
This tutorial demonstrates using [`clearml-agent`](../../clearml_agent.md)'s [`build`](../../clearml_agent/clearml_agent_ref.md#build)
|
||||
command to package a task into an executable container. In this example, you will build a Container image that, when
|
||||
command to package a task into an executable container. In this example, you will build a container image that, when
|
||||
run, will automatically execute the [keras_tensorboard.py](https://github.com/allegroai/clearml/blob/master/examples/frameworks/keras/keras_tensorboard.py)
|
||||
script.
|
||||
|
||||
|
Before Width: | Height: | Size: 103 KiB After Width: | Height: | Size: 84 KiB |
BIN
docs/img/fundamentals_task_progress_dark.png
Normal file
After Width: | Height: | Size: 84 KiB |
Before Width: | Height: | Size: 1.5 MiB After Width: | Height: | Size: 1.5 MiB |
Before Width: | Height: | Size: 1.5 MiB After Width: | Height: | Size: 1.5 MiB |
Before Width: | Height: | Size: 102 KiB After Width: | Height: | Size: 100 KiB |
Before Width: | Height: | Size: 103 KiB After Width: | Height: | Size: 103 KiB |
Before Width: | Height: | Size: 40 KiB After Width: | Height: | Size: 52 KiB |
Before Width: | Height: | Size: 41 KiB After Width: | Height: | Size: 54 KiB |
Before Width: | Height: | Size: 191 KiB |
Before Width: | Height: | Size: 188 KiB After Width: | Height: | Size: 221 KiB |
Before Width: | Height: | Size: 33 KiB After Width: | Height: | Size: 33 KiB |
Before Width: | Height: | Size: 34 KiB After Width: | Height: | Size: 34 KiB |
Before Width: | Height: | Size: 186 KiB After Width: | Height: | Size: 220 KiB |
Before Width: | Height: | Size: 23 KiB After Width: | Height: | Size: 43 KiB |
Before Width: | Height: | Size: 23 KiB After Width: | Height: | Size: 42 KiB |
Before Width: | Height: | Size: 166 KiB After Width: | Height: | Size: 123 KiB |
Before Width: | Height: | Size: 166 KiB After Width: | Height: | Size: 126 KiB |
Before Width: | Height: | Size: 171 KiB After Width: | Height: | Size: 128 KiB |
Before Width: | Height: | Size: 168 KiB After Width: | Height: | Size: 128 KiB |
Before Width: | Height: | Size: 199 KiB After Width: | Height: | Size: 153 KiB |
Before Width: | Height: | Size: 191 KiB After Width: | Height: | Size: 149 KiB |
@ -67,9 +67,13 @@ On the pipeline run panel, view the **RUN INFO** which shows:
|
||||
* Produced Artifacts
|
||||
* Output Models
|
||||
|
||||
<div class="max-w-25">
|
||||
|
||||

|
||||

|
||||
|
||||
</div>
|
||||
|
||||
To view a run's complete information, click **Full details**, which will open the pipeline's controller [task page](../webapp_exp_track_visual.md).
|
||||
View each list's complete details in the pipeline task's corresponding tabs:
|
||||
* **PARAMETERS** list > **CONFIGURATION** tab
|
||||
|
@ -44,7 +44,7 @@ The model table contains the following columns:
|
||||
| *Metadata* | User defined metadata key column. Available options depend upon the models in the table. | String |
|
||||
|
||||
|
||||
## Customizing the Model table
|
||||
## Customizing the Model Table
|
||||
|
||||
The model table is customizable. Changes are persistent (cached in the browser) and represented in the URL, so customized settings
|
||||
can be saved in a browser bookmark and shared with other ClearML users to collaborate.
|
||||
|