Skip to content

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

 
 

Latest commit

 

History

623 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

DANDI Notebooks

This repository contains example notebooks associated with datasets, conference tools, or more generally notebooks that illustrate the use of data on DANDI. This repository is cloned into the DANDI JupyterHub environment. Please note that you will need to visit https://dandiarchive.org and sign in once to get access to the JupyterHub.

Submission instructions

To add new notebooks, please send a Pull Request. Submissions should use the following file structure:

example-notebooks/
└── <dandiset id>/
    └── <org or lab name>/
        └── <mnemonic for paper or analysis>/
            ├── notebook.yaml
            ├── requirements.in
            ├── requirements.lock.txt   (generated)
            ├── README.md
            ├── <analysis 1>.ipynb
            ├── <analysis 2>.ipynb
            ├── ...
            └── <analysis n>.ipynb

For example, 000055/bruntonlab/peterson21

The README.md file should explain the goal of the submission, provide links to relevant scientific publications, and explain the purpose of each notebook file.

The notebook.yaml file is the entry's machine-readable metadata: title, maintainers (GitHub accounts), license, the notebooks it contains, and the datasets and papers it relates to (dandi:000055, doi:10.…). It also holds per-notebook CI flags. See notebook.yaml: entry metadata for the format.

The requirements.in file lists the notebooks' direct Python dependencies, one per line — the packages the notebooks actually import (e.g. dandi, pynwb, remfile, matplotlib). Do not list transitive dependencies or export a full freeze of your environment; our tooling compiles the complete pinned set from this file. After adding it, run

python .github/scripts/lock_notebook.py <path/to/your-notebook>.ipynb

which resolves the pins against Colab's runtime, writes the install cell and Colab badge into the notebook, and writes requirements.lock.txt. If a notebook needs a specific version range (say it was written against an older matplotlib API), express that as a bound in requirements.in (e.g. matplotlib<3.11).

Note: notebooks are automatically tested in CI, made runnable in Google Colab, and published as self-contained container images. The site also publishes a machine-readable index at https://notebooks.dandiarchive.org/notebooks.json (per dandiset: notebook paths with GitHub, Colab, and docker links) for other sites to embed, and the full catalog of entries at https://notebooks.dandiarchive.org/registry.json. Before opening a PR, see Adding a notebook: metadata, CI, and Colab for the notebook.yaml format, how the CI test works, and headless-execution gotchas. (Some older submissions carry an environment.yml instead of requirements.in; new submissions should use requirements.in.)

Feel free to reach out on the DANDI helpdesk with any questions.

Useful tools

We use https://app.reviewnb.com/ to provide convenient review of notebook diffs in Pull Requests in GitHub web UI.

To assist in reviewing diff's in notebooks locally we recommend to checkout nbdime which provides comparable functionality and integrates well with your local git.

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages