[ptx] Autopano 1.03 Beta 2

[alexandre jenny]

> I think the following points are nice for integration into 
> the frontends:
> 
> 1. option to output only one panorama, as the frontends
>    (hugin/ptgui/ptassembler) do not support the recognizing panorama
>    paradigma, and will ignore the control points written into 
> the second
>    image.

No problem, I'll add that.
 
> 2. for case 1, it would be nice to be able to specify an output file.

That's planned to be able to specify the output folder. I can also put the
name
in the specification.

> 3. The control points in the project files are not subpixel accurate,
>    but rounded to integers.

There are in the .oto file format. See below.

> 4. Usually the images of one project share the same lens 
> settings. It would
>    be nice if the project files would reflect that, example:
> 
> Instead of:
> 
> --------------------------
> #-imgfile 1600 1200 "sta_3135.jpg"
> o f0 y+0.000000 r+0.000000 p+0.000000 u20 d0.000000 e0.000000 
> v70.000000 a0.000000 b0.000000 c0.000000 #-imgfile 1600 1200 
> "stb_3136.jpg" o f0 y+0.000000 r+0.000000 p+0.000000 u20 
> d0.000000 e0.000000 v70.000000 a0.000000 b0.000000 c0.000000
> --------------------------
> 
> use
> 
> --------------------------
> #-imgfile 1600 1200 "sta_3135.jpg"
> o f0 y+0.000000 r+0.000000 p+0.000000 u20 d0.000000 e0.000000 
> v70.000000 a0.000000 b0.000000 c0.000000 #-imgfile 1600 1200 
> "sta_3136.jpg" o f0 y+0.000000 r+0.000000 p+0.000000 u20 d=0 
> e=0 v=0 a=0 b=0 c=0
> --------------------------
> 
> if the images are of the same size. Otherwise hugin will not 
> recognize that the variables are linked, and treat every 
> images distortion/fov value separately.

No problem.

> 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. 
 
> How does the PCA-SIFT compare to the normal SIFT? Is there a 
> big difference?

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.

---
Here is the copy of my email to Max and Joost for autopano integration.
---

I came up with this solution :
- autopano can now be launched with the files names in the command line (you
didn't need to copy the files into a temporary folder).
- projects files are created in the same folder as the input pictures. (once
more, no need to copy the pictures).
- The ouput of autopano will be a standard project file I called
'pano*'.oto. 
The syntax will be really similar to the other type of PanoTools projects.
Here is a example :

--- starts here
# oto project file generated by autopano

# input images:
#-imgfile 800 528 "D:\- Dev -\autopano\1.JPG"
o f0 y+0.000000 r+0.000000 p+0.000000 u20 d0.000000 e0.000000 v70.000000
a0.000000 b0.000000 c0.000000 
... 
#-imgfile 528 800 "D:\- Dev -\autopano\2.JPG" 
o f0 y+0.000000 r+0.000000 p+0.000000 u20 d0.000000 e0.000000 v70.000000
a0.000000 b0.000000 c0.000000

# Control points:
c n0 N1 x+141.1711 y+405.2382 X+121.7594 Y+141.2025
# Control Point No 0: 1.00000
...
c n0 N1 x+750.8411 y+300.9430 X+226.1197 Y+750.7546
# Control Point No 36: 1.00000
c n0 N1 x+779.9396 y+475.8783 X+51.1630 Y+779.9338
# Control Point No 38: 1.00000
--- ends here

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).
- 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).
In this way, the integration should be robust and will not change again for
the next version of autopano.


---


  Alexandre