Public bug reported:
I am a new 'hugin' user and I've been playing with it for about a week
encountering various problems. I hope I've managed to make some
systematization of the problems, so this report is the first in a series
of reports I'm going to file.
System info as hugin reports it:
"
Public bug reported:
The report uses the same data with the same data import instructions as
bug #1856336.
Input data and evidence can be found in
https://cloud.mail.ru/public/3Xz6/4wnVcSp1c web folder.
Input .NEF files were imported the usual way. Then control points were
found automatically -
The control point error distances are calculated in the output space.
When you change the output size (or projection), it is expected that the
cp error distance changes. (This is a design decision in the underlying
panotools library.)
** Changed in: hugin
Status: New => Invalid
--
You
"The control point error distances are calculated in the output space" -
which action of mine changes output space ?
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1856345
Title:
Running
The photometric optimizer chooses by default 200 (random) points per
image for the optimization of the photometric parameters. Using every
pixel would be to computationally intensive. So for each invocation of
the photometric optimizer different points are used and therefore
different absolute
"The photometric optimizer chooses by default 200 (random) points per
image" - does the documentation mention that the points are random ?
Is there a way to make behavior deterministic ?
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to
Public bug reported:
The more detailed summary: running geometric optimizer after stitcher,
but on the same input data produces drastically different result.
The testcase uses the same input data as in bug #1856336. The system is
the same and the instructions to download input data are the same.
The displayed focal length is calculated from the field of view. When you
optimize "Everything", you optimize also field of view and therefore the "focal
length" is expected to change.
Also the given focal length (in EXIF) is sometime lower than the focal length
calculated from the field of
"The displayed focal length is calculated from the field of view" - this
requires elaboration.
The fundamental geometrical optics formula states (assuming infinitely
thin lens) :
1/distance_to_object + 1/distance_to_sensor = 1/focal_length
.
And we also have hyperfocal distance:
9 matches
Mail list logo
