wandb.init
do to my training process?wandb.init()
is called from your training script an API call is made to create a run object on our servers. A new process is started to stream and collect metrics, thereby keeping all threads and logic out of your primary process. Your script runs normally and writes to local files, while the separate process streams them to our servers along with system metrics. You can always turn off streaming by running wandb off
from your training directory, or setting the WANDB_MODE
environment variable to offline
.wandb.init(mode="disabled")
or by setting WANDB_MODE=disabled
you will make wandb act like a NOOP which is perfect for testing your code.wandb.init(mode=“disabled”)
does not prevent wandb
from saving artifacts to WANDB_CACHE_DIR
wandb.config.update(...)
to associate a dataset with a training run. W&B does not store any data unless wandb.save
is called with the local file name.wandb.run.save()
and then get the name with wandb.run.name
..log()
and .summary
?wandb.log
every time the accuracy changes. Usually, you can just use .log. wandb.log()
will also update the summary value by default unless you have set the summary manually for that metricWANDB_MODE=offline
case where you can sync the data after it's been logged..wandb
file that is the datastore above. If you're also logging images, we write them to media/images
in that directory before uploading them to cloud storage.grant_type
to implicit
flow.WANDB_USERNAME
./teams/<your-team-name>
where you invite new team members. Select service and click create to add a service account.