-
Notifications
You must be signed in to change notification settings - Fork 28
ImageTransformations v0.9.0 #122
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
Changes from 4 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
@@ -0,0 +1,54 @@ | ||||||
# ImageTransformations | ||||||
|
||||||
## Version `v0.9.0` | ||||||
|
||||||
This version introduces changes internal `warp` and `invwarpedview` implementation thus users can expect some numerical differences. This version introduce a lot of API | ||||||
deprecations. | ||||||
|
||||||
- ![BREAKING][badge-breaking] Previously, `SubArray` passed to `invwarpedview` will use out-of-domain values to build a better result on the boundary. This is considered a too strong assumption and thus removed. ([#138][github-138]) | ||||||
johnnychen94 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
- ![BREAKING][badge-breaking] Rounding for numerical stability in `warp` is now applied to the corner points instead of to the transformation coefficients. ([#143][github-143]) | ||||||
- ![Deprecation][badge-deprecation] `degree` and `fill` arguments are deprecated in favor of their keyword versions `method` and `fillvalue`. ([#116][github-116]) | ||||||
- ![Deprecation][badge-deprecation] `invwarpedview` is deprecated in favor of `InvWarpedView`. ([#116][github-116], [#138][github-138]) | ||||||
- ![Deprecation][badge-deprecation] `warpedview` is deprecated in favor of `WarpedView`. ([#116][github-116]) | ||||||
- ![Enhancement][badge-enhancement] `restrict`/`restrict!` are moved to more lightweight package [ImageBase.jl]. ([#127][github-127]) | ||||||
johnnychen94 marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
- ![Enhancement][badge-enhancement] `imresize` now works on transparent colorant types(e.g., `ARGB`). ([#126][github-126]) | ||||||
- ![Enhancement][badge-enhancement] `restrict` now works on 0-argument colorant types(e.g., `ARGB32`). ([ImageBase#3][github-base-3]) | ||||||
- ![Bugfix][badge-bugfix] Interpolations v0.13.3 compatibility. ([#132][github-132]) | ||||||
johnnychen94 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
- ![Bugfix][badge-bugfix] `restrict` on singleton dimension is now a no-op. ([ImageBase#8][github-base-8]) | ||||||
- ![Bugfix][badge-bugfix] `restrict` on `OffsetArray` is now type stable. ([ImageBase#4][github-base-4]) | ||||||
|
- ![Bugfix][badge-bugfix] `restrict` on `OffsetArray` is now type stable. ([ImageBase#4][github-base-4]) | |
- ![Bugfix][badge-bugfix] `restrict` on `OffsetArray` always returns an `OffsetArray` result. ([ImageBase#4][github-base-4]) |
The meaning of "type-stable" is a little bit ambiguous: sometimes it means "the same type," but more often it simply means inferrable. Because of the potential for confusion, I think it's best to be specific.
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.
Actually, I did mean inferrable here (#118) but it's almost the same 😄
Uh oh!
There was an error while loading. Please reload this page.