Re: [hugin-ptx] Multi-row panoramas

[Stanley Green]

I tried stitching different pair combinations.
Row 1 & 3: No problem
Row 1 & 2: No problem
Row 2 & 3: No problem
The stitching problems only occur when using all three rows.

[Greg 'groggy' Lehey]

On Tuesday, 22 August 2023 at 6:57:45 -0400, Stanley Green wrote:
> I tried stitching different pair combinations.

A lot of detail missing here.

> Row 1 & 3: No problem
> Row 1 & 2: No problem
> Row 2 & 3: No problem

Except that the second and third variants only give you part of the
pano.

> The stitching problems only occur when using all three rows.

And what were they?

We've gone to a lot of trouble to investigate your problems. One of
them seems to be lack of adequate problem reporting. You don't even
say which method(s) you tried.

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.php

[Stanley Green]

Thank you Greg, I really appreciate all the work you guys are putting into solving my problem

> On Aug 22, 2023, at 7:48 AM, Greg 'groggy' Lehey <groo...@gmail.com> wrote:
>
> On Tuesday, 22 August 2023 at 6:57:45 -0400, Stanley Green wrote:
>> I tried stitching different pair combinations.
>
> A lot of detail missing here.
>
>> Row 1 & 3: No problem
>> Row 1 & 2: No problem
>> Row 2 & 3: No problem
>
> Except that the second and third variants only give you part of the
> pano.

That is correct. I was only trying to determine if row corruption is causing the problem. It does not look like row corruption is the problem.

>
>> The stitching problems only occur when using all three rows.
>
> And what were they?

When I tried to stitch all three rows, Hugin thought that they were a stack and produced a stitch that bore no resemblance to the scene.

>
> We've gone to a lot of trouble to investigate your problems. One of
> them seems to be lack of adequate problem reporting. You don't even
> say which method(s) you tried.

Sorry, I used the Simple interface with the Assistant screen. I loaded the images, tapped Align, and then hit Create Panorama

>
> 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.php
>

> --
> 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/20230822114819.GI55746%40eureka.lemis.com.

[Greg 'groggy' Lehey]

On Tuesday, 22 August 2023 at 8:24:24 -0400, Stanley Green wrote:
> Thank you Greg, I really appreciate all the work you guys are putting into solving my problem
>
>> On Aug 22, 2023, at 7:48 AM, Greg 'groggy' Lehey <groo...@gmail.com> wrote:
>>
>> On Tuesday, 22 August 2023 at 6:57:45 -0400, Stanley Green wrote:
>>> The stitching problems only occur when using all three rows.
>>
>> And what were they?
>

> When I tried to stitch all three rows, Hugin thought that they were
> a stack and produced a stitch that bore no resemblance to the scene.

You did read this, right?

On Tuesday, 22 August 2023 at 10:27:39 +1000, Greg 'groggy' Lehey wrote:
>
> 1. Loading the files produced the popup
>
> Hugin has image stacks detected in the added images and will
> assign corresponding stack numbers to the images. Should the
> position of images in each stack be linked?
>
> That's incorrect. There are no image stacks here, so you should
> answer No. I've almost never seen this message, and I suspect it
> comes here because of the overlap between images. 30% should be
> enough. This will give you fewer images and will greatly reduce
> the stitching time.

You can see an image of this popup at
http://www.lemis.com/grog/photos/Onephoto.php?dirdate=20230817&image=/grog/Photos/20230817/Hugin-fail-2.png

Did you not see it? I've gone to the trouble to set the simple
interface, but the message still appears. You should have selected
the first option ("Don't link position"). Did you do this? Or did
the popup not appear?

[Stanley Green]

The pop-up did occur and I chose do not link. The resulting image was very wide and narrow.

Sent from my iPhone

> On Aug 22, 2023, at 8:33 PM, Greg 'groggy' Lehey <groo...@gmail.com> wrote:

> --
> 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/20230823003314.GA72095%40eureka.lemis.com.

[Stanley Green]

I chose do not link

Sent from my iPhone

> On Aug 22, 2023, at 9:00 PM, Stanley Green <gree...@verizon.net> wrote:
>
> The pop-up did occur and I chose do not link. The resulting image was very wide and narrow.

[Greg 'groggy' Lehey]

On Tuesday, 22 August 2023 at 20:54:51 -0400, Hugin developers list wrote:
> The pop-up did occur and I chose do not link. The resulting image was very wide and narrow.

Both wide and narrow?

I have difficulty believing this. I've tried all three answers and
find that if I select "Link position", I get a panorama that is half
the expected width, and also ridiculous error values (667 average,
1297 maximum). My guess is that this is what you selected.

The other two both generate what appear to be similar images. Would
you please check again? Specifically, you want the selection on the
left "Don't link position".

[Stanley Green]

I am obviously confused, I tried so many things yesterday that I am getting the results mixed up. I am going to stop trying to remember and repeat the exercise.

> --
> 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/20230823033739.GB72095%40eureka.lemis.com.

[Stanley Green]

Greg

This time I followed you instructions and now it seems to be working.

Thank you VERY much for your patience and help

Stan

I have attached a series of screen shots showing what I did

I chose the first option, “Don’t assign stacks”

I chose, “Exposure corrected, low dynamic range”

Success!!

[Stanley Green]

Thanks to Greg & David, there is "Joy in Mudville”

I have tried this several times and I am now batting 1000 on getting a successful multi-row panorama.

Here is a summary that shows what is working for me. Please let me know if I missed something.

One thing I noticed that each time I tried this, I got a slightly different number of Control Points and a slight difference in the Mean error statistics

[Claudio Rocha]

II'll share what I do with multirow panoramas.

In my case the problem was that no matter what I did, even using multirow mode, Hugin would find Control Points in images that didn't belong on adjacent rows or columns, messing the final alignment. I had to go in and cleanup manually, wasting a lot of time.

Starting with a tiled array with rows a and columns like this:

A1 A2 A3 A4

B1 B2 B3 B4

C1 C2 C3 C4

For my needs I needed to find only the matching points in images that were directly adjacent instead of trying to find connecting points in all of the images. For example: for the tile B3 I needed only Control points on A3, B4 C3, and B2 

A1 A2 A3 A4
B1 B2 B3 B4
C1 C2 C3 C4

My workflow was 

1- Create a new project for each row (A1, A2, A3, etc), find the control points and.

2- Create a new project for each column (A1, B1, C1, etc), and find the control points. 

3- Merge all projects containing rows and columns using pto_merge. This allows all the images to be in the same project with their respective Control Points.

4- Create panorama using the resulting file.

I creates a script that works in Linux to automate the procedure.

Note that in my case the camera is moving linearly on a track, and the camera positions are different for each row and column, so I needed to create a new lens for each picture. Feel free to modify the script for your needs

I hope someone finds this useful