BraTS Orchestrator
______ _____ _____
| ___ \ |_ _/ ___|
| |_/ /_ __ __ _| | \ `--.
| ___ \ '__/ _` | | `--. \
| |_/ / | | (_| | | /\__/ /
\____/|_| \__,_\_/ \____/
_____ _ _ _
| _ | | | | | | |
| | | |_ __ ___| |__ ___ ___| |_ _ __ __ _| |_ ___ _ __
| | | | '__/ __| '_ \ / _ \/ __| __| '__/ _` | __/ _ \| '__|
\ \_/ / | | (__| | | | __/\__ \ |_| | | (_| | || (_) | |
\___/|_| \___|_| |_|\___||___/\__|_| \__,_|\__\___/|_|
Providing the top-performing algorithms from the Brain Tumor Segmentation (BraTS) challenges, through an easy-to-use Python API.
Documentation
|
Quickstart Get up and running in minutes. Go to Quickstart |
Segmentation Adult glioma, meningioma, metastases, and more. Go to Segmentation |
|
Inpainting Synthesize healthy tissue in tumor regions. Go to Inpainting |
Missing MRI Generate missing MRI sequences. Go to Missing MRI |
Installation
pip install brats
# Python >= 3.10 required for preprocessing:
pip install brats[preprocessing]
Quick Example
from brats import AdultGliomaPreAndPostTreatmentSegmenter
segmenter = AdultGliomaPreAndPostTreatmentSegmenter(cuda_devices="0")
segmenter.infer_single(
t1c="path/to/t1c.nii.gz",
t1n="path/to/t1n.nii.gz",
t2f="path/to/t2f.nii.gz",
t2w="path/to/t2w.nii.gz",
output_file="segmentation.nii.gz",
)
Citation
If you use BraTS Orchestrator in your research, please cite:
Kofler, F., et al. (2025). BraTS orchestrator: Democratizing and Disseminating state-of-the-art brain tumor image analysis. arXiv:2506.13807
@misc{kofler2025bratsorchestratordemocratizing,
title={BraTS orchestrator: Democratizing and Disseminating state-of-the-art brain tumor image analysis},
author={Florian Kofler and others},
year={2025},
eprint={2506.13807},
archivePrefix={arXiv},
primaryClass={eess.IV},
url={https://arxiv.org/abs/2506.13807},
}
Contributing
We welcome contributions! Please open a new issue here or have a look at our CONTRIBUTING.md.
License
Metadata
Release files for brats 0.1.13
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 | |
|---|---|---|---|---|
| brats-0.1.13.tar.gz | 324.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| brats-0.1.13-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 378.4 kB
Release files / brats-0.1.13.tar.gz
| Download URL | brats-0.1.13.tar.gz |
|---|---|
| Size | 324.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3738fbc1a3fd94c5caf66b89984b1b68f21c56175320336d69b1f31b66792c1b
|
|
BLAKE2b-256 checksum How to use checksums |
94678a4a418746f96b34484a75959cb8341291a2c0b88fb64f015a6137a9d869
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / brats-0.1.13-py3-none-any.whl
| Download URL | brats-0.1.13-py3-none-any.whl |
|---|---|
| Size | 54.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
04e7d1fd250e947293913bb239b628c39865cbee4d4bf4d923d4270bf0d526b9
|
|
BLAKE2b-256 checksum How to use checksums |
b7ddc6a390ba336d8be283234ec89fae2d77bbd3d1b3eae36d1a95d1b24d1efa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for brats 0.1.13
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.