-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Axis support #67
Axis support #67
Conversation
TODO: Add the axis argument for the packets. |
Lets take this version for a test drive:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
@@ -563,6 +568,7 @@ class MatrixWaverec2(object): | |||
def __init__( | |||
self, | |||
wavelet: Union[Wavelet, str], | |||
axes: Tuple[int, int] = (-2, -1), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Breaking change. But okay since pywt
uses this ordering.
Major changes:
Breaking changes:
axis
oraxes
argument appears before arguments related to boundary wavelet support. Pywt does not support boundary wavelets, so to respectpywt
argument order we have added the new arguments before anything related to boundary wavelets. This makes it easy to migrate frompywt
toptwt
and back. Unfortunately, this choice breaks calls to boundary wavelet arguments by order.To migrate call arguments related to boundary wavelets by name. This affects only matrix-fwt and wavelet-packet code that uses boundary wavelet support.