Thomas,

On Friday, 2019-03-22 10:32:45 -0700, you wrote:

> ...
> Images with the same lens (can) share same the lens parameters. Images with 
> the same stack (can) share the same image positions.

That clarifies it sufficiently.

> ...
>         Why do scripter always try to ignore a GUI?

Probably simply because a GUI doesn't lend itself to scripting ... :-)

Scripters, or at least myself tend to read manual pages.

> ...
> >                                    But are you going to say the I should 
> > add "v,!v0" to the list of variables to be optimized? 
> >
> Yes.

I tested that and got the following results in the final PTO file:

   # image lines
   #-hugin  cropFactor=1
   i w2552 h3508 f0 v10 Ra0 Rb0 Rc0 Rd0 Re0 Eev0 Er1 Eb1 r0 p0 y-4 TrX0 TrY0 
TrZ0 Tpy0 Tpp0 j0 a0 b0 c0 d-11.6267144999655 e58.0991796617598 g0 t0 Va1 Vb0 
Vc0 Vd0 Vx0 Vy0  Vm5 n"/home/rainer/devel/Test2-p1f/.0010.tif"
   #-hugin  cropFactor=1
   i w2552 h3508 f0 v10.0038583257815 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 
r179.973784393974 p0.564280695740596 y5.38605841280236 TrX0 TrY0 TrZ0 Tpy0 Tpp0 
j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0  Vm5 
n"/home/rainer/devel/Test2-p1f/.0020.tif"
   #-hugin  cropFactor=1
   i w2552 h3508 f0 v10.0040202229141 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 
r-179.533589935293 p0.528362597527063 y4.02695090314842 TrX0 TrY0 TrZ0 Tpy0 
Tpp0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0  Vm5 
n"/home/rainer/devel/Test2-p1f/.0030.tif"


   # specify variables that should be optimized
   v d0
   v e0
   v v1
   v r1
   v p1
   v y1
   v v2
   v r2
   v p2
   v y2
   v

Variables "v1" and "v2" roughly changed about four thousandths.  Is that
significant or is that simply not worth it?

> ...
> In the first case all images have the same dimensions and are therefore 
> treated as shooting with the same lens.
> In the second case the third images has different dimensions and is 
> therefore treated as a separated lens.

You are right.   That was a glitch in my script which used a wrong paper
format for the third scan.  This has meanwhile been fixed.

> > Again the second image has "v=0" while the value for the first and third 
> > ...
> Yes. This is not a odd value, this is mean that v is linked to image 0.

By inspecting  the various PTO files  I created,  I meanwhile found that
out myself,  or at least I strongly suspected it.  Thanks for confirming
that :-)

> ...
> > Well,  I'm on  Hugin 2015.0.0.   Does this version  already contain this 
> > assistant, and if yes, where do I find it?  
> 
> No. It is too old. 

Ok,  so I will clone  the source repository  and install  from there.  I
have sufficiently automated this process via a scrip t (again no GUI :-)
so this is not a big deal ...

Thanks for your help.

Sincerely,
  Rainer

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/23702.30960.219952.233695%40woitok.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to