Auto calculation of Yaw, pitch and roll failed in some computers

[Parasar Ghimire]

Hello everyone, 

I am just a random user of HUGIN. I use it to create 360 virtual tours for a website. 

I am using GoPro to take 5 horizontal shots, 1 zenith shot and 2 nadir shots. I import the 8 images to HUGIN and Align them using Circular Fisheye lens and let the software do its work. It auto calculates the yaw, pitch and roll and based on that identifies the control points.

Where I am having problem is that, it works on some computers and does not work on others for the same 8 photos. I am using the same set of photos to do this test on different computers.

I cannot standardize the procedure for others to follow because of this. If anyone has faced the same problem or would like to address this issue. Please reply and I can supply the set of photos for you to check yourself.

[T. Modes]

Parasar Ghimire schrieb am Donnerstag, 1. Oktober 2020 um 15:33:30 UTC+2:

Where I am having problem is that, it works on some computers and does not work on others for the same 8 photos. I am using the same set of photos to do this test on different computers.

I cannot standardize the procedure for others to follow because of this. If anyone has faced the same problem or would like to address this issue. Please reply and I can supply the set of photos for you to check yourself.

Without seeing an example set it is not possible to advice something. So if you could provide a sample set, this would be nice, so we could have an own look on it.

[Parasar Ghimire]

Hi Thomas,

Thanks for replying. Please find the attached images. This set of pictures works on my computer when I align them but doesn't work on other computers. 

Please advise me if I am missing something.

My general approach is:

1. import images into HUGIN

2. Set Lens type as Circular fisheye and focal length as 3.154

3. Click Align to auto-detect control points. 

The results are fine on my computers but fail in others as it isn't able to calculate yaw, pitch, and roll values. This is why I cannot recommend and standardize the process.

https://drive.google.com/file/d/1AlkHTbkZIKkAhTS1QxT4Uh5SQLl6KV12/view?usp=sharing

[Greg 'groggy' Lehey]

On Thursday, 1 October 2020 at 21:46:17 -0700, Parasar Ghimire wrote:
> Hi Thomas,
> Thanks for replying. Please find the attached images. This set of pictures
> works on my computer when I align them but doesn't work on other computers.
> Please advise me if I am missing something.
> My general approach is:
> 1. import images into HUGIN
> 2. Set Lens type as Circular fisheye and focal length as 3.154
> 3. Click Align to auto-detect control points.
>
> The results are fine on my computers but fail in others as it isn't able to
> calculate yaw, pitch, and roll values. This is why I cannot recommend and
> standardize the process.
>
> https://drive.google.com/file/d/1AlkHTbkZIKkAhTS1QxT4Uh5SQLl6KV12/view?usp=sharing

OK, I've taken a look at the images. I'm amazed that you can get them
to align at all. There's barely any overlap. And most certainly the
images as shown were not taken with a circular fisheye. I selected
full frame fisheye (which is probably also stretching the case) and
got the first five without trouble. I needed to add the sixth
manually. And that's as far as I got. I couldn't recognize any
connection between the last two and the rest. I think it speaks
highly for Hugin that any version works.

Why don't you try again with more images? Consider that the control
point detector needs to find at least 6 control points between images.
Think what points might be of use and ensure that they appear in at
least two images. If all else fails (like the ground in your images)
you could consider putting something like a lens cap on the ground and
taking it in different images, then removing the cap and taking more
images, finally omitting the images with the lens cap from the final
panorama.

And why does this work on some computers and not others? I've seen
similar issues in the past, but first you should check if you have the
same control point detectors on all the computers.

Greg
--
Sent from my desktop computer.
Finger groo...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

[giuseppe porciani]

Hi,

I gave it a try. In my case Hugin does not ask for lens parameters because the exif data give rectilinear: 98 degrees Hfov, which seems the case considering the relatively low distortion. In the five equatorial pictures CP detects enough control points. It does not in the zenith and nadir pictures. Adding manually control points in these pictures should work. Perhaps problems come from the not correct parameters given for the lens. ..

Regards,

Giuseppe

--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/20201002064845.GB2619%40eureka.lemis.com.

[giuseppe porciani]

Hi,

Sorry, I made some mistakes and bad assumptions.

I tried with these lens parameters: fisheye full frame; focal length 2,8; crop factor 5,6.

It stitches. From the exif data it seems you use a gopro 6 black. I took sensor and lens data from specs of this gopro version. Hope that may help.

Regards,

Giuseppe

[Luís Henrique Camargo Quiroz]

   Maybe discrepancies in lensfun? Not all the same version, not all updated?

  Run lensfun-update-data.  Hugin only can benefit from good lens parameters if they can be found in the database.  http://lensfun.sourceforge.net/usage/

  Luís Henrique

To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/CAO0N8z0qtO9-_FVC1t5mOK6oSSAaCU%3DGDRqNHfKr360%2B9uNVNw%40mail.gmail.com.

--

--
Luis Henrique Camargo Quiroz
http://luishcq.br.tripod.com - http://www.christusrex.org/www2/cantgreg
http://panoramaslh.net/

[T. Modes]

Hi Parasar,

Am Freitag, 2. Oktober 2020 06:46:17 UTC+2 schrieb Parasar Ghimire:

Hi Thomas,

Thanks for replying. Please find the attached images. This set of pictures works on my computer when I align them but doesn't work on other computers. 

Please advise me if I am missing something.

My general approach is:

1. import images into HUGIN

2. Set Lens type as Circular fisheye and focal length as 3.154

3. Click Align to auto-detect control points. 

The main problem with the provided sample set is that some images have been rotated physically and some not (images 1-6 are portrait, images 8 and 9 landscape).

This results that when you import the images into Hugin 2 different lenses are assigned and when you set the lens type to circular fisheye only the first lens is changed.

This confuses the control point finder and it fails to align.

If I manually rotate the last 2 images also to portrait format, the assistant works fine and aligns the pano. There is enough overlap for Hugin

If this does not work on all computers then on these computer the camera/lens is already in the local camera/lens database with different settings and when importing the images these settings are read from the database and used then.

So after importing the images check the lens projection, focal length and multiplier on these computer after importing images.

Thomas

@Luis: Hugin is not using the lensfun database. So this hint does not apply.