TF2.4_IVIM_code_collection
The ISMRM Open Science Initiative for Perfusion Imaging (OSIPI) is an initiative of the ISMRM Perfusion Study Group, founded in 2019 after a membership survey, and with a mission to:
“promote the sharing of perfusion imaging software in order to eliminate the practice of duplicate development, improve the reproducibility of perfusion imaging research, and speed up the translation into tools for discovery science, drug development, and clinical practice”
This IVIM code collection code library is maintained by OSIPI Taskforce 2.4 and aims to collect, test and share open-source code related to intravoxel incoherent motion (IVIM) analysis of diffusion encoded MRI data to be used in research and software development. Code contributions can include any code related IVIM analysis (denoising, motion correction, model fitting, etc.), but at an initial phase, development of tests and other features of the repository will predominantly focus on fitting algorithms. A goal of the IVIM OSIPI task force is to develop a fully tested and harmonized code library, building upon the contributions obtained through this initiative. Documentation and analysis are available on the OSIPI TF2.4.
We have some useful tools and further documentation on https://osipi.github.io/TF2.4_IVIM-MRI_CodeCollection/.
How to contribute
If you would like to get involve in OSIPI and work within the task force, please email the contacts listed on our website.
If you would like to contribute with code, please follow the instructions below:
- Setting up Git
- How to create a copy of the respository and contribute changes to the repository
- Guidelines for IVIM code contribution
- Guidelines to creating a test file
If you would like to use code from the repository and/or are new to Github or IVIM, please see the jupyter notebook below:
If you would like to use MATLAB-based algorithms or apply the testing framework to one of these algorithms, please have a look at these instructions:
Repository Organization
The repository is organized in four main folders along with configuration files for automated testing.
The doc folder contains all documentation related to the repository of task force 2.4.
The src folder contains source code contributed by the the community. Within src, the original folder contains the code to be tested, and the wrappers folder contains code for harmizing the calls the different code contributions. Within the original folders, contributions are stored in Initials_Institution, e.g. src/original/OGC_AmsterdamUMC.
The test folder contains the test files corresponding to the contributed code in src. to be structured
The utils folder contains various helpful tools.
Citing
If this repository was useful, please cite our upcoming MRM paper. The repository contains a lot of code from other sites. Please cite the appropriate papers depending on the code you used. The citations can be found with the "cite" function from OsipiBase:
fit=osipibase(algorithm="IAR_LU_biexp")
fit.cite()
DOIs can also be found in code_contributions_record.
View Testing Reports
Metadata
Release files for osipi-ivim 0.1.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 | |
|---|---|---|---|
| osipi_ivim-0.1.0.tar.gz | 67.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| osipi_ivim-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 190.0 kB
Release files / osipi_ivim-0.1.0.tar.gz
| Download URL | osipi_ivim-0.1.0.tar.gz |
|---|---|
| Size | 67.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c0237f090f662d5fd1c283d61a693c66e4f81c59f9d77e595c49976b88e85d14
|
|
BLAKE2b-256 checksum How to use checksums |
6c29cc1f88710be82d13345231640475a21d972e5fd0fce64861540e4867263f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Apr 28, 2026.
Transparency logRelease files / osipi_ivim-0.1.0-py3-none-any.whl
| Download URL | osipi_ivim-0.1.0-py3-none-any.whl |
|---|---|
| Size | 122.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1dfd7ca7c1cea70d6ae6bfa145266639c502522f9f4fb19a80f24209af6ab4df
|
|
BLAKE2b-256 checksum How to use checksums |
85b9d24def141ab82686d87cf73e91925c30cb53058a28d767481e7094d85582
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Apr 28, 2026.
Transparency log