wandb artifact putcommand to upload an artifact to the W&B server outside of a W&B run. Provide the name of the project you want the artifact to belong to along with the name of the artifact (
project/artifact_name).Optionally provide the type (
PATHin the code snippet below with the file path of the artifact you want to upload.
mnist/we have our dataset, a collection of images. Lets track it with an artifact:
mnist:latestlooks and behaves similarly to a regular artifact. The only difference is that the artifact only consists of metadata about the S3/GCS object such as its ETag, size, and version ID (if object versioning is enabled on the bucket).
/mountwith the following structure:
mnist/we have our dataset, a collection of images. Let's track it with an artifact:
max_objects=in calls to
file://prefix that denotes the use of filesystem references. The second is the path to our dataset,
mnist:latestlooks and acts just like a regular artifact. The only difference is that the artifact only consists of metadata about the files, such as their sizes and MD5 checksums. The files themselves never leave your system.
download()operation copies the files from the referenced paths to construct the artifact directory. In the above example, the contents of
/mount/datasets/mnistwill be copied into the directory
artifacts/mnist:v0/. If an artifact contains a reference to a file that was overwritten, then
download()will throw an error as the artifact can no longer be reconstructed.