> As long as you have implemented interesting computer vision algorithm it's
> interesting for libmv.
> Libmv focus on clean implementation of computer vision stuff.
The routines I have in mind are
1. Computation of focal length and camera orientation from vanishing
lines for two axes (the same as this
http://www.youtube.com/watch?v=BRM7WXU5GrY)
2. Computation of optical center coordinates from vanishing lines for
three axes
3. Computation of camera orientation from a known focal length and
vanishing lines for one axis.
4. Reconstruction of 3D geometry with rectangular faces (see
http://vimeo.com/35153437 at 1:00)
These, especially the first three, are pretty simple compared to the
motion tracking code currently in libmv and clean and self contained
implementations are definitely possible.
> I have already start a basic UI some month ago to draw lines, it could be
> used as a start. The vanishing constrain as the SketchUp perform is another
> story I think...
Cool. What do you mean by "the vanishing constraint"? For routines
1-3, what's needed in terms of UI is a variable number of line
segments with adjustable endpoints plus the ability to draw an image
and lines on top of it. Not that complicated in other words. Routine 4
requires a slightly more complex UI allowing extrusion of quads and
adjustment of their vertices.
If I decide to give this a go, I'll probably focus on 1-3 to begin
with.
>
>
>
>
>
>
>
>
>
> > Hello everyone,
>
> > some time ago I put together an add-on for Blender that does camera
> > calibration (focal length and camera orientation) based on still
> > images. More info and source code is available here:
> >
http://code.google.com/p/blam/.
>
> > Would it make sense to integrate such functionality into libmv or is
> > it beyond the scope of the library? The reason I'm asking is that I'm
> > investigating what it would take to integrate photo matching (with a
> > UI similar to that of SketchUphttp://
www.youtube.com/watch?v=BRM7WXU5GrY)