Merge branch 'main' of https://github.com/allegroai/clearml-docs
@ -68,7 +68,8 @@ reproducibility.
|
||||
Information about the dataset can be viewed in the WebApp, in the dataset's [details panel](../../webapp/datasets/webapp_dataset_viewing.md#version-details-panel).
|
||||
In the panel's **CONTENT** tab, you can see a table summarizing version contents, including file names, file sizes, and hashes.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Using the Dataset
|
||||
|
||||
|
@ -79,7 +79,8 @@ After a dataset has been closed, it can no longer be modified. This ensures futu
|
||||
Information about the dataset can be viewed in the WebApp, in the dataset's [details panel](../../webapp/datasets/webapp_dataset_viewing.md#version-details-panel).
|
||||
In the panel's **CONTENT** tab, you can see a table summarizing version contents, including file names, file sizes, and hashes.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Data Ingestion
|
||||
|
||||
|
@ -361,10 +361,16 @@ You can also use hashed passwords instead of plain-text passwords. To do that:
|
||||
|
||||
### Non-responsive Task Watchdog
|
||||
|
||||
The non-responsive task watchdog monitors tasks that were not updated for a specified time interval, and then
|
||||
the watchdog marks them as `aborted`. The non-responsive experiment watchdog is always active.
|
||||
The non-responsive task watchdog monitors for running tasks that have stopped communicating with the ClearML Server for a specified
|
||||
time interval. If a task remains unresponsive beyond the set threshold, the watchdog marks it as `aborted`.
|
||||
|
||||
Modify the following settings for the watchdog:
|
||||
A task is considered non-responsive if the time since its last communication with the ClearML Server exceeds the
|
||||
configured threshold. The watchdog starts counting after each successful communication with the server. If no further
|
||||
updates are received within the specified time, the task is considered non-responsive. This typically happens if:
|
||||
* The task's main process is stuck but has not exited.
|
||||
* There is a network issue preventing the task from communicating with the server.
|
||||
|
||||
You can configure the following watchdog settings:
|
||||
|
||||
* Watchdog status - enabled / disabled
|
||||
* The time threshold (in seconds) of experiment inactivity (default value is 7200 seconds (2 hours)).
|
||||
@ -372,10 +378,15 @@ Modify the following settings for the watchdog:
|
||||
|
||||
**To configure the non-responsive watchdog for the ClearML Server:**
|
||||
|
||||
1. In the ClearML Server `/opt/clearml/config/services.conf` file, add or edit the `tasks.non_responsive_tasks_watchdog`
|
||||
section and specify the watchdog settings.
|
||||
1. Open the ClearML Server `/opt/clearml/config/services.conf` file.
|
||||
|
||||
:::tip
|
||||
If the `services.conf` file does not exist, create your own in ClearML Server's `/opt/clearml/config` directory (or
|
||||
an alternate folder you configured).
|
||||
:::
|
||||
|
||||
1. Add or edit the `tasks.non_responsive_tasks_watchdog` section and specify the watchdog settings. For example:
|
||||
|
||||
For example:
|
||||
```
|
||||
tasks {
|
||||
non_responsive_tasks_watchdog {
|
||||
@ -389,11 +400,6 @@ Modify the following settings for the watchdog:
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
:::tip
|
||||
If the `services.conf` file does not exist, create your own in ClearML Server's `/opt/clearml/config` directory (or
|
||||
an alternate folder you configured), and input the modified configuration
|
||||
:::
|
||||
|
||||
1. Restart ClearML Server.
|
||||
|
||||
|
@ -57,24 +57,28 @@ Logger.current_logger().report_scalar(
|
||||
|
||||
These scalars can be visualized in plots, which appear in the ClearML web UI, in the task's **SCALARS** tab.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Hyperparameters
|
||||
|
||||
ClearML automatically logs command line options defined with `argparse`. They appear in **CONFIGURATION** **>** **HYPERPARAMETERS** **>** **Args**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Console
|
||||
|
||||
Text printed to the console for training progress, as well as all other console output, appear in **CONSOLE**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Artifacts
|
||||
|
||||
Models created by the task appear in the task's **ARTIFACTS** tab. ClearML automatically logs and tracks models
|
||||
and any snapshots created using PyTorch.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
|
@ -31,4 +31,5 @@ the `examples` project. This starts the parameter search, and creates the tasks:
|
||||
|
||||
When these tasks are completed, their [results can be compared](../../webapp/webapp_exp_comparing.md).
|
||||
|
||||

|
||||

|
||||

|
@ -34,7 +34,8 @@ Task.current_task().upload_artifact(
|
||||
|
||||
All of these artifacts appear in the main Task under **ARTIFACTS** **>** **OTHER**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Scalars
|
||||
|
||||
@ -54,7 +55,8 @@ Task.current_task().get_logger().report_scalar(
|
||||
|
||||
The single scalar plot for loss appears in **SCALARS**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Hyperparameters
|
||||
|
||||
@ -69,12 +71,15 @@ Task.current_task().connect(param)
|
||||
|
||||
All the hyperparameters appear in **CONFIGURATION** **>** **HYPERPARAMETERS**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Console
|
||||
|
||||
Output to the console, including the text messages printed from the main Task object and each subprocess appear in **CONSOLE**.
|
||||
|
||||

|
||||

|
||||

|
@ -26,14 +26,17 @@ Task.current_task().connect(additional_parameters)
|
||||
|
||||
Command line options appear in **CONFIGURATION** **>** **HYPERPARAMETERS** **>** **Args**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
Parameter dictionaries appear in **General**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Console
|
||||
|
||||
Output to the console, including the text messages from the Task in each subprocess, appear in **CONSOLE**.
|
||||
|
||||

|
||||

|
||||

|
@ -15,25 +15,30 @@ The example script does the following:
|
||||
ClearML automatically captures scalars logged by CatBoost. These scalars can be visualized in plots, which appear in the
|
||||
[ClearML web UI](../../../webapp/webapp_overview.md), in the task's **SCALARS** tab.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Hyperparameters
|
||||
ClearML automatically logs command line options defined with argparse. They appear in **CONFIGURATIONS > HYPERPARAMETERS > Args**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Console
|
||||
Text printed to the console for training progress, as well as all other console output, appear in **CONSOLE**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Artifacts
|
||||
Models created by the task appear in the task's **ARTIFACTS** tab. ClearML automatically logs and tracks
|
||||
models created using CatBoost.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
Clicking on the model name takes you to the [model's page](../../../webapp/webapp_model_viewing.md), where you can view
|
||||
the model's details and access the model.
|
||||
|
||||

|
||||

|
||||

|
||||
|
@ -18,16 +18,19 @@ The example code does the following:
|
||||
|
||||
ClearML automatically logs the histogram output to TensorBoard. They appear in **PLOTS**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Plots
|
||||
|
||||
Histograms output to TensorBoard. They appear in **PLOTS**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Logs
|
||||
|
||||
Text printed to the console for training progress, as well as all other console output, appear in **CONSOLE**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
@ -36,7 +36,8 @@ ClearML captures all of the `TrainingArguments` passed to the Trainer.
|
||||
|
||||
View these parameters in the task's **CONFIGURATION** tab **> Hyperparameters** section.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
|
||||
### Models
|
||||
@ -47,10 +48,12 @@ variable is set to `True`.
|
||||
ClearML automatically captures the model snapshots created by the Trainer, and saves them as artifacts. View the snapshots in the
|
||||
task's **ARTIFACTS** tab.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
### Scalars
|
||||
|
||||
ClearML automatically captures the Trainer's scalars, which can be viewed in the task's **Scalars** tab.
|
||||
|
||||

|
||||

|
||||

|
||||
|
@ -83,18 +83,22 @@ if CONDITION:
|
||||
## WebApp
|
||||
The model appears in the task's **ARTIFACTS** tab.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
Clicking on the model name takes you to the [model's page](../../../webapp/webapp_model_viewing.md), where you can view the
|
||||
model's details and access the model.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
The model's **NETWORK** tab displays its configuration.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
The model's **LABELS** tab displays its label enumeration.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
|
@ -35,7 +35,8 @@ Task.current_task().upload_artifact(
|
||||
|
||||
All of these artifacts appear in the main Task, **ARTIFACTS** **>** **OTHER**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Scalars
|
||||
|
||||
@ -54,7 +55,8 @@ Task.current_task().get_logger().report_scalar(
|
||||
|
||||
The single scalar plot for loss appears in **SCALARS**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Hyperparameters
|
||||
|
||||
@ -69,7 +71,8 @@ Task.current_task().connect(param)
|
||||
|
||||
Command line options appear in **CONFIGURATION** **>** **HYPERPARAMETERS** **>** **Args**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
Parameter dictionaries appear in the **General** section of **HYPERPARAMETERS**.
|
||||
|
||||
@ -78,10 +81,12 @@ param = {'worker_{}_stuff'.format(dist.get_rank()): 'some stuff ' + str(randint(
|
||||
Task.current_task().connect(param)
|
||||
```
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Log
|
||||
|
||||
Output to the console, including the text messages printed from the main Task object and each subprocess, appears in **CONSOLE**.
|
||||
|
||||

|
||||

|
||||

|
@ -14,15 +14,18 @@ The example does the following:
|
||||
|
||||
The images shown in the example script's `imshow` function appear according to metric in **DEBUG SAMPLES**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
Select a debug sample by metric.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
Open the debug sample in the image viewer.
|
||||
Click a debug sample to view it in the image viewer.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
|
||||
|
||||
|
@ -36,28 +36,33 @@ Logger.current_logger().report_scalar(
|
||||
These scalars can be visualized in plots, which appear in the ClearML [web UI](../../../webapp/webapp_overview.md),
|
||||
in the task's **SCALARS** tab.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Hyperparameters
|
||||
|
||||
ClearML automatically logs command line options defined with `argparse`. They appear in **CONFIGURATION** **>** **HYPERPARAMETERS** **>** **Args**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Console
|
||||
|
||||
Text printed to the console for training progress, as well as all other console output, appear in **CONSOLE**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Artifacts
|
||||
|
||||
Models created by the task appear in the task's **ARTIFACTS** tab. ClearML automatically logs and tracks models
|
||||
and any snapshots created using PyTorch.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
Clicking on the model name takes you to the [model's page](../../../webapp/webapp_model_viewing.md), where you can view
|
||||
the model's details and access the model.
|
||||
|
||||

|
||||

|
||||

|
@ -18,34 +18,40 @@ In the example script, the `train` and `test` functions call the TensorBoard `Su
|
||||
These scalars, along with the resource utilization plots, which are titled **:monitor: machine**, appear in the task's
|
||||
page in the [ClearML web UI](../../../webapp/webapp_overview.md) under **SCALARS**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Debug Samples
|
||||
|
||||
ClearML automatically tracks images and text output to TensorFlow. They appear in **DEBUG SAMPLES**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Hyperparameters
|
||||
|
||||
ClearML automatically logs TensorFlow Definitions. They appear in **CONFIGURATION** **>** **HYPERPARAMETERS** **>** **TF_DEFINE**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Console
|
||||
|
||||
Text printed to the console for training progress, as well as all other console output, appear in **CONSOLE**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Artifacts
|
||||
|
||||
Models created by the task appear in the task's **ARTIFACTS** tab. ClearML automatically logs and tracks
|
||||
models and any snapshots created using PyTorch.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
Clicking on a model's name takes you to the [model's page](../../../webapp/webapp_model_viewing.md), where you can view
|
||||
the model's details and access the model.
|
||||
|
||||

|
||||

|
||||

|
@ -18,29 +18,34 @@ The loss and accuracy metric scalar plots, along with the resource utilization p
|
||||
appear in the task's page in the [web UI](../../../webapp/webapp_overview.md), under **SCALARS**.
|
||||
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Hyperparameters
|
||||
|
||||
ClearML automatically logs command line options defined with `argparse`. They appear in **CONFIGURATION** **>**
|
||||
**HYPERPARAMETERS** **>** **Args**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Log
|
||||
|
||||
Text printed to the console for training progress, as well as all other console output, appear in **CONSOLE**.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Artifacts
|
||||
|
||||
Models created by the task appear in the task's **ARTIFACTS** tab. ClearML automatically logs and tracks
|
||||
models and any snapshots created using PyTorch.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
Clicking on the model name takes you to the [model's page](../../../webapp/webapp_model_viewing.md), where you can view
|
||||
the model's details and access the model.
|
||||
|
||||

|
||||

|
||||

|
||||
|
@ -11,10 +11,12 @@ associated with the `examples` project.
|
||||
|
||||
The debug sample images appear according to metric, in the task's **DEBUG SAMPLES** tab.
|
||||
|
||||

|
||||

|
||||

|
||||
|
||||
## Hyperparameters
|
||||
|
||||
ClearML automatically logs TensorFlow Definitions. They appear in **CONFIGURATION** **>** **HYPERPARAMETERS** **>** **TF_DEFINE**.
|
||||
|
||||

|
||||

|
||||

|
Before Width: | Height: | Size: 40 KiB After Width: | Height: | Size: 40 KiB |
BIN
docs/img/examples_catboost_artifacts_dark.png
Normal file
After Width: | Height: | Size: 40 KiB |
Before Width: | Height: | Size: 30 KiB After Width: | Height: | Size: 31 KiB |
BIN
docs/img/examples_catboost_configurations_dark.png
Normal file
After Width: | Height: | Size: 31 KiB |
Before Width: | Height: | Size: 222 KiB After Width: | Height: | Size: 136 KiB |
BIN
docs/img/examples_catboost_console_dark.png
Normal file
After Width: | Height: | Size: 138 KiB |
Before Width: | Height: | Size: 50 KiB After Width: | Height: | Size: 45 KiB |
BIN
docs/img/examples_catboost_model_dark.png
Normal file
After Width: | Height: | Size: 60 KiB |
Before Width: | Height: | Size: 62 KiB After Width: | Height: | Size: 63 KiB |
BIN
docs/img/examples_catboost_scalars_dark.png
Normal file
After Width: | Height: | Size: 66 KiB |
Before Width: | Height: | Size: 129 KiB After Width: | Height: | Size: 122 KiB |
BIN
docs/img/examples_data_management_cifar_dataset_dark.png
Normal file
After Width: | Height: | Size: 125 KiB |
Before Width: | Height: | Size: 92 KiB After Width: | Height: | Size: 106 KiB |
BIN
docs/img/examples_hpo_parallel_coordinates_dark.png
Normal file
After Width: | Height: | Size: 119 KiB |
Before Width: | Height: | Size: 43 KiB After Width: | Height: | Size: 42 KiB |
BIN
docs/img/examples_model_update_artifacts_dark.png
Normal file
After Width: | Height: | Size: 42 KiB |
Before Width: | Height: | Size: 30 KiB After Width: | Height: | Size: 30 KiB |
BIN
docs/img/examples_model_update_labels_dark.png
Normal file
After Width: | Height: | Size: 31 KiB |
Before Width: | Height: | Size: 52 KiB After Width: | Height: | Size: 42 KiB |
BIN
docs/img/examples_model_update_model_dark.png
Normal file
After Width: | Height: | Size: 42 KiB |
Before Width: | Height: | Size: 29 KiB After Width: | Height: | Size: 27 KiB |
BIN
docs/img/examples_model_update_network_dark.png
Normal file
After Width: | Height: | Size: 27 KiB |
Before Width: | Height: | Size: 32 KiB After Width: | Height: | Size: 34 KiB |
BIN
docs/img/examples_pytorch_distributed_example_01_dark.png
Normal file
After Width: | Height: | Size: 34 KiB |
Before Width: | Height: | Size: 60 KiB |
Before Width: | Height: | Size: 60 KiB After Width: | Height: | Size: 63 KiB |
BIN
docs/img/examples_pytorch_distributed_example_02_dark.png
Normal file
After Width: | Height: | Size: 63 KiB |
Before Width: | Height: | Size: 179 KiB After Width: | Height: | Size: 113 KiB |
BIN
docs/img/examples_pytorch_distributed_example_06_dark.png
Normal file
After Width: | Height: | Size: 118 KiB |
Before Width: | Height: | Size: 141 KiB After Width: | Height: | Size: 118 KiB |
BIN
docs/img/examples_pytorch_distributed_example_08_dark.png
Normal file
After Width: | Height: | Size: 124 KiB |
Before Width: | Height: | Size: 69 KiB After Width: | Height: | Size: 64 KiB |
BIN
docs/img/examples_pytorch_distributed_example_09_dark.png
Normal file
After Width: | Height: | Size: 64 KiB |
Before Width: | Height: | Size: 50 KiB After Width: | Height: | Size: 221 KiB |
BIN
docs/img/examples_pytorch_matplotlib_02_dark.png
Normal file
After Width: | Height: | Size: 222 KiB |
Before Width: | Height: | Size: 40 KiB After Width: | Height: | Size: 196 KiB |
BIN
docs/img/examples_pytorch_matplotlib_02a_dark.png
Normal file
After Width: | Height: | Size: 196 KiB |
Before Width: | Height: | Size: 704 KiB After Width: | Height: | Size: 981 KiB |
BIN
docs/img/examples_pytorch_matplotlib_02b_dark.png
Normal file
After Width: | Height: | Size: 975 KiB |
Before Width: | Height: | Size: 45 KiB After Width: | Height: | Size: 50 KiB |
BIN
docs/img/examples_pytorch_mnist_01_dark.png
Normal file
After Width: | Height: | Size: 50 KiB |
Before Width: | Height: | Size: 34 KiB After Width: | Height: | Size: 40 KiB |
BIN
docs/img/examples_pytorch_mnist_02_dark.png
Normal file
After Width: | Height: | Size: 40 KiB |
Before Width: | Height: | Size: 49 KiB After Width: | Height: | Size: 46 KiB |
BIN
docs/img/examples_pytorch_mnist_03_dark.png
Normal file
After Width: | Height: | Size: 46 KiB |
Before Width: | Height: | Size: 185 KiB After Width: | Height: | Size: 106 KiB |
BIN
docs/img/examples_pytorch_mnist_06_dark.png
Normal file
After Width: | Height: | Size: 105 KiB |
Before Width: | Height: | Size: 67 KiB After Width: | Height: | Size: 73 KiB |
BIN
docs/img/examples_pytorch_mnist_07_dark.png
Normal file
After Width: | Height: | Size: 72 KiB |
Before Width: | Height: | Size: 42 KiB After Width: | Height: | Size: 44 KiB |
BIN
docs/img/examples_pytorch_tensorboard_01_dark.png
Normal file
After Width: | Height: | Size: 44 KiB |
Before Width: | Height: | Size: 44 KiB After Width: | Height: | Size: 47 KiB |
BIN
docs/img/examples_pytorch_tensorboard_02_dark.png
Normal file
After Width: | Height: | Size: 47 KiB |
Before Width: | Height: | Size: 62 KiB After Width: | Height: | Size: 41 KiB |
BIN
docs/img/examples_pytorch_tensorboard_03_dark.png
Normal file
After Width: | Height: | Size: 41 KiB |
Before Width: | Height: | Size: 210 KiB After Width: | Height: | Size: 103 KiB |
BIN
docs/img/examples_pytorch_tensorboard_06_dark.png
Normal file
After Width: | Height: | Size: 108 KiB |
Before Width: | Height: | Size: 86 KiB After Width: | Height: | Size: 95 KiB |
BIN
docs/img/examples_pytorch_tensorboard_07_dark.png
Normal file
After Width: | Height: | Size: 95 KiB |
Before Width: | Height: | Size: 27 KiB After Width: | Height: | Size: 35 KiB |
BIN
docs/img/examples_pytorch_tensorboard_08_dark.png
Normal file
After Width: | Height: | Size: 35 KiB |
Before Width: | Height: | Size: 43 KiB After Width: | Height: | Size: 44 KiB |
BIN
docs/img/examples_pytorch_tensorboardx_01_dark.png
Normal file
After Width: | Height: | Size: 45 KiB |
Before Width: | Height: | Size: 198 KiB After Width: | Height: | Size: 118 KiB |
BIN
docs/img/examples_pytorch_tensorboardx_02_dark.png
Normal file
After Width: | Height: | Size: 121 KiB |
Before Width: | Height: | Size: 87 KiB After Width: | Height: | Size: 81 KiB |
BIN
docs/img/examples_pytorch_tensorboardx_03_dark.png
Normal file
After Width: | Height: | Size: 80 KiB |
Before Width: | Height: | Size: 35 KiB After Width: | Height: | Size: 38 KiB |
BIN
docs/img/examples_pytorch_tensorboardx_04_dark.png
Normal file
After Width: | Height: | Size: 38 KiB |
Before Width: | Height: | Size: 49 KiB After Width: | Height: | Size: 47 KiB |
BIN
docs/img/examples_pytorch_tensorboardx_model_dark.png
Normal file
After Width: | Height: | Size: 47 KiB |
Before Width: | Height: | Size: 35 KiB After Width: | Height: | Size: 40 KiB |
BIN
docs/img/examples_remote_execution_artifacts_dark.png
Normal file
After Width: | Height: | Size: 40 KiB |
Before Width: | Height: | Size: 77 KiB After Width: | Height: | Size: 84 KiB |
BIN
docs/img/examples_reporting_fastai_01_dark.png
Normal file
After Width: | Height: | Size: 87 KiB |
Before Width: | Height: | Size: 177 KiB After Width: | Height: | Size: 296 KiB |
BIN
docs/img/examples_reporting_fastai_02_dark.png
Normal file
After Width: | Height: | Size: 301 KiB |
Before Width: | Height: | Size: 154 KiB After Width: | Height: | Size: 108 KiB |
BIN
docs/img/examples_reporting_fastai_03_dark.png
Normal file
After Width: | Height: | Size: 112 KiB |
Before Width: | Height: | Size: 32 KiB After Width: | Height: | Size: 34 KiB |
BIN
docs/img/examples_subprocess_example_01_dark.png
Normal file
After Width: | Height: | Size: 34 KiB |
Before Width: | Height: | Size: 93 KiB After Width: | Height: | Size: 88 KiB |
BIN
docs/img/examples_subprocess_example_01a_dark.png
Normal file
After Width: | Height: | Size: 88 KiB |