|
4 | 4 | "cell_type": "markdown", |
5 | 5 | "metadata": {}, |
6 | 6 | "source": [ |
7 | | - "# Dreadnode Artifact Logging\n", |
| 7 | + "## Dreadnode Artifact Logging\n", |
8 | 8 | "\n", |
9 | | - "This notebook demonstrates how to log artifacts (files and directories) to your Dreadnode platform projects. Artifacts are preserved with their original structure and can be used to track assets.\n", |
10 | | - "\n", |
11 | | - "### Benefits of Artifact Logging\n", |
12 | | - "\n", |
13 | | - "Artifact logging provides several key benefits for your workflow:\n", |
14 | | - "\n", |
15 | | - "- **Reproducibility**: Ensure your runs can reference the exact files used.\n", |
16 | | - "- **Organization**: Maintain the structure of complex file hierarchies.\n", |
17 | | - "- **Efficiency**: Content-based deduplication saves storage space.\n", |
18 | | - "- **Traceability**: Connect inputs, outputs, and code in one place.\n" |
| 9 | + "This notebook demonstrates how to log artifacts (files and directories) to your Dreadnode platform projects. Artifacts are preserved with their original structure and can be used to track assets.\n" |
19 | 10 | ] |
20 | 11 | }, |
21 | 12 | { |
|
36 | 27 | "cell_type": "markdown", |
37 | 28 | "metadata": {}, |
38 | 29 | "source": [ |
39 | | - "## Logging Entire Directory as an Artifact\n", |
| 30 | + "### Logging Entire Directory as an Artifact\n", |
40 | 31 | "\n", |
41 | 32 | "When you log a directory, Dreadnode SDK will preserve the entire directory structure and all files within it. This could be useful for keeping track of datasets, model checkpoints, or collections of related files in a project.\n" |
42 | 33 | ] |
|
59 | 50 | "cell_type": "markdown", |
60 | 51 | "metadata": {}, |
61 | 52 | "source": [ |
62 | | - "## Logging a Single File as an Artifact\n", |
| 53 | + "### Logging a Single File as an Artifact\n", |
63 | 54 | "\n", |
64 | 55 | "For individual files like pkl, image, or standalone models, you can log them directly:\n" |
65 | 56 | ] |
|
0 commit comments