Closed gworkman closed 9 months ago
Hi @gworkman, thanks for reporting this issue, and sorry that I didn't have enough bandwidth to look into this problem for a long time. This issue is fixed in #231, and it will be released with v0.1.36 at sometime later this week. I'll let you know once v0.1.36 is shipped!
Thanks! Looking forward to it. I'll test it out this week and report if any other issues pop up with regards to creating a customized image stitching pipeline (this is perfect timing as I'm just now looking into this again!).
Hi @gworkman, v0.1.36 is released, and it works now. :)
iex> image = Evision.imread("test.jpg")
%Evision.Mat{
channels: 3,
dims: 2,
type: {:u, 8},
raw_type: 16,
shape: {1080, 1920, 3},
ref: #Reference<0.1560746059.813301793.233425>
}
iex> opts = [nfeatures: 500]
[nfeatures: 500]
iex> detector = Evision.ORB.create(opts)
%Evision.ORB{ref: #Reference<0.1560746059.813301784.233032>}
iex> Evision.Detail.computeImageFeatures2(detector, image)
%Evision.Detail.ImageFeatures{ref: #Reference<0.1560746059.813301784.233033>}
Hello!
I'm trying to reproduce in Elixir some of the lower-level stitching pipeline from python
stitching
package. Kudos to the team over there, they have made it really clear what is going on under the hood, but in my efforts I can't seem to find a way to Evision to work with applying some of the higher-level abstractions to specific instances of detectors, matchers, etc.Specifically, here's the first file I started to port to Elixir:
However, the call to
Evision.Detail.computeImageFeatures2(detector, image)
does not work. The error message is:I haven't found a way to convert the instance of the feature finder (in this case,
Evision.ORB
) to the baseFeature2D
struct - I tried copying theref
from theORB
struct to a newFeature2D
struct, but it didn't work. How should I proceed?Thanks!