You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mat is described as a "multidimensional array" and has a constructor allowing you to construct one. Is there any benefit in generalizing the wrapper to allow more than 2 "spatial" dimensions?
The text was updated successfully, but these errors were encountered:
timholy
added a commit
to timholy/JuliaOpenCVBindingGenerator
that referenced
this issue
Sep 12, 2021
This is a proposed redesign that may be a bit more natural to work
with from the Julia perspective. The principal difference are:
- Support eltypes of the form `SVector{T,N}`: this makes this wrapper
behave more like OpenCV itself, which (unlike Python) does not use
an array dimension to encode the number of color channels.
- Support `N0f8` and `N0f16`, JuliaImages preferred interpretation of
8- and 16-bit unsigned intensity data. (See FixedPointNumbers and
https://juliaimages.org/latest/tutorials/arrays_colors/#fixedpoint;
interestingly, OpenCV itself suffers from the exact same problem, see
https://stackoverflow.com/questions/14539498/change-type-of-mat-object-from-cv-32f-to-cv-8u
for an example of a user who got bit by the "divide by 255" rule.)
- Work towards support for multidimensional arrays (see
JuliaImages/OpenCV.jl#4)
- Validate arguments more carefully and improve correctness in a few
key places
Mat
is described as a "multidimensional array" and has a constructor allowing you to construct one. Is there any benefit in generalizing the wrapper to allow more than 2 "spatial" dimensions?The text was updated successfully, but these errors were encountered: