Use the W&B Python SDK to construct artifacts from W&B Runs. You can add files, directories, URIs, and files from parallel runs to artifacts. After you add a file to an artifact, save the artifact to the W&B Server or your own private server. Each artifact is associated with a run.
For information on how to track external files, such as files stored in Amazon S3, see the Track external files page.
Construct an artifact
Construct a W&B artifact in three steps:
- Create an artifact Python object with
wandb.Artifact()
- Add one or more files to the artifact
- Save your artifact to the W&B server
Create an artifact Python object with wandb.Artifact()
Initialize the wandb.Artifact() class to create an artifact object. Specify the following parameters:
- Name: The name of your artifact. The name should be unique, descriptive, and memorable.
- Type: The type of artifact. The type should be short, descriptive, and correspond to a single step of your machine learning pipeline. Common artifact types include
'dataset' or 'model'.
W&B uses the name and type you provide to create a directed acyclic graph in the W&B App. See Explore and traverse artifact graphs for more information.
Artifacts can’t have the same name, regardless of type. In other words, you can’t create an artifact named cats of type dataset and another artifact with the same name of type model.
You can optionally provide a description and metadata when you initialize an artifact object. For more information about available attributes and parameters, see the wandb.Artifact class definition in the Python SDK Reference Guide.
Copy and paste the following code snippet to create an artifact object. Replace the [NAME] and [TYPE] placeholders with your own values:
Add one or more files to the artifact
Add files, directories, external URI references (such as Amazon S3) and more to your artifact object.
To add a single file, use the artifact object’s Artifact.add_file() method:
To add a directory, use the Artifact.add_dir() method:
See Add files to an artifact, for more information about adding different file types to an artifact.
Save your artifact to the W&B server
Use the run object’s wandb.Run.log_artifact() method to save the artifact.
When to use wandb.Run.log_artifact() or Artifact.save()
- Use
wandb.Run.log_artifact() to create a new artifact and associate it with a specific run.
- Use
Artifact.save() to update an existing artifact without creating a new run.
Putting this all together, the following code snippet shows how to create a dataset artifact, add a file to the artifact, and save the artifact to W&B:
Each time you log an artifact with the same name and type, W&B creates a new version of that artifact. For more information, see Create a new artifact version.
W&B performs wandb.Run.log_artifact() calls asynchronously for faster uploads. This can cause surprising behavior when you log artifacts in a loop. For example:The artifact version v0 is not guaranteed to have an index of 0 in its metadata because W&B might log artifacts in an arbitrary order.
Add files to an artifact
The following sections show how to add different types of objects to an artifact. Assume you have a directory with the following structure as you read through the examples:
Add a single file
Use wandb.Artifact.add_file() to add a single local file to an artifact. Provide the local path to the file as the local_path parameter:
For example, suppose you had a file called 'hello.txt' in your working local directory.
The artifact now has the following content:
Optionally, pass a different name to the name parameter to rename the file within the artifact object itself. Continuing the previous example:
The artifact is stored as:
The following table shows how different API calls produce different artifact contents:
Add multiple files
Use the wandb.Artifact.add_dir() method to add multiple files from a local directory to an artifact. Provide the local path to the directory as the local_path parameter.
The following table shows how different API calls produce different artifact contents:
Add a URI reference
To point an artifact to content stored outside of W&B (such as in an object store) without copying the underlying bytes, add an external URI reference with the wandb.Artifact.add_reference() method. Artifacts track checksums and other information for reproducibility if the URI has a scheme that the W&B library supports. Replace the 'uri' string with your own URI. Optionally pass the desired path within the artifact for the name parameter.
Artifacts support the following URI schemes:
http(s)://: A path to a file accessible over HTTP. The artifact tracks checksums in the form of etags and size metadata if the HTTP server supports the ETag and Content-Length response headers.
s3://: A path to an object or object prefix in S3. The artifact tracks checksums and versioning information (if the bucket has object versioning enabled) for the referenced objects. W&B expands object prefixes to include the objects under the prefix, up to a maximum of 10,000 objects.
gs://: A path to an object or object prefix in GCS. The artifact tracks checksums and versioning information (if the bucket has object versioning enabled) for the referenced objects. W&B expands object prefixes to include the objects under the prefix, up to a maximum of 10,000 objects.
The following table shows how different API calls produce different artifact contents:
Add files to artifacts from parallel runs
For large datasets or distributed training, multiple parallel runs might need to contribute to a single artifact.
The following code snippet shows how to use the W&B Public API to list the files in a run, including their names and URLs. Replace the [ENTITY]/[PROJECT]/[RUN-ID] placeholder with your own values:
See the File class for more information about available attributes and methods.