On Tue 12-Jan-2010 at 14:36 -0800, Terry Duell wrote:
On Jan 13, 9:16 am, Bruno Postle <[email protected]> wrote:
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.
To add a bit of grist to the mill, I tried an amendment to the
definition of the APSC detector, choosing 'mutil-row panorama' and it
appears to be quite a lot slower than using gigastart as the hugin
detector. That is my impression.
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. Arguments would be (untested as usual):
--points %p --size 1600 --output %o %i
--
Bruno
--
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
