Registry tutorial - basic

[ngrayluna]

W&B Registry tutorial, example using simple PyTorch neural network for classifying animal classes.

The purpose of this notebook is to show how to use registry with the minimal amount of boiler plate code (so as to hopefully not drown out the W&B-specific portions of the notebook).

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[github-actions]

Thanks for contributing to wandb/examples!
We appreciate your efforts in opening a PR for the examples repository. Our goal is to ensure a smooth and enjoyable experience for you 😎.

Guidelines

The examples repo is regularly tested against the ever-evolving ML stack. To facilitate our work, please adhere to the following guidelines:

• Notebook naming: You can use a combination of snake_case and CamelCase for your notebook name. Avoid using spaces (replace them with _) and special characters (&%$?). For example:

Cool_Keras_integration_example_with_weights_and_biases.ipynb 

is acceptable, but

Cool Keras Example with W&B.ipynb

is not. Avoid spaces and the & character. To refer to W&B, you can use: weights_and_biases or just wandb (it's our library, after all!)

• Managing dependencies within the notebook: You may need to set up dependencies to ensure that your code works. Please avoid the following practices:

  • Docker-related activities. If Docker installation is required, consider adding a full example with the corresponding Dockerfile to the wandb/examples/examples folder (where non-Colab examples reside).
  • Using pip install as the primary method to install packages. When calling pip in a cell, avoid performing other tasks. We automatically filter these types of cells, and executing other actions might break the automatic testing of the notebooks. For example,

  pip install -qU wandb transformers gpt4
  

  is acceptable, but

  pip install -qU wandb
  import wandb

  is not.

  • Installing packages from a GitHub branch. Although it's acceptable 😎 to directly obtain the latest bleeding-edge libraries from GitHub, did you know that you can install them like this:

  !pip install -q git+https://github.com/huggingface/transformers

  You don't need to clone, then cd into the repo and install it in editable mode.

  • Avoid referencing specific Colab directories. Google Colab has a /content directory where everything resides. Avoid explicitly referencing this directory because we test our notebooks with pure Jupyter (without Colab). Instead, use relative paths to make the notebook reproducible.

• The Jupyter notebook file .ipynb is nothing more than a JSON file with primarily two types of cells: markdown and code. There is also a bunch of other metadata specific to Google Colab. We have a set of tools to ensure proper notebook formatting. These tools can be found at wandb/nb_helpers.

Before merging, wait for a maintainer to clean and format the notebooks you're adding. You can tag @tcapelle.

Before marking the PR as ready for review, please run your notebook one more time. Restart the Colab and run all. We will provide you with links to open the Colabs below

The following colabs were changed
-colabs/wandb_registry/zoo_wandb.ipynb

[tcapelle]

Added a name, a tracker, colab badge and clean up =)

[tcapelle]

[class_labels.get(x) for x in predicted.numpy()]

Reply via ReviewNB

[tcapelle]

what about this commented pieces?

Reply via ReviewNB

[abraham-leal]

Overall awesome, lots of stylistic suggestions for readability. Thank you!

[abraham-leal]

It'd be cleaner to ask the user to input a WANDB_API_KEY upstream to not block them in the middle of running the notebook interactively?

[abraham-leal]

Context manager?

[abraham-leal]

Would be helpful to explain how / why you arrived at this path from .download()

[abraham-leal]

Context manager?

[rratshin-wandb]

• Is it possible to use an ORG_NAME not associated with the bug bash? Actually wondering if we need to just use <INSERT YOUR ORG_NAME HERE> syntax as this will only actually work if you have a key associated with that org (please correct me if I am wrong about this).

Reply via ReviewNB

[rratshin-wandb]

• Is it possible to use an ORG_NAME not associated with the bug bash? Actually wondering if we need to just use <INSERT YOUR ORG_NAME HERE> syntax as this will only actually work if you have a key associated with that org (please correct me if I am wrong about this).

Reply via ReviewNB

[ngrayluna]

Pushed edits, things to resolve (see Slack thread for answers)

1. Add action that replaces org variable strings w/ actual org name for CI
2. Once tags ship (SDK) add that to notebook

Note: Might need to update this notebook if we hide org names.