search

hybridgroup / gocv

Go package for computer vision using OpenCV 4 and beyond. Includes support for DNN, CUDA, OpenCV Contrib, and OpenVINO.
https://gocv.io
Other
6.72k stars 867 forks source link

Need support for new Tracker format #799

Open ansoni-san opened 3 years ago

ansoni-san commented 3 years ago

Hi,

Why were some of the trackers removed in this commit: https://github.com/hybridgroup/gocv/commit/442292a1e272b8f0964ce8e54b3fde7fc70cb24c

There seems to be no explanation anywhere.

deadprogram commented 3 years ago

Hello @ansoni-san please see https://github.com/opencv/opencv/pull/18838

GoCV just mirrors what they are doing over in OpenCV, as best we can.

Hope that helps!

ieliz commented 3 years ago

Hello, @ansoni-san! You can see the explanation here.

ansoni-san commented 3 years ago

Ah, perfect. This is what I was looking for. But I'm sad that there's more needless deprecations upstream with no clear migration path 😞

Maybe when I have time I will try and resubmit a PR with the Median Flow tracker added under the new tracking structure, so I am not stuck on opencv v4.5.0 👐🏽

Thanks guys! 🙂🙏🏽

deadprogram commented 3 years ago

The problem was that I did not understand the tracking structure myself, and I had to do something relatively fast in order to support the rest of the update to OpenCV 4.5.1.

I am still not completely sure how to add those legacy trackers back in, or to add whatever is the new format.

I am going to reopen/rename this issue so we can continue to track it. Pun intended? :joy_cat:

ieliz commented 3 years ago

@ansoni-san, you can see all migration path here: https://github.com/opencv/opencv_contrib/pull/2737 https://github.com/opencv/opencv/pull/18838. These PR's are mentioned here: https://github.com/opencv/opencv/issues/18481. About deprecations: the OpenCV team were used a LaSOT-based benchmark for trackers comparing and some recent papers related to visual object tracking for choosing which trackers should be moved in new API and which should be in legacy. It is also mentioned in the issue about the new API (with links and arguments).