Skip to main content

pyharbinger

PyPI Python versions License: MIT

Python port of the R harbinger — a framework for time series event detection (anomalies, change points, and motifs/discords), built on the DAL Toolbox Experiment Line.

pyharbinger unifies many detection methods under one interface (fit → detect → evaluate) and a common evaluation protocol, so different detectors can be compared fairly — reusing classic libraries (scikit-learn, numpy, pandas, scipy, ruptures) through thin adapters.

It is the capstone of the DAL Python family:

  • Builds on pydaltoolbox (foundation) and pytspredit (time series prediction) — its regressors power the forecasting-based anomaly detectors.

Installation

pip install pyharbinger

On Python 3.14, ruptures 1.1.x has no prebuilt wheel yet; install with pip install --prefer-binary pyharbinger so pip uses the pure-Python ruptures 1.0.6 wheel. Python 3.9–3.13 install directly.

Quickstart

from pyharbinger import HanrFft, HarEval, datasets

# a labeled example series (one injected anomaly)
dataset = datasets.examples_anomalies()["simple"]
serie, event = dataset["serie"], dataset["event"]

# fit -> detect -> evaluate
model = HanrFft().fit(serie)
detection = model.detect(serie)
print(detection[detection["event"]])

metrics = model.evaluate(detection, event)
print(metrics["confMatrix"])
print("F1:", metrics["F1"])

What's included

Every detector extends Harbinger and returns a detection table with columns idx / event / type ("anomaly", "changepoint", "discord" or "").

Group Classes
Core Harbinger (base contract), deviation / filter / candidate-selection utilities
Evaluation HarEval (hard), HarEvalSoft (SoftED, soft matching via the Hungarian algorithm)
Anomaly HanrMl (forecasting residuals, wraps a pytspredit regressor), HanrFft, HanrFftAmoc, HanrFftBinseg, HanrFftAmocCusum, HanrFftBinsegCusum, HanrHistogram, HanrFbiad
Change point HcpAmoc, HcpBinseg, HcpPelt (via ruptures), HcpKswin, HcpPageHinkley, HcpCfLr, HcpScp, HcpJoinpoint, HcpChow, HcpGft (native structural change), HcpCfArima, HcpCfEts (ChangeFinder, native forecast replacement), HcpBocpd (Bayesian online, native ocp replacement)
Clustering HanctKmeans (anomalies / discords)
Classification HancMl (supervised; wraps a pydaltoolbox classifier)
Multivariate HmuPca (PCA reconstruction error)
Datasets datasets.examples_anomalies(), datasets.examples_changepoints()

Detectors accept a univariate series or, for the multivariate ones, a DataFrame with one column per variable.

Roadmap

Later releases expand coverage toward feature parity with R in two cycles. The low-dependency cycle adds the FFT-hybrid anomaly detectors, the extended change-point family (ChangeFinder, Chow, GFT, join-point, BOCPD, ...), native SAX motif/discord, ensembles, plotting, and the streaming runners. The heavy-dependency cycle then adds — each behind an optional extra — matrix profile (stumpy), GARCH (arch), EMD (EMD-signal), wavelets (PyWavelets), DTW clustering, and the autoencoder detectors (deep-learning backend). See develop/planejamento.md for the full plan.

Faithfulness to R

The port is validated against the R package on the same data at every step. Deterministic components match R to numerical precision (deviation measures, filters, candidate selection, hard/soft evaluation, FFT/histogram/FBIAD detectors, HanrMl with a deterministic regressor, HanctKmeans centroids count, and HcpPageHinkley). Where the backend or RNG differs, the tolerance is documented:

  • HanrMl with a rank-reduced ELM (nhid < input_size, purelin) depends on the hidden-weight RNG.
  • HanctKmeans and HcpKswin depend on initialization / random-subsample RNG.
  • HcpAmoc/HcpBinseg/HcpPelt use ruptures (Gaussian cost); R uses changepoint::cpt.meanvar with the MBIC penalty, so agreement is approximate.
  • HancMl detections match R (e.g. the hanc_ml k-NN example flags the same positions), but class probabilities can differ because scikit-learn and R's class::knn break ties differently.
  • HmuPca matches R exactly (same events and residuals) after fixing a latent degeneracy in R's hmu_pca, which kept all principal components; both now reconstruct from a reduced set (90% variance by default, capped at n_features - 1).
  • HcpCfLr, HcpScp and the FFT-hybrid anomaly detectors match R exactly on the example series. HcpJoinpoint matches R on well-conditioned series; on a perfectly piecewise-linear series its segment residuals collapse to round-off, so the exact break positions are numerically ill-conditioned (the dominant change point is still recovered).
  • HcpChow and HcpGft are re-engineered "++" versions of R's strucchange backend: the least-squares (mean-only) Chow sup-F / Bai & Perron breakpoints are generalised to a Gaussian mean + variance segmentation cost (with the conservative LWZ penalty for the break count in HcpGft), so they also catch scale/variance-regime changes the mean-shift model misses. They deliberately diverge from strucchange, so the gate is detection quality vs ground truth, not R parity: on the example series the summed SoftED-F1 rises from the faithful ports' 3.40 / 2.44 (R 3.31 / 2.20) to 3.73 / 3.17 (develop/benchmark_backimpl.py).
  • HcpCfArima and HcpCfEts are native re-implementations of R's forecast backend (auto.arima / ets): the models are fitted with statsmodels, but the order/model selection is ours. HcpCfEts matches R ets() exactly on all example series. HcpCfArima matches R's integration order d on all series and matches detections exactly on the well-conditioned ones (simple, complex); elsewhere the (p, q) stepwise selection diverges from forecast (statsmodels full-ML AICc vs forecast's CSS/ML approximation and stepwise path), so detections overlap substantially but are not identical — the documented tolerance for forecast's auto-selection.
  • HcpBocpd is a native (pure numpy/scipy) re-implementation of R's ocp backend — Bayesian Online Change Point Detection (Adams & MacKay, 2007) with a Normal-Inverse-Gamma / Student-t predictive. ocp is only an R Suggests dependency and has no maintained Python port, so native is the only faithful path. It matches the real ocp backend exactly (identical detected indices) on all seven example series, including the long increasing_amplitude (n = 1002).

License

MIT

Metadata

Release files for pyharbinger 0.4.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 pyharbinger 0.4.4
File Size Uploaded Provenance Actions
pyharbinger-0.4.4.tar.gz 104.7 kB Without provenance Details for pyharbinger-0.4.4.tar.gz

Built distribution (wheel)

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

Total release size: 211.2 kB

Release files / pyharbinger-0.4.4.tar.gz

Download URL pyharbinger-0.4.4.tar.gz
Size 104.7 kB
Tags Source
SHA-256 checksum
How to use checksums
80b62d9ee5f35a372fc9cab474e076330de56e2d8b646d9cb42575da3356f71a
BLAKE2b-256 checksum
How to use checksums
b9a4133d35de533672aaee04b72ae2a94b37b7f9b2bef9a2ba6b43adb5ff2c86
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.0

Release files / pyharbinger-0.4.4-py3-none-any.whl

Download URL pyharbinger-0.4.4-py3-none-any.whl
Size 106.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
43a08c906e9fda7bf0fe619d604f36accc91c68b22f70a2fd1896f06f5368009
BLAKE2b-256 checksum
How to use checksums
f78863733e8aeb6780e570f52b30e70f2b715a286609aff5851708df3d00528b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.0

Security for pyharbinger 0.4.4

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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