Re: [hugin-ptx] Re: Which optimizer to use on command line? (in looping script)

[T. Modes]

Am Freitag, 9. Februar 2018 07:52:23 UTC+1 schrieb Alister Ling:
>
> It works nicely! Thank you so much. 
>
Sorry, but you missed the point. Please reread my post again.
Cite:
>> When you exchange only the image in the project file (as shown in your 
pseudo-code) without 
>> modifying control points/adding new control points there is no point in 
executing autooptimiser.
>> The control points are the same, so the result of the autooptimiser is 
the nearly same as 
>> before (beside some little numeric error).

The first one of the sequence I do manually and save to  
> ZenithProc_preop.pto .
> Then I run the loop where the output of the optimiser ( -o ZenithProc.pto ) 
> becomes input to nona
>
> $com = "E:\\bin\\autooptimiser.exe -q -n -o ZenithProc.pto 
> ZenithProc_preop.pto ";
> # part1 pano:
> $com = "E:\\bin\\nona -m TIFF_m -o Zenith ZenithProc.pto Cam0.tif 
> Cam1.tif Cam2.tif";
># part 2 : enfuse/blend
> $com = "E:\\bin\\enfuse --output=Zenith.tif Zenith.tif 
> Zenith0001.tif Zenith0002.tif 2> PROC_ERR.txt";
>
This corresponds to loading ZenithProc.preop.pto in Hugin GUI, pressing 
optimize, then save again (and this 1500 times). Then you replace the 
images and remap the images and fused them.  

The autooptimiser runs quite quickly. 
>
Now to let the 1500 triplets process overnight. 
>
 You run autooptimiser for each triplet on the same input and so you will 
get always (nearly) the same output (because you don't change the control 
points)
So if you have a lot of time and want to heat your home...

-- 
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/44f77a12-2259-43c3-a8a1-cbc6476ba08f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Which optimizer to use on command line? (in looping script)

[Alister Ling]

It works nicely! Thank you so much. I will post a link to a small tutorial
on this in a couple of days.
The first one of the sequence I do manually and save to
ZenithProc_preop.pto .
Then I run the loop where the output of the optimiser ( -o ZenithProc.pto )
becomes input to nona

$com = "E:\\bin\\autooptimiser.exe -q -n -o ZenithProc.pto
ZenithProc_preop.pto ";
# part1 pano:
$com = "E:\\bin\\nona -m TIFF_m -o Zenith ZenithProc.pto Cam0.tif
Cam1.tif Cam2.tif";
   # part 2 : enfuse/blend
$com = "E:\\bin\\enfuse --output=Zenith.tif Zenith.tif
Zenith0001.tif Zenith0002.tif 2> PROC_ERR.txt";

The autooptimiser runs quite quickly.
Now to let the 1500 triplets process overnight.
Regards,
Alister.

On Sat, Feb 3, 2018 at 2:01 AM, T. Modes  wrote:

>
>
> Am Samstag, 3. Februar 2018 00:51:53 UTC+1 schrieb Alister Ling:
>>
>> Hi, which optimizer do I call on the command-line,
>>
> Use autooptimiser (PTOptimiser does not understand all advanced options in
> the Hugin project file).
>
> how and when?
>>
> You call it, when you changed control points and want to calculate the new
> positions based on the changed control points.
> The optimiser takes only the control points into account (but not the
> image content). It tries to find the solution (=a set of image positions
> and lens parameters) where the error of all control points is minimal.
> (Nona is then using this solution to do the remapping of the images, nona
> does not calculate these positions).
>
> A slightly long description: Each control point is connected with 2
> images, so you get 2 positions in the panorama (with the current image
> positions). Ideally these 2 positions would be identical, practically they
> have same displacement - this is the control point error.
> The optimiser starts with the current image positions in the pto file. It
> calculated the control point error for all control points. Then the
> optimiser changes the image positions (and lens parameters) a little and
> calculate the control point errors again (this is one iteration, as
> displayed in the progress window or the console).
> If there average error is reduced with the new positions it changes the
> image positions further in this direction. If the average error becomes
> bigger with the new positions it changes the parameters in the other
> direction. (This is a simplified description of the algorithm). This is
> done until the average error does not decrease further.
>
>
>> It looks like I should call optimizer before nona; but I already have a
>> pto file with all the parameters made from my manual execution of hugin.
>> But in the nona documentation it says it ignores the optimisation lines in
>> the pto file. So I am confused and would appreciate some pointers.
>>
>> In the loop below, the optimizer does not get called, and I end up with
>> double stars in my sky (that's why I need your help!). In my manual
>> production I have 7 control points between each pair and it stitches nicely.
>>
>> I am using a script to loop several hundred triplets using nona and
>> enfuse (here in pseudo-code)
>>
> When you exchange only the image in the project file (as shown in your
> pseudo-code) without modifying control points/adding new control points
> there is no point in executing autooptimiser.
> The control points are the same, so the result of the autooptimiser is the
> nearly same as before (beside some little numeric error).
>
> Thomas
>
>>
>> --
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "hugin and other free panoramic software" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/hugin-ptx/JDBA5gKLA68/unsubscribe.
> To unsubscribe from this group and all its topics, 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/2f7c864a-bbf0-4750-93ca-85565eb16de5%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAE42BT85YdpVG2f_CP1_Tjr8SDXhLpgpELtTJ7WrNfwQqzuFUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.