On Tuesday, August 16, 2022 at 3:25:26 PM UTC-4 Florian Königstein wrote:
>
>> But I took parts of the old code and built a command line utility named
>> Hugin2PTOptimizer that converts a Hugin .pto file to a .pto file readable
>> by PTOptimizer.
>> I have messed a bit around in the code and
On Friday, August 12, 2022 at 12:37:53 PM UTC-4 Florian Königstein wrote:
> Probably it's best here to first optimize only raw, pitch and roll and
> then only translations.
I gave that a lot of thought, and I have not yet coded/tested what I
decided to do instead. But I think there is a
>
> I hope you didn't enable any FOV optimization. I certainly think that is
> fundamentally broken in hugin and isn't safe to mix into any kind of
> controlled test.
>
No, I didn't optimize FOV.
>
>> And in ill-conditioned mathematical problems like here small differences
>> in roundoff
On Tuesday, August 9, 2022 at 1:38:07 PM UTC-4 Florian Königstein wrote:
> Some time ago I tried whether analytical calculation of the partial
> derivatives is better (faster convergence). I wrote code for analytical
> calculation (via automatic differentiation), but it seemed that there was
On Tue, Aug 9, 2022 at 12:12 PM Florian Königstein
wrote:
> The image DSC00293.JPG was missing. I took the image DSC00289.JPG as a
> (false) replacement for it.
> First, there are about 20 CPs with distances of about >9000. They are
> totally wrong correspondences. I deleted them.
>
I really
Some time ago I tried whether analytical calculation of the partial
derivatives is better (faster convergence). I wrote code for analytical
calculation (via automatic differentiation), but it seemed that there was
no advantage (longer time and little or no reduction in the number of
The image DSC00293.JPG was missing. I took the image DSC00289.JPG as a
(false) replacement for it.
First, there are about 20 CPs with distances of about >9000. They are
totally wrong correspondences. I deleted them.
I tested optimization only on Hugin++. It took about 10 seconds on my
computer
I worried this sidetrack of the discussion may be stopping someone who
knows more about the answers I'm looking for from replying in this thread.
I really want a better understanding of why results differ so much in the
same optimization problem among version and builds of pano13 (and maybe of
On Monday, August 8, 2022 at 3:29:44 PM UTC-4 Florian Königstein wrote:
> Before I answer to your post more detailed, could you please send me the
> images per Mail so that I can load the pano without the need for dummy
> images. Maybe the optimization was faster for me since some CPs were
>
I'd like to explain mathematically why estimating both translation and
rotation is difficult when the translation is small and the FOV is small:
Assume you have a CP with an x-coordinate 'x' (x-distance on the CCD image
sensor from the middle) , and the focal length is f. The "focal axis" is
I shoot lots of handheld panoramas. I'm relatively steady at holding my
camera and things come out fine rotating about the vertical center of my
stance. I have never had to use translation of any sort for these shots,
and optimization works pretty quickly.
I've found I get better results by
Before I answer to your post more detailed, could you please send me the
images per Mail so that I can load the pano without the need for dummy
images. Maybe the optimization was faster for me since some CPs were
deleted due to my dummy image. Having your images I can see the speed in
exactly
On Monday, August 8, 2022 at 11:32:07 AM UTC-4 Florian Königstein wrote:
> Hi John,
>
> Optimization ran fast for me,
>
What is "fast" and which hugin did you use?
It runs "fast" (17 to 36 seconds) using any build of pano13 with sparse
lev-mar. But I still want it to be faster and I want
Hi John,
without the images Hugin asks for loading them. I took some dummy image.
Hugin++ said that there were invalid CPs, probably due to other image
dimensions. Optimization ran fast for me, but I think I know where there is
the problem.
First I assume:
** You took the images in a
14 matches
Mail list logo
