Wavelet feature extraction for ML pipelines.

FerroWave turns wavelet decompositions into features that can move from research notebooks to Rust inference and analytics systems.

Why this needs production signal processing

!

Time-domain features miss scale-localized behavior that matters in noisy signals.

!

Notebook feature code often breaks when moved into lower-latency production systems.

!

ML pipelines need repeatable feature generation across research and deployment environments.

How FerroWave handles it

01

Decompose the signal

Classical or adaptive transforms expose behavior across time, scale, frequency, and mode.

02

Generate features

Feature vectors, scaleograms, coefficients, energies, ridges, and streaming summaries can feed downstream models.

03

Deploy in Rust

The same transform path can support batch research and production feature extraction.

What makes this FerroWave-shaped

The public site explicitly highlights AI and ML feature extraction.

FerroWave supports multi-scale vectors, scaleogram tensors, and streaming features.

Reference-pinned behavior helps preserve research-to-runtime equivalence.

Common concerns

Are wavelet features only for financial data?

No. Financial signals are one use case; the feature-extraction story applies to broader time-series ML pipelines.

Can features be generated online?

Yes. Streaming transforms and online inference features are part of the public positioning.