Re: [hugin-ptx] Re: first attempt at a spherical pano

2016-09-26 Thread Stefan Peter
Dear Michael Havens
Am 26.09.2016 um 15:18 schrieb Michael Havens:
> I get it... they got rid of the optimizer tab and moved the settings
> into Photos.

Not exactly. You still get an optimizer tab when you set the Optimize ->
Geometric setting to "Custom parameters" in the Photo tab.

With kind regards

Stefan Peter

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
(See https://en.wikipedia.org/wiki/Posting_style for details)

-- 
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/8203f938-6f28-0b6c-bd8a-a91c7b3144e9%40swissonline.ch.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Re: first attempt at a spherical pano

2016-09-26 Thread Michael Havens
I get it... they got rid of the optimizer tab and moved the settings into 
Photos.

-- 
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/ed2883ea-e2e9-41f5-baa3-80c7113e22ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Re: first attempt at a spherical pano

2016-09-26 Thread Michael Havens


On Monday, September 26, 2016 at 3:09:51 AM UTC-4, zarl wrote:
>
> Michael Havens wrote on 26.09.16 01:18: 
> > What does 'optimize' do? I just ran almost the entire process through to 
> > the end (2 hours) when I was rereading what I hadn't done when I noticed 
> > it was said I did not optimize it. So I stopped, optimized, and started 
> > the process again. BUT what does it do? 
>
> http://wiki.panotools.org/Hugin_Optimizer_tab 
>

Thank you for that. While reading through it I found 'optimizer tab'. I 
don't have an 'optimizer tab'. Only 'Photos', 'Masks', 'Control Points', 
and 'Stitcher' tabs. I can optimize with Edit-> optimize but no tab.

-- 
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/602cfa02-4ddc-45af-9f97-3d58ad81d9f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Re: Source code review

2016-09-26 Thread Bruno Postle


On 26 September 2016 10:17:22 BST, Bernd D wrote:
>
>Of course, this is not an error in cpfind. cpfind results can only be as 
>accurate as the input data. Without --fullscale, the accuracy is at least 
>halved. That may be acceptable. But I have total failures seen in the 
>absence of this option, which resulted that hugin run more than 3 hours on 
>a 25x25 mosaic of images with 1000x1000pix (Overlap approx 150pix). The
>pictures were taken on a scanning electron microscope.

This is a special case, Hugin has to assume that most input images are photos 
taken with Bayer sensors that have higher pixel resolution than necessary.

I haven't tested this, but it is also possible that downsizing the pictures 
removes high frequency artefacts that would confuse the feature detector 
(leading to better results for digital photos).

-- 
Bruno

-- 
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/15BE88EA-6BF8-4CAC-ABF3-5EE3017EBD1A%40postle.net.
For more options, visit https://groups.google.com/d/optout.


[hugin-ptx] Re: Source code review

2016-09-26 Thread Bernd D


Am Samstag, 24. September 2016 15:19:00 UTC+2 schrieb T. Modes:
>
>
>
> Am Dienstag, 20. September 2016 14:47:50 UTC+2 schrieb Bernd D:
>>
>> On site *Optimizer* in table *Image Orientation*, column *Trx*, *TrY*, 
>> *TrZ* show only rounded to integer values.
>>
> No. The values are shown with 1 digit. 
>
  Ok. And “0.04999” is show as “0” That's what I mean.

>
>>1. On site *Stitcher*, edit fields *Horizontal* and *Vertical* show 
>>only rounded to integer values.
>>
>> Yes. The optimal fov calculates with a resolution of 1 deg. And the most 
> use case is a panorama with a high fov. So for this use case you don't need 
> a higher resolution. 
>
No, the calculation is with double precision. Only the GUI Value is 
rounded. If you let the edit field untouched then hugin use the unrounded 
value.

For a 360° panorama with 1pix is 1° error = 1pix/1° * 360° = 28pix

>
>
>> Per default the *-–fullscale* option for *cpfind.exe* is not set. 
>> Without this option *cpfind* work not correct (find lesser CPs and 
>> misplace this). 
>>
> Please don't state such general statements. In most case cpfind works fine 
> without fullscale. There may be case where full scale is better suited, 
> e.g. your images with a very low resolution and a repeating pattern. But 
> this is specific to this use case and does not apply in general.
>
  

Sorry, I do not agree. It would have saved me several days troubleshooting 
if someone had warned me against this pitfall.

Of course, this is not an error in cpfind. cpfind results can only be as 
accurate as the input data. Without --fullscale, the accuracy is at least 
halved. That may be acceptable. But I have total failures seen in the 
absence of this option, which resulted that hugin run more than 3 hours on 
a 25x25 mosaic of images with 1000x1000pix (Overlap approx 150pix). The 
pictures were taken on a scanning electron microscope. After this time I 
have give up and kill the process. With --fullscale it needs the expected 
approximately 
30 minutes.

-- 
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/713298a1-b164-4c84-84d5-6675bbc5c62b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Re: first attempt at a spherical pano

2016-09-26 Thread Carl von Einem

Michael Havens wrote on 26.09.16 01:18:

What does 'optimize' do? I just ran almost the entire process through to
the end (2 hours) when I was rereading what I hadn't done when I noticed
it was said I did not optimize it. So I stopped, optimized, and started
the process again. BUT what does it do?


http://wiki.panotools.org/Hugin_Optimizer_tab


Further, is there any benefit in running it twice... threee, four times?


I think you should start with a simple horizontal, one row set of images 
taken from a tripod (don't forget about overlap) and play with that 
through the whole process of creating a 360° panorama without having to 
care about nadir and zenith. Once you get familiar with the process, 
include nadir and zenith images in the next step.


In the "tutorials" section of http://wiki.panotools.org/ I found a link 
to -> Panorama Tools - Using The Optimizer

http://www.johnhpanos.com/optitute.htm
(maybe a bit outdated at several points but I hope you'll get the image)

You can always use the Panotools wiki as a glossary. In Firefox you can 
easily add it to your list of search engines.


I also have a feeling that your knowledge of the operating system you're 
working with is rather basic. Maybe you can also find tutorials about 
that somewhere.


Carl

--
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/3308ed09-0247-9ab8-b05b-b962929371c3%40einem.net.
For more options, visit https://groups.google.com/d/optout.