Skip to main content

slicerheart_4dflow

WARNING: This implementation is a draft, under active refinement.

Draft Implementation of Filters for 4D flow MRI processing by the SlicerHeart project:

  • background phase (eddy current) correction: ols, msac, wrls, war+msac, arto
  • velocity anti-aliasing (phase unwrapping): temporal, Laplacian 3D/4D, Laplacian then temporal
  • multi-venc (dual-/triple-venc) unwrapping (DRAFT, phantom-tested): sdv, odv, stepwise, schnell
  • noise masking and PC-MRA
  • divergence-free filtering and denoising: fdm, relaxed, leray, dfw
  • plane flow quantification and mass-conservation QA
  • pathlines (numpy RK4 or VTK particle tracer) and centerline-based plane placement
  • derived hemodynamics: vorticity, helicity, kinetic energy, viscous energy loss
  • wall shear stress (TAWSS, OSI) from the lumen segmentation
  • relative pressure by the pressure Poisson equation
  • per-study quality report (venc adequacy, noise, residual offset, mass conservation) as JSON and Markdown
  • analytic phantoms (Poiseuille, Womersley, stenosis, bifurcation, thorax, valve jet) and a phase-contrast forward model (noise, aliasing, partial volume, dephasing, multi-venc) for tests without data download

Only numpy and scipy are required; VTK is needed for pathline export and the VTK particle tracer. Methods, defaults and literature references are described in docs/FLOWFILTERS_README.md, docs/BACKGROUND.md and docs/METHODS_DRAFT.md.

Installation

pip install slicerheart_4dflow

In 3D Slicer: slicer.util.pip_install("slicerheart_4dflow").

Usage

import slicerheart_4dflow as f4d

# encoded velocity components, each aliased at its venc
corrected, info = f4d.correct_background_phase(velocity_t, magnitude_t, method="war+msac")
unwrapped = f4d.unwrap_velocity(corrected, venc, voxel_to_world, method="laplacian_then_temporal")
# world velocity components
velocity_world_t = unwrapped @ encoding_to_world.T
filtered, infos = f4d.divergence_free_sequence(velocity_world_t, lumen_mask, voxel_to_world, method="fdm")
flow = f4d.plane_flow(filtered, voxel_to_world, centre=(10.0, -32.0, 54.0), normal=(0.0, 0.3, 1.0),
                      radius=15.0, lumen_mask=lumen_mask)["flow"]

Conventions (see geometry.py):

  • Image arrays are indexed [k, j, i] (i varies fastest), as returned by ITK GetArrayFromImage or slicer.util.arrayFromVolume: velocity (nt, nk, nj, ni, 3), magnitude (nt, nk, nj, ni), lumen mask (nk, nj, ni) bool.
  • voxel_to_world is a 4x4 homogeneous matrix that maps voxel coordinates (i, j, k, 1) to world coordinates (x, y, z, 1) in mm. Any affine mapping is supported: anisotropic, oblique, flipped or even sheared voxel axes. f4d.voxel_to_world_matrix(spacing, origin, directions) builds one.
  • The world coordinate system can be any (e.g. LPS or RAS); the package makes no assumption about it, the inputs only need to be consistent.
  • Velocity vectors have world components (vx, vy, vz) in the coordinate system of voxel_to_world. Unwrapping is the exception: it must be applied to the components as encoded, because each encoding direction aliases at its own venc.
  • Points (plane centres, seeds, centerlines, pathline points) are world (x, y, z) mm; plane normals are world vectors.

Reading data prepared in 3D Slicer

slicer_io.py reads the files that 3D Slicer writes, so data can be processed without Slicer and without a DICOM reader. It needs the clinical extra (pip install slicerheart_4dflow[clinical], which installs pynrrd).

  • Formats:
    • volumes and volume sequences (.nrrd, .seq.nrrd), with vector components converted by the measurement frame
    • segmentations (.seg.nrrd), including several layers and cropped extents
    • plane markups (.mrk.json)
    • whole 4D flow test cases exported by SlicerHeart Import 4D Flow (see tests/clinical/README.md)
  • World frame: arrays follow the conventions above. The world frame is the file's (LPS), or RAS with world="RAS".
f4d.dataset_cases("D:/Data/4Dflow/_test_cases_anonymized_")      # ["Patient0001", ...]
case = f4d.load_case("D:/Data/4Dflow/_test_cases_anonymized_", "Patient0004")
case["velocity_raw_t"], case["magnitude_t"], case["voxel_to_world"], case["venc_mm_s"], case["lumen"], case["planes"]
lumen, voxel_to_world = f4d.read_segmentation("lumen.seg.nrrd", segment="lumen")

Development

pip install -e ".[test]"
python -m pytest

Tests that use an aortic CFD example download it into tests/data on first use, from the TestingData release (see tests/README.md).

Test results (the regression metrics of the last run) are written to .test-reports/ at the repository root, which is not committed; set SLICERHEART_4DFLOW_TEST_REPORT_DIR to use another folder. The clinical tests and the baselines kept with the clinical data are described in tests/clinical/README.md.

Releasing

Versions are derived from git tags. Publishing a GitHub release with a tag such as v0.1.0 runs the tests, builds the sdist and wheel, and uploads them to PyPI (.github/workflows/publish.yml). This requires a PyPI trusted publisher set up for project slicerheart_4dflow, repository JolleyLab/slicerheart_4dflow, workflow publish.yml, environment pypi.

License

MIT

Metadata

Release files for slicerheart-4dflow 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for slicerheart-4dflow 0.2.0
File Size Uploaded Provenance
slicerheart_4dflow-0.2.0.tar.gz 251.8 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for slicerheart-4dflow 0.2.0
File Interpreter ABI Platform
slicerheart_4dflow-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 375.2 kB

Release files / slicerheart_4dflow-0.2.0.tar.gz

Download URL slicerheart_4dflow-0.2.0.tar.gz
Size 251.8 kB
Tags Source
SHA-256 checksum
How to use checksums
1bd30b6157c82ce5680fe6db94a1454c5da3cad4e688f10721ed79691af92dcb
BLAKE2b-256 checksum
How to use checksums
5dbd936016cbf209e63503e016a7c963ef8c919d585e24502a0b6f91f66f7309
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 23, 2026.

Transparency log

Release files / slicerheart_4dflow-0.2.0-py3-none-any.whl

Download URL slicerheart_4dflow-0.2.0-py3-none-any.whl
Size 123.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
026c161272dd5e539117f3bcc854381541cf431012210191ac2c189e16079396
BLAKE2b-256 checksum
How to use checksums
b23229df82b2ebe0fefa5b5c4e6e36712e07189d86049019975879bb9d5fb4f5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 23, 2026.

Transparency log

Security for slicerheart-4dflow 0.2.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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for slicerheart_4dflow-0.2.0.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 Oct 23, 2026.

Transparency log

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.

Release history Release notifications | RSS feed

This release

0.2.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page