FT4FTIRS
FT4FTIRS (Fourier Tranform for Fourier Transform Infrared Spectroscopy) is a Python package for processing interferograms from FTIR (Fourier Transform Infrared Spectroscopy) data. It supports reading Bruker OPUS files, processing interferograms (apodization, zero-filling, Fourier transform), and extracting spectra for further analysis.
Installation
You can install the package using pip:
pip install ft4ftirs
Quick start
from ft4ftirs.io.bruker_opus import BrukerOpusReader
from ft4ftirs.processing.pipeline import SpectralPipeline
from ft4ftirs.processing.scan_averaging import average_spectra
# Load the interferogram(s) plus the instrument-recommended apodizer, phase
# corrector and zero-filling factor from a Bruker OPUS file.
reader = BrukerOpusReader()
data = reader.load("sample.0")
# Run the interferogram -> single-beam spectrum pipeline (apodization,
# zero-filling, FFT and phase correction). Passing the file's zero-filling
# factor reproduces the spectral point spacing OPUS produced.
pipeline = SpectralPipeline(
data["apodizer"], data["phase_corrector"], data["zero_filling_factor"]
)
# A bidirectional file holds a forward and a backward scan. They carry
# different phase errors, so transform each one separately and average the
# resulting *spectra* -- never the interferograms.
spectrum = average_spectra([pipeline(ig) for ig in data["interferograms"]])
print(spectrum.wavenumbers, spectrum.intensities)
See examples/example_opus.py for a complete, runnable script.
Package layout
ft4ftirs.data—InterferogramandSpectrumcontainers.ft4ftirs.io— instrument file readers (currently Bruker OPUS).ft4ftirs.processing— apodization, ZPD finding, phase correction, and theSpectralPipeline.ft4ftirs.analysis— transmittance/absorbance/reflectance conversion and spectral quality metrics.
Metadata
Release files for ft4ftirs 1.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 | |
|---|---|---|---|
| ft4ftirs-1.1.0.tar.gz | 45.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ft4ftirs-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 96.4 kB
Release files / ft4ftirs-1.1.0.tar.gz
| Download URL | ft4ftirs-1.1.0.tar.gz |
|---|---|
| Size | 45.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
757401ded1e76d6e37898ec8987c051633deb6748def194ac8a343023beeba35
|
|
BLAKE2b-256 checksum How to use checksums |
cf215866e26f86cc3227297fa43376e492fe487bf267fc6eaa1befdd0323abad
|
| 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 Aug 20, 2026.
Transparency logRelease files / ft4ftirs-1.1.0-py3-none-any.whl
| Download URL | ft4ftirs-1.1.0-py3-none-any.whl |
|---|---|
| Size | 50.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
62d244666344b73998b9c2e41b96ad65f3e7d8d03b3ae2d8da7eb4cd9287ec31
|
|
BLAKE2b-256 checksum How to use checksums |
452f0007a039a092218b18fd4bbb92a2d5653eab5a6dd9f73179d790acf8e542
|
| 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 Aug 20, 2026.
Transparency log