OBI-ONE
OBI-ONE is a standardized library of workflows for biophysically-detailed brain modeling, with the following features:
- Integration with a standardized cloud database for neuroscience and computational neuroscience through entitysdk.
- Standardized provenance of workflows.
- Standardized parameter scans across different modeling workflows.
- Corresponding OpenAPI schema and service generated from Pydantic.
Installation
For Most Users (Default)
# Install core + science dependencies
make install
This installs everything needed for running tasks and data processing scripts.
For Development (Full Setup)
# Install all dependencies + dev tools
make install-dev
This installs everything needed for development: all optional dependencies + dev tools (pytest, ruff, etc.).
For Specific Use Cases
# Service deployment
make install-service
# Notebook development
make install-notebooks
# Production build (all deps, no dev tools)
make install-all
Pre-installation Requirements
brew install uv open-mpi boost cmake
Launch-script Dependencies
The scripts under launch_scripts/ run as tasks in the launch-system, each with its own pinned requirements files. See docs/internal/launch-script-dependencies.md for how to compile, check, and pin these dependencies.
Examples
Notebooks are available in examples/. Remember to install notebook dependencies with
make install-notebooks
Technical Overview / Glossary
The package is split into core/ and scientific/ code.
core/ defines the following key classes:
- ScanConfig: defines configurations for specific modeling use cases such as a CircuitSimulationScanConfig. A Form is composed of one or multiple Blocks (see next), which define the parameterization of a use case. Currently Forms can have both single Blocks and dictionaries of Blocks. Each Form, for example, has its own Initialize Block for specifying the base parameters of the use case. Dictionaries of Blocks of a particular type are used where the Form can accept an unspecified number of this Block type, such as Stimulus Blocks.
- Block: defines a component of a ScanConfig. Blocks are the components which support the specification of parameters which should be scanned over in the multi-dimensional parameter scan. When using the Form (in a Jupyter Notebook for example). Any parameter which is specified as a list is used as a dimension of a multi-dimensional parameter scan when passed to a Scan object (see below).
- SingleConfig:
- Task:
- ScanGenerationTask: is an example task which takes a single ScanConfig as input, an output path and a string for specifying how output files should be stored. Then the function scan.execute() function can then be called which generates the multiple dimensional scan
FastAPI Service
Launch the FastAPI Service, with docs viewable at: http://127.0.0.1:8100/docs
make install-service
make run-local
Documentation
OBI-ONE uses MkDocs with the Material theme for documentation.
Installing Documentation Dependencies
To install the documentation dependencies (MkDocs and MkDocs Material) without affecting your existing dependencies:
make install-docs
This command uses uv sync --group docs to add only the documentation dependencies to your environment, ensuring that other installed packages remain unchanged.
Serving Documentation Locally
To build and serve the documentation locally for preview:
make serve-docs
This will start a local development server (typically at http://127.0.0.1:8000) where you can preview the documentation. The server will automatically reload when you make changes to the documentation files.
Tags
Tags are metadata used to link documentation .md files to products. Each documentation file should include appropriate tags in its frontmatter to categorize and organize content.
Continuous Integration
The documentation is automatically checked in CI on pull requests. The .github/workflows/check-docs.yml workflow:
- Checks if any files in the
docs/directory have been modified in the pull request - If no documentation changes are detected, the check fails with an error message
- You can skip this check by adding the
skip docslabel to your pull request
This ensures that documentation is updated alongside code changes. The check only runs on pull requests targeting main and can be bypassed with the skip docs label when documentation updates are not needed.
Contributions
Please see CONTRIBUTING.md for guidelines on how to contribute.
Acknowledgements
Copyright © 2025-2026 Open Brain Institute
1 maintainer
Metadata
1 maintainer
Release files for obi-one 2026.10.19
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| obi_one-2026.10.19.tar.gz | 16.8 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| obi_one-2026.10.19-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.4 MB
Release files / obi_one-2026.10.19.tar.gz
| Download URL | obi_one-2026.10.19.tar.gz |
|---|---|
| Size | 16.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
92d4cd5b510115e4b147f71797693e1ec8beb466ec92a270929da211dc5a1c6b
|
|
BLAKE2b-256 checksum How to use checksums |
7e1c80b3efe16657a1551fdd06ab0669fc29a049d1e061c33832942ab199b949
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / obi_one-2026.10.19-py3-none-any.whl
| Download URL | obi_one-2026.10.19-py3-none-any.whl |
|---|---|
| Size | 631.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a35fb70a690ecba692e2750b74690010938b4173f751e206b0e6b012626a4039
|
|
BLAKE2b-256 checksum How to use checksums |
372a266515598e5f95e2fc18cfa9a8d73871f43a6f9f5b13ca2149c702cf675b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for obi-one 2026.10.19
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for obi_one-2026.10.19.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
