wandb.init()
, start a new cell with %%wandb
to see live graphs in the notebook. If you run this cell multiple times, data will be appended to the run.%wandb
magic:%%wandb
or %wandb
magics, after running wandb.init()
you can end any cell with wandb.run
to show in-line graphs, or call ipython.display(...)
on any report, sweep, or run object returned from our apis.wandb.init
for the first time in a Colab, we automatically authenticate your runtime if you're currently logged in to W&B in your browser. On the overview tab of your run page, you'll see a link to the Colab.%wandb
magic accepts a path to your project, sweeps or reports and will render the W&B interface directly in the notebook.wandb docker --jupyter
to launch a docker container, mount your code in it, ensure Jupyter is installed, and launch on port 8888.wandb.init
is called to mark a run as "finished". That allows you to run multiple cells (say, one to set up data, one to train, one to test) in whatever order you like and have them all log to the same run. If you turn on code saving in settings, you'll also log the cells that were executed, in order and in the state in which they were run, enabling you to reproduce even the most non-linear of pipelines. To mark a run as complete manually in a Jupyter notebook, call run.finish
.wandb.login
:INFO SenderThread:11484 [sender.py:finish():979]
in your notebook, you can disable those with the following:WANDB_NOTEBOOK_NAME
?"Failed to query for notebook name, you can set it manually with the WANDB_NOTEBOOK_NAME environment variable,"
you can resolve it by setting the environment variable. There's multiple ways to do so: