Am Mittwoch, 20. März 2019 18:11:45 UTC+1 schrieb Rainer Woitok:
>
> These pointers are still missing.  Isn't there any technical or theoret- 
> ical documentation  of the concepts  used in Hugin?   

Images with the same lens (can) share same the lens parameters. Images with 
the same stack (can) share the same image positions.
That's all. Open a project in Hugin and select Group by lens/stack on the 
images tab in the panorama editor. Then you see which parameters are 
linked. Why do scripter always try to ignore a GUI?
 

> > For scanned images this lens concept is not so good. So you would like 
> to 
> > optimize the field of view for each individual image. This can be 
> achieved 
> > by assigning each image an own lens or by unlink the fov parameter of 
> this 
> > lens (pto_var --unlink v0). 
>
> The latter approach seems cheaper from a programmer's point of view, be- 
> cause the former requires  to dynamically generate the  "i1,...,in" list 
> from the number of input images.   But are you going to say the I should 
> add "v,!v0" to the list of variables to be optimized? 
>
Yes.


> When I provide two input files, "pto_gen" prints 
>
>    Generating pto file... 
>    Reading .../.0010.tif... 
>    Reading .../.0020.tif... 
>
>    Assigned 1 lenses. 
>
>
> Mind the "v10" for the first image and the "v=0" for the second.  When I 
> provide three input files, "pto_gen" prints 
>
>    Generating pto file... 
>    Reading .../.0010.tif... 
>    Reading .../.0020.tif... 
>    Reading .../.0030.tif... 
>
>    Assigned 2 lenses. 
>    Project contains more than one lens, but you requested to assign 
>    stacks. This is not supported. Therefore stacks will not be 
>    assigned. 
>
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.


> Again the second image has "v=0" while the value for the first and third 
> image is correct.   This odd value will  only be corrected  when I issue 
> either of the commands  "pto_var --unlink v0"  or  "pto_lensstack --new- 
> lens i1,i2".  Is this expected behaviour? 
>
Yes. This is not a odd value, this is mean that v is linked to image 0.


> Why are "d1", "e1", "g1", and "t1" not optimized? 
>
They are optimized via the linked variables. As said open the project in 
the GUI and inspect the image variables when selecting group by.

>
> > PS: Current Hugin version contains also an user-defined assistant for 
> > scanned images. 
>
> 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. 

> But I would prefer a command 
> line solution over a GUI. 
>
Who said that the assistant is in the GUI. There is also a command line 
interface.

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/df294c03-540a-44c4-bb50-701e7c4682b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to