Padding and correlation options for WaveletOperator
+ check for range_geometry
size
#1638
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.
Describe your changes
bnd_cond
similar toGradientOperator
. This just applies the existing options from pywt.axes
using thecorrelation
keyword similar toGradientOperator
. This sets theaxes
unlessaxes
is already specified, which takes priority. It also gives errors and warnings for nonsense choices.range_geometry
is now checked upon initialization to make sure the wavelet coefficients fit.VectorGeometry
which has so many weird behaviours such as not setting the shape automatically. Also the special option for setting 1D domain geometry has been removed because it was pointless.Describe any testing you have performed
Describe any testing you wish to be implemented :)
axes
orcorrelation
) should keep those dimensions same size as inputcorrelation
andaxes
are also checked for clashes and overall viabilityChannels
should not work with data without channelschannel
or one of the dimensions in 2D data?Link relevant issues
correlation
keyword due to this comment in Adds WaveletOperator, WaveletNorm #1615bnd_cond
, in particular the funny name