Skip to main content

openlifu

Actions Status Documentation Status

PyPI version PyPI platforms

GitHub Discussion

openlifu is a toolbox for planning and controlling focused ultrasound treatments. It generally replicates the functionality developed in the MATLAB open-TFUS toolbox.

Supported Versions

openlifu-python maintenance by release line

Versions may fall to a lower support tier every six months or so, each time the downstream desktop application selects a newer version of openlifu. See the support schedule for details.

Installation

Requirements

Python 3.10-3.12.

We recommend installing openlifu in a virtual environment.

For most users, install the application dependency set:

python -m pip install "openlifu[app]"

This installs the core package plus dependencies for database and volume I/O, simulation, mesh and photogrammetry workflows, cloud sync, and hardware communication support via openlifu-sdk.

Minimal install

If you only need the lightweight core package:

python -m pip install openlifu

The minimal install does not include optional dependencies for simulation, DICOM/NIfTI volume loading, mesh/VTK workflows, photogrammetry, cloud sync, or hardware communication.

Install selected features

You can also install only the optional dependency groups you need:

python -m pip install "openlifu[sim,db]"
python -m pip install "openlifu[io]"
python -m pip install "openlifu[jupyter]"

Useful extras include:

  • app: recommended application set
  • sim: k-Wave simulation support
  • db: DICOM/NIfTI and database volume support
  • mesh: mesh and VTK support
  • photogrammetry: photo-based mesh reconstruction dependencies
  • io: hardware communication dependencies, including openlifu-sdk
  • cloud: cloud sync dependencies
  • jupyter: notebook support

Installing Meshroom

If you are using openlifu.nav.photoscan to reconstruct meshes from photo collections, then you will need to set up Meshroom 2025.1.0.

Ubuntu

Download and Extract

  1. Download Meshroom 2025.1.0 for Linux from https://github.com/alicevision/Meshroom/releases/tag/v2025.1.0.

  2. Extract the downloaded archive:

    tar -xvf Meshroom-2025.1.0-Linux.tar.gz
    

Add Meshroom to PATH

Temporary (Current Session) Run:

export PATH="<path-to-meshroom>/Meshroom-2025.1.0-Linux:$PATH"

Replace <path-to-meshroom> with the actual path where Meshroom was extracted.

Permanent (Persistent Across Sessions) For Bash users:

echo 'export PATH="<path-to-meshroom>/Meshroom-2025.1.0-Linux:$PATH"' >> ~/.bashrc
source ~/.bashrc

Windows

Download and Extract

  1. Download Meshroom 2025.1.0 for Windows from https://github.com/alicevision/Meshroom/releases/tag/v2025.1.0.
  2. Extract the downloaded archive to a directory of your choice.

Add Meshroom to PATH

  1. Open Edit environment variables for your account from the Start menu.
  2. In the Environment Variables window, under User variables, select Path and click Edit.
  3. Click New, and add the path to the folder containing Meshroom.exe.
  4. Click OK to save the changes.

Enable GPU Acceleration

To ensure Meshroom uses your NVIDIA GPU:

  1. Open NVIDIA Control Panel.
  2. In the left sidebar under 3D Settings, click Manage 3D settings.
  3. Go to the Program Settings tab.
  4. Click Add, then browse to and select Meshroom.exe from the folder where you extracted Meshroom.
  5. Under Select the preferred graphics processor for this program, choose High-performance NVIDIA processor.
  6. Click Apply.

Getting Sample Data

A sample database for testing and examples is maintained in the openlifu-sample-database repository. Its files are tracked with Git LFS, so first install Git LFS.

Then check out the tagged version of the sample database that is compatible with this version of openlifu:

git clone --depth 1 --branch openlifu-v0.22 https://github.com/OpenwaterHealth/openlifu-sample-database.git
cd openlifu-sample-database
git lfs pull

Disclaimer

CAUTION - Investigational device. Limited by Federal (or United States) law to investigational use. The system described here has not been evaluated by the FDA and is not designed for the treatment or diagnosis of any disease. It is provided AS-IS, with no warranties. User assumes all liability and responsibility for identifying and mitigating risks associated with using this software.

Metadata

Release files for openlifu 0.22.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 openlifu 0.22.0
File Size Uploaded
openlifu-0.22.0.tar.gz 294.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for openlifu 0.22.0
File Interpreter ABI Platform
openlifu-0.22.0-py3-none-any.whl Python 3 none any Details

Total release size: 467.9 kB

Release files / openlifu-0.22.0.tar.gz

Download URL openlifu-0.22.0.tar.gz
Size 294.1 kB
Tags Source
SHA-256 checksum
How to use checksums
94bc976c7386b66d4c7796be060b186d47f774252759bf47d8382044dc489932
BLAKE2b-256 checksum
How to use checksums
ebc4fd73e1e9b7389a601ad559509ed9c99676d064185c188280c6d581313cec
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 5, 2026.

Transparency log

Release files / openlifu-0.22.0-py3-none-any.whl

Download URL openlifu-0.22.0-py3-none-any.whl
Size 173.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
416cefc7d5497cf07c32ec4d8d9e62158e0fc7f2327c077590b662b875057dbf
BLAKE2b-256 checksum
How to use checksums
10cd888286fbcbdb665ea2c498170c00ccd885705afc14d627353038e7e890cd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 5, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.22.0 This release

2 release files

0.21.2

2 release files

0.21.1

2 release files

0.21.0

2 release files

0.20.2

2 release files

0.20.1

2 release files

0.20.0

2 release files

0.19.0

2 release files

0.18.0

2 release files

0.17.0

2 release files

0.15.0

2 release files

0.14.0

2 release files

0.13.0

2 release files

0.10.0

2 release files

0.9.0

2 release files

0.8.1

2 release files

0.8.0

2 release files

0.7.1

2 release files

0.7.0

2 release files

0.6.0

2 release files

0.5.0

2 release files

0.4.0

2 release files

0.3.2

2 release files

0.3.1

2 release files

0.3.0

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.0

2 release files

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