On Thu 11-Feb-2010 at 09:18 +0100, Harry van der Wolf wrote:
I'm not totally happy with the name panomatic is that is already an existing name for an existing CP matcher/detector. Can't we call the panomatic binary something like "cp_matcher" or "hugin_matcher" or "hugin_cp_matcher" or anything else logical, not interfering and confusing with an existing program.
'panomatic' is ok so long as it replaces the existing panomatic, and the panomatic webpage indicates this.
..but I think that ultimately this needs to be merged into Hugin and built as a Hugin tool, for two reasons:
1. The best interface we have for specifying parameters is a .pto project, this works very well for autopano-sift-c and the various wrappers in Panotools::Script. So the control point generator may as well use the Hugin model and parser for this.
2. Feature classification really needs to be done with re-projected data, again the Hugin libraries are best placed to do this (the approach that the old match-n-shift wrapper took to create temporary stereographic files with PTmender had lots of problems).
-- 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 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
