OSS-DBSv2
This is the development version of the OSS-DBS rewrite. Use with caution and please wait for the first official release before deploying it. Bug reports are highly welcome, though!
Installation
OSS-DBS is tested with Python 3.8, 3.9, 3.10, and 3.11.
Windows users and Mac users with Python 3.8: Please install NEURON separately before installing OSS-DBS. The instructions can be found here.
All other users can run
pip install ossdbs
Developers
To install OSS-DBS, clone it into a local directory,
cd into this directory and run
pip install -e .
To also run the test suite of OSS-DBS, run
pip install -e ".[test]"
To develop OSS-DBS, run
pip install -e ".[dev]"
To locally build the docs of OSS-DBS, run
pip install -e ".[doc]"
To do everything of the above, run
pip install -e ".[all]"
Run OSS-DBS
To run OSS-DBS, cd into the input_files directory, insert your parameters in the input.json
and start the simulation with
ossdbs input.json
Also check out the examples directory and the documentation.
Development
The code development follows different coding styles that are checked
by git pre-commit hooks.
Install pre-commit via pip install pre-commit and run
pre-commit install to activate it.
Testing
OSS-DBS has two types of tests:
Unit Tests (tests/): Fast, isolated tests that run on every push/PR.
pytest # Run all unit tests
pytest --cov # With coverage
Simulation Tests (input_test_cases/): Full simulation tests that validate the complete pipeline. These run only on pull requests to avoid slowing down regular development.
pytest input_test_cases/test_simulations.py -m simulation # All simulation tests
pytest input_test_cases/test_simulations.py -m "simulation and not slow" # Fast only
See input_test_cases/README.md for detailed documentation on the simulation test suite, including how to add new tests.
Directory Structure
tests/- Unit tests (run on every commit)input_test_cases/- Simulation tests (run on PR only)input_files/- Reference input filesexamples/- Example code for users (may be resource-intensive)
Release files for ossdbs 0.5.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ossdbs-0.5.6.tar.gz | 302.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ossdbs-0.5.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 525.3 kB
Release files / ossdbs-0.5.6.tar.gz
| Download URL | ossdbs-0.5.6.tar.gz |
|---|---|
| Size | 302.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
30fea15f4d808c8508a6556b2de033de6e13a9903ac5a2cb7734019fd466b9bc
|
|
BLAKE2b-256 checksum How to use checksums |
8bd5b4f1e21ded1ce669c02177d1c8f9242e7ac2cf76b92a38710fad3bf7208b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Jul 29, 2026.
Transparency logRelease files / ossdbs-0.5.6-py3-none-any.whl
| Download URL | ossdbs-0.5.6-py3-none-any.whl |
|---|---|
| Size | 222.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e086cf7e157e01279cb94a9a6544c2000eb4c4082db6132b74eda5491b68c4cd
|
|
BLAKE2b-256 checksum How to use checksums |
841fd5af698e9cd93d2b36ab31e0eb929974e27f68e9693dfcc0adab8e193bd0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Jul 29, 2026.
Transparency log