[ptx] Re: Hugin stitching not working

[Carl von Einem]

Sean,

it's not the stitching thats wrong, you already messed up the 
optimization by only optimizing one picture:

# specify variables that should be optimized
v p1 r1 y1
v

better do something like:
v y0 p0 r0 p1 r1

now you optimize the yaw of one picture (one should stay fix as an 
anchor image), pitch and roll of both images.
I added several t1 control points (two points in one picture indicating 
a vertical line in the "doors":

# Control points:
c n0 N0 x400 y362 X381 Y775 t1
# Control Point No 0: 2.43714
c n0 N0 x612 y326 X609 Y768 t1
# Control Point No 1: 0.533513
c n0 N0 x868 y285 X889 Y867 t1
# Control Point No 2: 4.32838
c n1 N1 x535 y864 X532 Y323 t1
# Control Point No 3: 2.93463

and that optimized comfortably to

#-imgfile 960 1280 0 "045.jpg"
o f0 y0 r-1.36353 p8.94349 v=0 a=0 b=0 c=0 d=0 e=0 g=0 t=0
#-imgfile 960 1280 0 "046.jpg"
o f0 y22.2485 r0.42884 p10.4035 v=0 a=0 b=0 c=0 d=0 e=0 g=0 t=0

compare my y/p/r with your values:
y20.1366 n"045.jpg"
p-0.132258 r2.0 y-7.39216 n"046.jpg"

and I didn't even optimize for v or a/b/c yet.

Carl

btw tested with PTMac (cheating with BBEdit, my text editor) since I 
have no working installation of hugin yet. You see all the frontends 
work happily together :-)

> Subject:
> [ptx] 
> From:
> Sean Davis <seand at colorado.edu>
> Date:
> Wed, 6 Jul 2005 12:49:46 -0600
> To:
> ptx at email-lists.org
> 
> Hi
> 
> I just installed hugin from CVS, and am trying to follow the 'stitching two 
> photos together' hugin tutorial described at 
> http://hugin.sourceforge.net/tutorials/two-photos/en.shtml
> 
> However, when I do this, the final image I get is completely wrong!  The right 
> image is on the left, and it appears as though the program ignored all the 
> points I set.
> 
> I believe I have set and optimized the weight points properly.  I have posted 
> the two images (045.jpg and 046.jpg), the final image (test.jpg), and the 
> project file (test.pto) at my website http://paos.colorado.edu/~seand/hugin/
> 
> Does anyone have a clue whats wrong here?
> 
> Thanks,
> Sean
> 
> 
>