A Python package for radiomics analysis.
Table of Contents
- Introduction
- Installation
- Using MEDiml
- Tutorials
- IBSI Standardization
- Getting help
- Contributing
- Acknowledgement
- Citation
- License
Introduction
MEDiml-pkg is an open-source Python package that can be used for processing multi-modal medical images (MRI, CT or PET) and for extracting their radiomic features. It is also the computational engine behind MEDiml-app, the desktop application for conducting radiomics workflows without writing code. This package is meant to facilitate the processing of medical images and the subsequent computation of all types of radiomic features whilst maintaining the reproducibility of analyses. This package has been standardised with the IBSI norms.
See the workflow figure at the top for a step-by-step overview of the package, from medical image datasets and preprocessing to radiomic feature extraction and machine learning.
Installation
Python installation
The MEDiml package requires Python 3.8, 3.9 or 3.10. If you don't have it installed on your machine, follow the instructions here to install it.
Package installation
You can easily install the MEDiml package from PyPI using:
pip install MEDiml
Or, with uv (the fastest Python package and project manager):
uv pip install mediml # into your current environment
uv add mediml # into a uv project
uv tool install --python 3.10 mediml # only the `radiomics` command, in its own environment
If your uv project uses Python 3.11 or newer, create one for Python 3.10 instead: uv init --python 3.10.
For more installation options (Conda, Poetry...) check out the installation documentation.
Using MEDiml
MEDiml can be used either as a command line tool for batch radiomics extraction, or as a Python package that you import directly into your own scripts and notebooks for finer-grained control over the processing and feature extraction pipeline.
Using MEDiml through the command line
After installation, you can launch radiomics extraction directly from the terminal:
radiomics <path/to/input> <path/to/settings_file> <path/save> --use-niftis --n-batch 4 --skip-existing
By default, every scan found in the input folder is processed, and all the ROIs of a scan are
combined into a single region (i.e. {ROI_1}+{ROI_2}). To process a specific list of scans and
ROIs instead, pass a CSV file with the
optional --path-csv argument:
radiomics <path/to/input> <path/to/settings_file> <path/save> --path-csv <path/to/csv_file>
The command wraps the existing BatchExtractor workflow and selects the appropriate input format automatically. The full list of arguments, required ones first, is described below:
| Argument | Required | Description |
|---|---|---|
path_input |
Yes | Path to the input dataset folder containing the scans to process. |
path_settings |
Yes | Path to the radiomics extraction settings file. |
path_save |
Yes | Path to the folder where the extracted feature files will be written. |
--path-csv |
No | Path to a CSV file mapping specific scans to specific ROIs (columns: PatientID, ImagingScanName, ImagingModality, ROIname). If omitted, every scan found in the input folder is processed and all of its ROIs are combined into a single region. |
--use-niftis |
No | Process NIfTI files instead of DICOM files. This is the default behavior and is mutually exclusive with --use-dicoms. |
--use-dicoms |
No | Process DICOM files instead of NIfTI files. Mutually exclusive with --use-niftis. |
--n-batch |
No | Number of CPU cores to use for extraction. Defaults to 4. |
--skip-existing |
No | Skip scans whose features already exist in the output folder. |
Using MEDiml through code
import os
import pickle
import MEDiml
# Load MEDiml DataManager
dm = MEDiml.DataManager(path_dicoms=os.getcwd())
# Process the DICOM files and retrieve the MEDiml object
med_obj = dm.process_all_dicoms()[0]
# Extract ROI mask from the object. `name_roi` is optional: when it is omitted,
# the union of all the ROIs found in the object is used.
vol_obj_init, roi_obj_init = MEDiml.processing.get_roi_from_indexes(
med_obj,
name_roi='{ED}+{ET}+{NET}',
box_string='full')
# Extract features from the imaging data
local_intensity = MEDiml.biomarkers.local_intensity.extract_all(
img_obj=vol_obj_init.data,
roi_obj=roi_obj_init.data,
res=[1, 1, 1]
)
# Update radiomics results class
med_obj.update_radiomics(loc_int_features=local_intensity)
# Saving radiomics results
med_obj.save_radiomics(
scan_file_name='STS-UdS-001__T1.MRscan.npy',
path_save=os.getcwd(),
roi_type='GrossTumorVolume',
roi_type_label='GTV',
)
Tutorials
We have created many tutorial notebooks to assist you in learning how to use the different parts of the package. More details can be found in the documentation.
IBSI Standardization
The image biomarker standardization initiative (IBSI) is an independent international collaboration that aims to standardize the extraction of image biomarkers from acquired imaging. The IBSI therefore seeks to provide image biomarker nomenclature and definitions, benchmark datasets, and benchmark values to verify image processing and image biomarker calculations, as well as reporting guidelines, for high-throughput image analysis. We participate in this collaboration with our package to make sure it respects international nomenclatures and definitions. The participation was separated into two chapters:
IBSI Chapter 1
The IBSI chapter 1 is dedicated to the standardization of commonly used radiomic features. It was initiated in September 2016 and reached completion in March 2020. We have created two jupyter notebooks for each phase of the chapter and made them available for the users to run the IBSI tests for themselves. The tests can also be explored in interactive Colab notebooks that are directly accessible here:
IBSI Chapter 2
The IBSI chapter 2 was launched in June 2020 and reached completion in February 2024. It is dedicated to the standardization of commonly used imaging filters in radiomic studies. We have created two jupyter notebooks for each phase of the chapter and made them available for the users to run the IBSI tests for themselves and validate image filtering and image biomarker calculations from filter response maps. The tests can also be explored in interactive Colab notebooks that are directly accessible here:
Our team named UdeS (a.k.a. Université de Sherbrooke) has already submitted the benchmarked values to the IBSI uploading website.
Run IBSI tests locally
You can view and run the tests locally with Jupyter Notebook. If it is not already installed on your machine, install it using:
python -m pip install jupyter
Then access the IBSI tests folder using:
cd notebooks/ibsi/
Finally, launch Jupyter Notebook to navigate through the IBSI notebooks using:
jupyter notebook
Make sure to run the notebooks with a Jupyter kernel that has MEDiml installed. If that's not the case, you can simply install it from within the notebook by running the following in a code cell:
! pip install MEDiml
Getting help
- Bugs and feature requests: open an issue on GitHub Issues.
- Questions and discussion: join the MEDomics Discord.
Contributing
Contributions are welcome. See CONTRIBUTING.md and our Code of Conduct.
Acknowledgement
MEDiml is an open-source package developed at the MEDomicsLab laboratory with the collaboration of the international consortium MEDomics. We welcome any contribution and feedback. Furthermore, we wish that this package could serve the growing radiomics research community by providing a flexible as well as IBSI standardized tool to reimplement existing methods and develop new ones.
Citation
If you use MEDiml in your research, please cite it using:
@misc{loutfi2026mediml,
title = {{MEDical Image analysis with Machine Learning (MEDiml)}: Strategies for Simpler Radiomics},
author = {Ait Lhaj Loutfi, Mahdi and others},
year = {2026},
eprint = {2610.37715},
archiveprefix = {arXiv},
doi = {10.48550/arXiv.2610.37715}
}
The MEDiml reference manual explains the radiomics concepts and workflow shared by the Python package and desktop application, including image preprocessing, feature extraction, predictive modelling and interpretation. It also covers the software architecture and installation, compares MEDiml with other tools, and illustrates its use on five oncological imaging cohorts.
License
MEDiml-pkg is released under the GNU General Public License v3.0.
Metadata
Release files for mediml 1.0.0
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 |
|---|---|---|---|---|
| mediml-1.0.0.tar.gz | 240.9 kB | Without provenance | Details for mediml-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mediml-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for mediml-1.0.0-py3-none-any.whl |
Total release size: 520.1 kB
Release files / mediml-1.0.0.tar.gz
| Download URL | mediml-1.0.0.tar.gz |
|---|---|
| Size | 240.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dbc7e2fa550a73ef45a8f2d75bc2b84eaa442bd54cdd4cb8a1d7406e9abda904
|
|
BLAKE2b-256 checksum How to use checksums |
4b920c47093f6366fa1892c8c2e2d0d2efd766a981b2d2d976f9c00ce9932d15
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.18
|
Release files / mediml-1.0.0-py3-none-any.whl
| Download URL | mediml-1.0.0-py3-none-any.whl |
|---|---|
| Size | 279.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a2d7fcd87777141ebf4e744571bdc9ac2be5f9ecfc8bc671451042d902b02545
|
|
BLAKE2b-256 checksum How to use checksums |
6b7c836e68cb1865c1b76b8d1feea76041c331fb758e2a63073bfaf6e0ddc103
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.18
|
Security for mediml 1.0.0
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.