mosamatic-cli
Command-line tool for running processing tasks on medical images
To-do
-
NumPy to NIFTI conversion
-
Create PNG images from DICOM files
-
Slice selection using either Total Segmentator or MOOSE
What you can do is first create spinal segmentations of a CT scan. Then you can use that data to pick a segmentation, e.g., the L3 vertebra and select the middle slice. In terms of commands/tasks, this would mean a command/task:
- SegmentAnatomyTS: with option to output a specific segmentation object
- SegmentAnatomyMOOSE: with option to output a specific segmentation object
- SelectSlice: Given a CT scan and a segmentation object, select the middle or other slice
-
CT/MRI registration using ANTsPy
-
Total Segmentator liver segmentation CT + MRI (Dixon H2O)
-
IMAT analysis
Discuss with Leroy how to detect fat inside muscle (either as SAT or black pixels). If pixels inside muscle are black, what does that mean? Can I overlay the mask on top of the image and check the pixel gray values and then determine (using the Alberta threshold range) whether these pixels are fat or not?
-
Calculate muscle PDFF maps from Dixon MRI after registering with CT
Commands
- numpy2nifti
- createpngsfromdicomfiles
- selectvertebralslice --engine=ts,moose --vertebra=l3,t4 --position=all,top,middle,bottom
- registerl3 --modalities=ct/dixon,ct/t1,ct/t2
- segmentanatomy --engine=ts,moose --masks=all,spine,l3,t4,liver,vessels
- segmentmusclefatl3[tensorflow] --imat=true,false
- calculatepdffmap2d --inphase=/path/to/image --outphase=/path/to/image --water=/path/to/image --mask=/path/to/mask (muscle and fat)
- calculatepdffmap3d --inphase=/path/to/series --outphase=/path/to/series --water=/path/to/series --mask=/path/to/mask (liver)
Next action
- Implement slice selection with Total Segmentator
Metadata
Release files for mosamatic-cli-macos 1.6.2
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 |
|---|---|---|---|---|
| mosamatic_cli_macos-1.6.2.tar.gz | 27.8 kB | Without provenance | Details for mosamatic_cli_macos-1.6.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mosamatic_cli_macos-1.6.2-py3-none-any.whl | Python 3 | none | any | Details for mosamatic_cli_macos-1.6.2-py3-none-any.whl |
Total release size: 68.9 kB
Release files / mosamatic_cli_macos-1.6.2.tar.gz
| Download URL | mosamatic_cli_macos-1.6.2.tar.gz |
|---|---|
| Size | 27.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
901126a1bcfe38ca8c47ff07735660bd60f1a2021e965174bcc10d05c940d5b8
|
|
BLAKE2b-256 checksum How to use checksums |
4973c9d11aa0155352bed2accb82ac2b1d96679030a1f3e72edc8efb500ec898
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.4 CPython/3.11.0 Darwin/24.5.0
|
Release files / mosamatic_cli_macos-1.6.2-py3-none-any.whl
| Download URL | mosamatic_cli_macos-1.6.2-py3-none-any.whl |
|---|---|
| Size | 41.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0fea3db1306e5b0ea4bd9a1c23a32646d45bb9b5ae9dedac7638ec8f78c57e84
|
|
BLAKE2b-256 checksum How to use checksums |
9e8455b2ece9805e1e0b80764916534fd038f21b1729036cd2999768a4d07530
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.4 CPython/3.11.0 Darwin/24.5.0
|
Security for mosamatic-cli-macos 1.6.2
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.