[ptx] Even more SIFT successes

[Ed Halley]

I think there's room for both panosifter (if I've got it right) and for
autoconnecting the images.

* Images tab (and toolbar) can have any magical "find the right images
out of a pile of images" features.  If that magic also gives an initial
set of control points, then fine.

* Control Points tab (and toolbar) can have any magical "associate
points between the two selected images" features.

* I think it's okay for the toolbar to have "associate points between
any likely pairs of images" features, but that shouldn't be found in the
Control Points tab itself, since those are all clearly related to a
given selected pair of images.  It's sufficiently magic that people may
use it without even looking at the Control Points tab.

On a separate note, if there is an internal and/or multiple external
choices for a given feature, the user should be able to select it.  For
example, you should be able to choose from Nona or PTStitcher for the
rendering tab.  For feature-matching, you might need another similar
choice.

Is there any need to rethink the feature markers situation?  SIFT just
finds prominent items in one image, right?  So do we need to visualize
new markers that have not been associated/tied to other images?

I never completed a revision of the toolbar buttons, but they should be
color-keyed and ordered to their function in producing a panoramic
image.  I'll offer more assistance there once we start playing with
options.

On Mon, 2004-01-19 at 10:29, Mike Runge wrote:
> I think one of the earliest goal for hugin was to create a user-friendly
> interface to pano-tools. Meanwhile it has become much more :-)
> But panosifter within hugin could be a good chance to help newbies having an
> easy start. So I would not hide it for advanced use. I would try to make it
> the default or a part of a wizard function?!
> 
> Maybe another function in hugin would be helpful, that cleans up some extreme
> mismatching controlpoints for image pairs with a lot of controlpoints?! Or
> the wizard could recommend a list of actions (deleting specific points,
> etc.)
> 
> Maybe the future use of hugin could be to start with panosifter and (for
> advanced users) clean up some problems and optimize by hand?!
> 
> Just an idea ...
> 
> best, mike 
> 
>  
> On 1/19/2004, "Pablo d'Angelo" <pablo at mathematik.uni-ulm.de> wrote:
> 
> >On Sun, 18 Jan 2004, Ed Halley wrote:
> >
> >> On Sun, 2004-01-18 at 11:19, Sebastian Nowozin wrote:
> >> > You all must be becoming pretty tired of hearing of yet another success
> ;-)
> >>
> >> No, not at all.  There are two key milestones for me, speaking for the
> >> average user, however:
> >>
> >>  (1) we get the go-ahead to use SIFT (or an alternative) in the product,
> >>  (2) the interface of hugin hides any external tool complexity.
> >
> >Any ideas for the interface? Should some functionality like in panosifter
> be
> >available in hugin, or should we just constrain ourself to matching the
> >loaded images, with a "create control points" button?
> >
> >ciao
> >  Pablo
> >--
> >http://wurm.wohnheim.uni-ulm.de/~redman/
> >Please use PGP
> >
> >
-- 
[ e d @ h a l l e y . c c ]