[ptx] Autopano 1.03 Beta 2

[Pablo d'Angelo]

On Wed, 21 Jul 2004, Alexandre Jenny wrote:

> > I can compile a linux version as well, if you want to.
> 
> I'll try to it myself. I have to improve my knowledge of linux developpement
> tools. 

Do you still have the patches I send you for version 1.02?

> I didn't finished yet PCA sift. In fact, I already changed the feature
> calculation
> for the sift algorithm which is yet different from the original SIFT. This
> change
> really improved distinctiveness which was the goal of PCA.
> So my last job is to compare my changes to PCA which have another big
> advantages,
> The feature vectors are really shorter than sift, 32 bytes against 128. It
> will
> boost kdtree detection a lot.

Ah, interesting. doesn't that reduce the distinctiveness of the feature
vectors? Have you just reduced the number of patches that are considered
during building the feature vector or are you using less gradients for each
patch. (Hope I remember the algorithm correctly...)

> So the only think you will have to cope with is the opening of a .oto file, 
> which is quite the same as a standard Panotools file (one exception :
> controls points location are floats and not int : 
> I have a subpixel accuracy so I don't want to lose it, but you are free not
> to use it).

I'm not completely sure, but I think that PTOptimizer can read floats. and
even if it can't, it'll probably stop when it recongnizes the "."
Hugin supports float coordinates from version 0. (at least when
loading/saving projects). Soon it will also support subpixel accurate fine
tune.

So I guess it is save to enable floating point coordinates for the other
formats as well.

> - Finally, the launch of autopano could be done directly by some button or
> menu : Just provide files names in command line and analyse the .oto project
> after that. There's here 2 solutions : (keep the current project open and
> merge control points from .oto into but you have to probably remap Picture
> number, or just keep the setting of the current project, open the .oto as a
> new project and 
> fix settings).

I'll parse the control points out of the .oto file. Are the images in the
.oto file in the same order as specified on the command line?

This should work with the current hugin release as well (after adjusting the
call parameters, which default currently to the autopano-sift call
interface).

Probably I should detect which kind of autopano was selected by the user and
choose right arguments depending on the program name.

ciao
  Pablo