AutoSeg
AutoSeg runs TotalSegmentator on every .nii or .nii.gz file inside a folder tree.
Given a root folder, it searches that folder and all subfolders for NIfTI files, runs:
TotalSegmentator -i <input_file> -o <output_folder> -ta <task>
and saves each segmentation output beside the source scan.
Requirements
- Python 3.9 or newer
- TotalSegmentator installed and available on your command line
Install TotalSegmentator separately before using this package. You should be able to run:
TotalSegmentator --help
Install
After this package is published to PyPI, users will be able to install it with:
pip install autoseg
Task Argument
AutoSeg adds the -ta flag to the TotalSegmentator command for you. You only need to provide the task name:
autoseg "C:\path\to\scans" total
Usage
Run AutoSeg on a folder:
autoseg "C:\path\to\scans" total
Use another TotalSegmentator task by passing the task name after the folder:
autoseg "C:\path\to\scans" <task name>
If you leave the task name off, AutoSeg prompts for it during runtime:
autoseg "C:\path\to\scans"
Use TotalSegmentator's --statistics option for volume and intensity calculations
autoseg "C:\path\to\scans" <task name> statistics
Preview what would run without starting TotalSegmentator (Reduced wait time for testing/troubleshooting):
autoseg "C:\path\to\scans" total --dry-run
Output Folders
For each input file, AutoSeg creates a segmentation folder in the same directory as the scan.
Example:
C:\data\patient01\scan.nii.gz
C:\data\patient01\scan_segmentations\
If the expected output folder already exists and contains files, AutoSeg skips that scan so it does not run segmentation again.
AutoSeg also ignores folders named segmentations or ending in _segmentations. This prevents a resumed run from trying to segment TotalSegmentator's own output .nii.gz mask files.
Metadata
Release files for autoseg 1.1.1
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 | |
|---|---|---|---|---|
| autoseg-1.1.1.tar.gz | 4.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autoseg-1.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.0 kB
Release files / autoseg-1.1.1.tar.gz
| Download URL | autoseg-1.1.1.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
59a3783bf0a27c7727d1ff6917d39e63d6e05eff76be32f5b04cfd4413cb7251
|
|
BLAKE2b-256 checksum How to use checksums |
52f92ff29b8354ddef5d6301c467e4edd96b49b9145257e3f7e769a502de4dc9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 Sep 21, 2026.
Transparency logRelease files / autoseg-1.1.1-py3-none-any.whl
| Download URL | autoseg-1.1.1-py3-none-any.whl |
|---|---|
| Size | 4.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
034a583f56769280ee81d25d520a5854be9ac71102dda9fe47e072a39330056b
|
|
BLAKE2b-256 checksum How to use checksums |
f789d7ff5fd5d12c559d3b25d2dbfe04b05adba61c365c8584098d6d9d7cd60a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 Sep 21, 2026.
Transparency logSecurity for autoseg 1.1.1
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 autoseg-1.1.1.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 Sep 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.