Properly trim wavelet packet node coefficients during reconstruction #448
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For some boundary modes and data sizes, round-trip DWT/IDWT can results in an output that has an additional coefficient. Here is a simple 1D example where roundtrip transform of a length 17 signal gives a length 18 output:
pywt.waverec(pywt.wavedec(np.arange(17), 'db3', level=3), 'db3').shape
There is some existing logic that seems intended to trim the extra coefficients during wavelet packet transforms:
pywt/pywt/_wavelet_packets.py
Lines 570 to 572 in f0f4ee0
However, this really needs to be done at the
Noderather thanWaveletPacketlevel as indicated by the shape problem raised in #447.closes #447