ClearML/clearml-docs
1
0
Fork 0
mirror of https://github.com/clearml/clearml-docs synced 2025-06-26 18:17:44 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Small edits (#476)

Browse Source
This commit is contained in:
pollfly
2023-02-16 12:17:53 +02:00
committed by GitHub
parent 5458f8036b
commit 2cf096f7ec
27 changed files with 64 additions and 64 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/faq.md
View File

@@ -364,7 +364,7 @@ Your firewall may be preventing the connection. Try one of the following solutio
**How do I modify experiment names once they have been created?**
An experiment's name is a user-controlled property, which can be accessed via the `Task.name` variable. This allows you to use meaningful naming schemes for easily filtering and comparing of experiments.
An experiment's name is a user-controlled property, which can be accessed via the `Task.name` variable. This lets you use meaningful naming schemes for easily filtering and comparing of experiments.
For example, to distinguish between different experiments, you can append the task ID to the task name:
```python
@@ -469,7 +469,7 @@ After thirty minutes, it remains unchanged.
**Can I control what ClearML automatically logs?** <a id="controlling_logging"></a>
Yes! ClearML allows you to control automatic logging for `stdout`, `stderr`, and frameworks when initializing a Task
Yes! ClearML lets you control automatic logging for `stdout`, `stderr`, and frameworks when initializing a Task
by calling the [`Task.init`](references/sdk/task.md#taskinit) method.
To control a Task's framework logging, use the `auto_connect_frameworks` parameter. Turn off all automatic logging by setting the
@@ -629,7 +629,7 @@ experiment info panel > EXECUTION tab.
**I read there is a feature for centralized model storage. How do I use it?** <a id="centralized-model-storage"></a>
When calling [Task.init](references/sdk/task.md#taskinit),
providing the `output_uri` parameter allows you to specify the location in which model checkpoints (snapshots) will be stored.
providing the `output_uri` parameter lets you specify the location in which model checkpoints (snapshots) will be stored.
For example, to store model checkpoints (snapshots) in `/mnt/shared/folder`: