Wavelet Neural Networks
pip install waveletnn
Package provides the implementation of orthonormal and biorthogonal wavelet transforms via convolutions. Batch multi-channel one- and -two-dimensional data is supported. For analysis kernels of even length are supported, while for inverse transform (synthesis) kernels are required to have length 4k + 2. The blocks are:
OrthonormalWaveletBlock1DOrthonormalWaveletBlock2DBiorthogonalWaveletBlock1DBiorthogonalWaveletBlock2DInverseWaveletBlock1DInverseWaveletBlock2D
Package provides loss functions for wavelet's kernels regularizations to preserve features of both orthonormal (OrthonormalWaveletRegularization) and biorthogonal (BiorthogonalWaveletRegularization) wavelets while training. The features are admissibility (sum of coeffs), orthogonality and regularity. For more info on training see notebooks directory.
The package can use wavelets from the PyWavelets library. If the library is not yet installed use pip install waveletnn[pywt] for full installation. The wavelet blocks can be constructed by providing the name of the wavelet to be used (see pywt.wavelist()) or by manually providing scaling filter for orthonormal blocks and scaling and wavelet analysis filters for biorthogonal wavelets. Note, that results of transform blocks are different from the results of the pywt functions: the approximation from each level is half its input no matter what signal extension mode is used.
The signal extension (padding) is performed via separate module PadSequence. Extension modes are:
- "constant" --
... v v | x1 x2 ... xn | v v ..., with defaultv = 0(same as intorch, default behavior corresponds to "zero" padding inpywt) - "circular" --
... xn-1 xn | x1 x2 ... xn | x1 x2 ...(same as intorch, corresponds to "periodic" padding inpywt) - "replicate" --
... x1 x1 | x1 x2 ... xn | xn xn ...(same as intorch, corresponds to "constant" padding inpywt) - "reflect" --
... x3 x2 | x1 x2 ... xn | xn-1 xn-2 ...(same as intorchandpywt) - "antireflect" --
... (2*x1 - x3) (2*x1 - x2) | x1 x2 ... xn | (2*xn - xn-1) (2*xn - xn-2) ...(same as inpywt, not present intorch)
For examples on usage see notebooks directory.
Release files for waveletnn 0.3.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| waveletnn-0.3.4.tar.gz | 8.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| waveletnn-0.3.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.6 kB
Release files / waveletnn-0.3.4.tar.gz
| Download URL | waveletnn-0.3.4.tar.gz |
|---|---|
| Size | 8.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2c765ad7fe2bbb157527dfea3ea12a9cfbf2570199686ef7f06648ae4c91f241
|
|
BLAKE2b-256 checksum How to use checksums |
e2e72cc216686962a502463c6f15f13f657078f390cdde7e5a78db108fec2156
|
| 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 Sep 10, 2025.
Transparency logRelease files / waveletnn-0.3.4-py3-none-any.whl
| Download URL | waveletnn-0.3.4-py3-none-any.whl |
|---|---|
| Size | 11.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1546f4f401ad743e165a7c246b8fca5f7a57ebc78329ee780081b777e37ac925
|
|
BLAKE2b-256 checksum How to use checksums |
56b57887634c37c8cd79d7b04393411a3c48766080630bb2c8fd28cf4efa64c4
|
| 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 Sep 10, 2025.
Transparency log