p4TSA — package for Time Series Analysis

Contact: info@elenacuoco.com — https://www.elenacuoco.com

p4TSA is a spin-off of the C++ Noise Analysis Package (NAP). The core is written in C++ and is exposed to Python through a pybind11 binding. The Python interface is called py4TSA (you can still pronounce it pi'za) and is imported as py4tsa.

The module used to be called pytsa. That name on PyPI belongs to an unrelated project, so change any import pytsa to import py4tsa.

What is this for?

p4TSA is a minimal package of ad-hoc functions to work with time series. It includes:

• Whitening in the time domain
• Double whitening (equivalent to dividing by the Power Spectral Density) in the time domain
• Wavelet decomposition
• Wavelet Detection Filter

The pipeline that uses it

p4TSA is the C++ core. The search pipeline that drives it — trigger generation and the downstream trigger analysis — is wdflow, which imports this library through py4tsa. wdflow supersedes the earlier wdf package.

The two share the top-level module name wdf, so they cannot be installed side by side: whichever wdf sits directly in site-packages shadows the other, including an editable install of wdflow. If import wdf resolves somewhere unexpected, pip uninstall wdf removes the legacy package.

How to cite

Use of this code in published work requires citation of the following.

The Wavelet Detection Filter:

• E. Cuoco, The Wavelet Detection Filter: A Real Time Unmodeled Pipeline for Gravitational Wave Transients, Ranking Coincidences with a Graph Neural Network, arXiv:2609.12797 (2026). arxiv.org/html/2609.12797v1, 10.48550/arXiv.2609.12797
• E. Cuoco, M. Razzano, A. Utina, Wavelet-based classification of transient signals for gravitational wave detectors, 26th European Signal Processing Conference (EUSIPCO), 2648–2652 (2018). 10.23919/EUSIPCO.2018.8553393

Time-domain whitening, which this library implements:

• E. Cuoco et al., On-line power spectra identification and whitening for the noise in interferometric gravitational wave detectors, Class. Quantum Grav. 18, 1727 (2001). 10.1088/0264-9381/18/9/309
• E. Cuoco et al., Noise parametric identification and whitening for LIGO 40-m interferometer data, Phys. Rev. D 64, 122002 (2001). 10.1103/PhysRevD.64.122002

CITATION.cff in this repository carries the same list in machine-readable form; GitHub's Cite this repository button reads it.

Requirements

p4TSA is not a pure-Python package: building it compiles the C++ core into a single Python extension module. It depends on a few native libraries:

The wheels on PyPI carry GSL, FFTW3 and FrameL inside them, so this table matters only when building from source. All of it is on conda-forge.

Installation with pip (Linux)

pip install py4tsa
python -c "import py4tsa; print(py4tsa.__file__)"

The wheels are manylinux_2_28_x86_64, for CPython 3.10 to 3.13.

Elsewhere — macOS, Windows, another architecture — pip falls back to the source distribution, which compiles the C++ core and needs the libraries above; use conda there.

Installation with conda

Option A — install a pre-built package

If a built package has been published to a conda channel, install it directly (replace <channel> with the channel it was uploaded to):

conda install -c conda-forge -c <channel> py4tsa

The importable module is py4tsa:

python -c "import py4tsa; print('py4TSA ready')"

Option B — build from source with conda-build

The repository ships a conda recipe under conda-recipe/. The native dependencies live on conda-forge, which must be enabled with strict channel priority, otherwise conda resolves against defaults (where framel, libframel and libboost-headers do not exist).

The build follows the Python of the environment you activate, so py4tsa always matches the interpreter you use — no fixed pin, no version mismatch at install time.

# 1. install conda-build in the base environment
conda install -n base conda-build

# 2. enable conda-forge with strict priority (once)
conda config --add channels conda-forge
conda config --set channel_priority strict

# 3. activate the environment you want to use py4tsa in (or create it),
#    then build FOR that environment's Python:
conda activate <your-env>
PYVER=$(python -c "import sys; print(f'{sys.version_info.major}.{sys.version_info.minor}')")
conda build conda-recipe/ -c conda-forge --python=$PYVER

# 4. install into the same environment
conda install -c conda-forge --use-local py4tsa

--python=$PYVER compiles the package exactly for the active environment's Python. If that environment uses a pre-release Python, conda-forge may not yet provide builds of the dependencies — in that case use an environment with a stable Python.

Build and install the py4tsa Python module

The C++ sources are compiled with CMake into a Python extension module named py4tsa. Build and install it for the currently active Python environment with:

conda install -c conda-forge cmake make compilers pybind11 gsl fftw framel libboost-headers cereal

cmake -S . -B build \
  -DCMAKE_BUILD_TYPE=Release \
  -DCMAKE_INSTALL_PREFIX="$CONDA_PREFIX"

cmake --build build -j"$(nproc)"
cmake --install build

CMake may install the compiled extension in the environment prefix. Move it to the active Python site-packages directory if necessary:

PYTHON_SITE=$(python -c "import sysconfig; print(sysconfig.get_paths()['platlib'])")
mv "$CONDA_PREFIX"/py4tsa*.so "$PYTHON_SITE"/

Verify the installation with:

python -c "import py4tsa; print(py4tsa.__file__)"

Reinstalling after changing the C++ sources

A rebuild does not by itself change what import py4tsa loads. Repeat the build and install, and check that the module Python resolves is the one just built:

cmake --build build -j"$(nproc)"
cmake --install build

PYTHON_SITE=$(python -c "import sysconfig; print(sysconfig.get_paths()['platlib'])")
mv "$CONDA_PREFIX"/py4tsa*.so "$PYTHON_SITE"/

md5sum build/py4tsa*.so "$PYTHON_SITE"/py4tsa*.so

The two checksums must match. If they differ, the interpreter is still loading the previous build and any change to the C++ will appear not to have taken effect -- a failure that looks like a bug in the code rather than in the install.

A .so placed in site-packages this way takes precedence over an editable install (pip install -e .), which resolves the module through a .pth file instead. Having both means the copied file wins and rebuilds stop taking effect silently, so pick one: either move the file after each build, as above, or use the editable install and delete the copy in site-packages.

Installation with pip

pip builds the C++ extension from source, so the native libraries and the Boost headers must already be present in the environment. The simplest way to provide them is a conda environment:

conda install -c conda-forge gsl fftw framel libboost-headers cereal
pip install .

To build a wheel instead of installing in place:

pip install build
python -m build --wheel        # -> dist/py4tsa-3.2.0-*.whl

Running the tests

pip install pytest
pytest python-wrapper/tests/ -v

Runs on every push/PR via GitHub Actions (Python 3.10-3.12).

Changelog

2.2.0 (2026-08-03)

• Contact info updated: elena.cuoco@unibo.it replacing the retired ego-gw.it address everywhere it appeared (source headers, README, docs); Giancarlo Cella dropped as a docs team contact.
• Missing docs page added for ExtraWaveletFamilies.hpp (Coiflet/Symlet bases below) — it had doxygen comments but no Sphinx page since it was introduced.
• CI Node.js 20 deprecation cleared: actions/checkout v4→v5, mamba-org/setup-micromamba v1→v3 (both now Node 24-native).
• test_02_persistence.py no longer depends on wdf: builds its SeqView fixture with py4tsa's own SeqView_double_t/FillPoint instead of wdf.structures.array2SeqView, which isn't installed in this repo's CI.
• WDF trigger SNR statistic fixed: EventFullFeatured::mSigma now exposes the winning wavelet basis's own per-window sigma across the C++/Python boundary (was previously recomputed downstream from a separate, staler sigma convention). The candidate wavelet-basis list dropped the 3 biorthogonal B-spline bases (not L2-energy-preserving, let them win basis selection spuriously even on pure noise).
• Candidate wavelet-basis list redesigned and trimmed (WDF2Classify/WDF2Reconstruct, 19 → 10 bases): dropped redundant plain/centered Daubechies duplicates (same filter taps, just phase-shifted), added Coiflet (order 1, 2) and Symlet (order 4, 8) — genuinely new basis shapes, plugged into GSL's own extensible gsl_wavelet_type mechanism (no new external wavelet library, no GSL patching). See include/ExtraWaveletFamilies.hpp.
• eternity (1999-2003 vendored XML persistence) removed entirely, replaced with Cereal (header-only, actively maintained; new cereal conda-forge dependency). See include/CerealPersistence.hpp.
• Legacy pre-packaging-build files removed: bind.sh, install_dependencies.sh, install_full_dependencies.sh, python-wrapper/CMakeLists.txt (an orphaned separate build script from before this repo's CMake packaging build, unused by it).
• CI moved from Travis to GitHub Actions (.github/workflows/ci.yml) — Travis's free tier for open source was retired years ago, and its old config predated the current build system.

Contributing

Changes reach master through pull requests only, and a pull request merges only once CI is green. See CONTRIBUTING.md for how to build and test locally, what CI checks, and the invariants a change to the detection filter must preserve.

Who do I talk to?

• Repo owner / admin: info@elenacuoco.com
• Team contacts: elena.cuoco@unibo.it

License

GPL-3.0-or-later. See LICENSE.