Hi Terry and Bruno, > >> I'm pretty sure this is not how it is supposed to work. Thomas has > >> actually reimplemented all the logic from gigastart within Hugin, > >> i.e. what you enter for Program and Arguments are settings for a > >> 'normal' control point detector such as autopano-sift-c or > >> panomatic. > >I assume from this that the trick is to set up a number of new > >detector definitions, all using APSC (or whatever) but each having a > >different 'Type', and a different name so that they can be selected > >from the 'images' tab for a particular project. > > Yes, I think that is the idea. >
You are right, that was the idea. > gigastart creates a vast number of temporary files, but these are > reused by the Makefile system, so images are only opened once for > classifying features (though looking at the code, I don't see how > gigastart would work from the Hugin GUI as it is). > > Calling autopano-sift-c multiple times will result in a lot of > duplicated work, probably what is needed is to go back to the old > autopano-c-complete.sh script which will cache features as .key > files between runs. I'm aware of this drawback. Using the current approach enables the use of any cp detector (autopano-sift-c, panomatic or even Pablos new patent-free generator). I implemented some checks so that each image pair is only checked once. Implementing a two step approach would be possible. This would limit this setting to autopano-sift-c and it would create many temporary files. Thomas
-- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
