[Soc-2011-dev] Weekly Progress Report #10 - libmv Tracker

Matthias Fauconneau matthias.fauconneau at gmail.com
Fri Jul 29 19:46:40 CEST 2011


Hi,

Complete formatted version of the report (with screenshots):
 http://wiki.blender.org/index.php/User:Matthias.fauconneau/GSoC2011

=== Week 10: July 22 - July 29 ===

* API: Support creating FloatImage without copying data.
* Merge uncalibrated reconstruction.
* New Distortion/Undistortion API:
** Compute lookup grid for fast warping of sequences.
** Support distortion/undistortion, float/ubyte, 1-4 channels using
generic programming.
** Bilinear sampling.
** Process 1920x1080 images in 25ms for ubyte and 50ms for float (on A64 2GHz).
* Learn Unit Testing workflow and prepare Intersect and Resect unit tests.
** Remove tests depending on dead code.
** Fix CameraIntrinsics test.
** Add Intersect test.

Fast image distortion and undistortion still need to be integrated to
Blender compositor.

Ideally, the renderer should support distortion directly instead of
resampling the rendered image.

=== Week 11: July 29 - August 5 ===

Once Keir is finished with the tracker refactor, we will be able to
improve and optimize it. Feature prediction could be added to help
avoid drifting markers.
Once the tracking works robustly in most case, we should improve
feature detection (with outlier rejection) to allow nearly automatic
tracking.

=== Week 12: August 5 - August 12 ===

Libmv will need to be refactored to remove all unused and unsupported parts.
Only methods relevant to tracking and reconstruction should be kept.
This simplification of libmv design will ease the maintenance, reduce
compile time,
decrease binary size, increase performance, and help attract contributors.

This step will also enable the integration of OpenCV calibration
methods on sane foundations, thus enabling Blender developers to add a
camera calibration interface without requiring a dependency on the
complete OpenCV framework.

=== Week 13: August 12 - August 19 ===

This week will be reserved to ensure the code is maintainable by
future contributors.
API documentation will be improved and the code will be better commented.


More information about the Soc-2011-dev mailing list