Organize hyperparameter sweeps
Condensed content, removed emojis, fixed markdown titles sizes, etc.
Check out this pull request on ![]()
See visual diffs & provide feedback on Jupyter Notebooks.
Powered by ReviewNB
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
Dockerfileto thewandb/examples/examplesfolder (where non-Colab examples reside). - Using
pip installas the primary method to install packages. When callingpipin 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 gpt4is acceptable, but
pip install -qU wandb import wandbis 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/transformersYou don't need to clone, then
cdinto the repo and install it in editable mode.- Avoid referencing specific Colab directories. Google Colab has a
/contentdirectory 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.
- Docker-related activities. If Docker installation is required, consider adding a full example with the corresponding
-
The Jupyter notebook file
.ipynbis 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
cleanand 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/pytorch/Organizing_Hyperparameter_Sweeps_in_PyTorch_with_W&B.ipynb
Can I merge this?
@tcapelle Yes, please. :)
Oh, do we need to clear out this line (kernel spec info): https://github.com/wandb/examples/pull/517/files#diff-df362cc8062e3f79092e816d7a26ebc58d35a950ddbbda11ab608c2bf3162fb7R585