search

dddvision / functionalnavigation

Trajectory Optimization Manager for Multiple Algorithms and Sensors (TOMMAS)
3 stars 4 forks source link

OpticalFlowOpenCV should only find graph edges when there is image motion #20

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

1. When using ThesisDataDDiel, OpticalFlowOpenCV gets bogged down even though 
there is virtually no image motion for the first few seconds.

What is the expected output? What do you see instead?

The findEdges function should return no graph edges until the camera moves 
substantially.

Original issue reported on code.google.com by dddvis...@gmail.com on 23 Jul 2010 at 8:03

GoogleCodeExporter commented 9 years ago 
This is more of an enhancement to Optical Flow than a defect.

Original comment by dddvis...@gmail.com on 20 Sep 2010 at 9:44

GoogleCodeExporter commented 9 years ago 
The function description for findEdges has changed, such that the current 
behavior of OpticalFlowOpenCV is as expected.

Original comment by dddvis...@gmail.com on 13 Oct 2010 at 4:58