Labelmerge
Labelmerge: A BIDS app for merging multiple label maps and metadata into a single parcellation scheme.
Examination of the brain has led to the creation and distribution of numerous parcellation schemes, studying various features or aspects including gross anatomy, cytoarchitecture, myeloarchitecture, functional connectivty, or structural connectivity. With the growing number of available schemes, there exists a need for methods to robustly merge different these different atlases from numerous sources depending on the aims of the specific study.
Currently, combining multiple atlases requires image-processing tools to manually remove and add the regions of interest from the respective atlases. While effective, this task becomes inefficient and is prone to error when looking to combine specific labels of interest from multiple atlases or across a group of subjects. To that end we developed Labelmerge, a Brain Imaging Data Structure (BIDS) app that combines the parcellations of multiple atlases into a single parcellation scheme that can be applied towards downstream analysis.
Contributing
Clone the git repository. Labelmerge dependencies are managed with Poetry (version 1.2.x), which you'll need installed on your machine. You can find instructions on the Poetry website.
Then, setup the development environment with the following commands:
poetry install
poetry run poe setup
Labelmerge uses poethepoet as a task runner. You can see what commands are available by running:
poetry run poe
If you wish, you can also run poe [command] directly by installing poethepoet on your system. Follow the install instructions at the link above.
Labelmerge uses pre-commit hooks (installed via the poe setup command above) to lint and format code (we use black, isort, flake8). By default, these hooks are run on every commit.
Please be sure they all pass before making a PR.
Metadata
Release files for labelmerge 0.4.7
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 | Actions |
|---|---|---|---|---|
| labelmerge-0.4.7.tar.gz | 8.2 kB | Without provenance | Details for labelmerge-0.4.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| labelmerge-0.4.7-py3-none-any.whl | Python 3 | none | any | Details for labelmerge-0.4.7-py3-none-any.whl |
Total release size: 17.1 kB
Release files / labelmerge-0.4.7.tar.gz
| Download URL | labelmerge-0.4.7.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e9109fa181eaf8d975eae05d2580bad23d57e2272213e57bcb321558fe81ca5c
|
|
BLAKE2b-256 checksum How to use checksums |
d5c94bd8c1a86534d64bad079359bf37685f6dfd349ce879877a6a650b605668
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.7.1 CPython/3.10.13 Linux/6.2.0-1018-azure
|
Release files / labelmerge-0.4.7-py3-none-any.whl
| Download URL | labelmerge-0.4.7-py3-none-any.whl |
|---|---|
| Size | 8.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
36e354f814843621b368e6488b77298c045f40673df3943557be8ea171e94138
|
|
BLAKE2b-256 checksum How to use checksums |
ed8d4494db9105613855996430966e81c1a035fc804eb9d4e7bce9744f86dee6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.7.1 CPython/3.10.13 Linux/6.2.0-1018-azure
|
Security for labelmerge 0.4.7
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.