Intel® Integrated Performance Primitives
Deliberate problems developing high-performance vision, signal, security, and storage applications.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
6814 Discussions

OpticalFlowPyrLK feature points

Adriaan_van_Os
New Contributor I
‎02-09-2020 05:56 AM
764 Views

The docs for OpticalFlowPyrLK don't explicitly state whether the pPrev array of initial coordinates of the feature-points is an input parameter or not. My impression however is that pPrev must be specified by the caller. The IPPI demo code in OpticalFlowPyrLK.c on the other hand, simply sets the pPrev array to zero values.

My questions:

1. So, is this just bad sample code or an undocumented something where OpticalFlowPyrLK figures out good feature points itself ?

2. OpticalFlowPyrLK is based on "Pyramidal Implementation of the Lucas Kanade Feature Tracker" by Jean-Yves Bouguet, of the Intel Corporation Microprocessor Research Labs. Chapter 3 "Feature Selection" of this document describes an the algorithm to select feature-points. How does that algorithm translate into IPPI calls ?

Regards,

Adriaan van Os

0 Kudos

Link Copied

1 Reply
Gennady_F_Intel
Moderator
‎02-12-2020 08:21 PM
764 Views

yes, this example contains some of the inconsistencies with the actual implementation and has to be redeveloped. We will try fix all of them.

Actually, the pPrev is in and out parameters and has to be initialized at the input to this function.

0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.