Skip to main content

oct-to-tiff

DOI PyPI - Version PyPI - License PyPI Downloads

A command line tool for converting optical coherence tomography angiography (OCTA) data.

Installation

via uv (recommended):

uv pip install oct-to-tiff

via pip:

pip install oct-to-tiff

via conda:

conda install conda-forge::oct-to-tiff

Getting started

oct-to-tiff /path/to/image.OCT

will read an OCT volume and write to a single OME-TIFF file, including voxel size in the metadata.

By default, the output file will be written with the same name as the input file and to the same directory:

tree /path/to/images
    ├── image.OCT
    └── image.ome.tif

To specify a custom output directory, see Optional arguments below.

Batch processing

for file in *.OCT; do oct-to-tiff "${file}"; done

will convert all OCT volumes in the current directory to OME-TIFF files, including voxel size in the metadata.

Supported scan patterns

This tool has been developed by reverse engineering data from the Optovue RTVue XR Avanti System.

Due to limited test data, only the following scan patterns are currently supported:

Structural OCT

  • 3D Cornea
  • 3D Disc
  • 3D Retina
  • 3D Widefield
  • 3D Widefield MCT
  • Angle
  • Cornea Cross Line
  • Cornea Line
  • Cross Line
  • Enhanced HD Line
  • GCC
  • Grid
  • Line
  • ONH (Partial)
  • Pachymetry Wide
  • Radial Lines
  • Raster
  • Retina Map (Partial)

OCT Angiography

  • Angio Disc
  • Angio Retina
  • HD Angio Disc
  • HD Angio Retina

Optional arguments

To view these options at any time, run oct-to-tiff --help.

--output OUTPUT

Description: specify a custom output directory.

If the path to the output directory does not exist, a new directory (and parent directories) will be created.

Usage:

oct-to-tiff /path/to/image.OCT --output /path/to/output/directory

--overwrite

Description: overwrite output file if it exists.

Usage:

oct-to-tiff /path/to/image.OCT --overwrite

--size SIZE

Description: scan size in mm.

Sets the correct voxel size for scan patterns with adjustable length.

Usage:

oct-to-tiff /path/to/image.OCT --size 4.5

--log-level LEVEL

Description: sets the logging level (default: WARNING)

Usage:

oct-to-tiff /path/to/image.OCT --log-level INFO

--version

Description: show program's version number and exit.

Usage:

oct-to-tiff --version

The following options are mutually exclusive:

--angio

Description: convert extracted OCTA data.

Usage:

oct-to-tiff /path/to/data --angio --size 4.5

--en-face

Description: convert extracted en face data.

Usage:

oct-to-tiff /path/to/data --en-face --size 4.5

--seg-curve

Description: convert extracted segmentation data.

Usage:

oct-to-tiff /path/to/data --seg-curve

--boundaries

Description: convert segmentation lines to ImageJ ROIs.

Usage:

oct-to-tiff /path/to/curve.xml --boundaries

Contributing

This project uses Ruff for linting and formatting.

Requirements

Requires Python 3.11 or higher.

Release files for oct-to-tiff 0.6.4

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

Source distribution (sdist)

Source distribution for oct-to-tiff 0.6.4
File Size Uploaded
oct_to_tiff-0.6.4.tar.gz 6.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for oct-to-tiff 0.6.4
File Interpreter ABI Platform
oct_to_tiff-0.6.4-py3-none-any.whl Python 3 none any Details

Total release size: 14.4 kB

Release files / oct_to_tiff-0.6.4.tar.gz

Download URL oct_to_tiff-0.6.4.tar.gz
Size 6.6 kB
Tags Source
SHA-256 checksum
How to use checksums
d290dc49b9ec017e335474fc664bcecc684bae2a7198ccb44b30dc079767abf8
BLAKE2b-256 checksum
How to use checksums
cee2f393da5448fed004465f80424540d2ff15b52526a5782a96b6ec06d4078d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Mar 25, 2026.

Transparency log

Release files / oct_to_tiff-0.6.4-py3-none-any.whl

Download URL oct_to_tiff-0.6.4-py3-none-any.whl
Size 7.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
54b59c39ee23751c23e4ccb1a4061aaa349683e59c7f1e531507b9498baaa0a1
BLAKE2b-256 checksum
How to use checksums
38f699231a3da81dd317485933bf3c9fa21e5508560923ecae01faffe0a484a7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Mar 25, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.6.4 This release

2 release files

0.6.3

2 release files

0.6.2

2 release files

0.6.1

2 release files

0.6.0

2 release files

0.5.0

2 release files

0.4.0

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.1.1

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