I've just been successful in building on Win XP with VS 2005, and started playing with panomatic_nopatent :). With the default settings from the readme, on a 2 row, 360 panorama, I'm finding a number of false matches. I'd like to provide helpful input, or other help, however I can.
I'm particularly interested in the case of pictures taken on a panoramic head, so they are known to be spaced on a phi/elevation grid. What kinds of cases is this algorithm suited for? What would give it problems? My problem panorama has varying white balance and exposure, for example. I think you mentioned some research papers about the algorithm - can you point me to them? Thanks, Aron On Feb 12, 9:24 am, Pablo d'Angelo <pablo.dang...@web.de> wrote: > Pablo d'Angelo wrote: > > > Currently, it should be a drop in replacement. A new name would be nice. > > > There is no way to build my extended package without the SURF > > descriptor, so its not yet suitable for general redistribution, some > > more small modification to the build scripts are necessary. > > I just changed the build configuration, so that by default, the SURF > descriptor is not compiled. See the README if you want to build with > support for SURF. > > ciao > Pablo -- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
