Am Montag, 27. Mai 2019 02:46:27 UTC+2 schrieb Kurt Hillig:
>
> All of the CP distance values I've been looking at are from the CP list
> (which I usually sort in decreasing order, as pairs with very large
> distances are often from cpfind misidentifying a pair) - I generally keep
> this list
All of the CP distance values I've been looking at are from the CP list
(which I usually sort in decreasing order, as pairs with very large
distances are often from cpfind misidentifying a pair) - I generally keep
this list displayed on my second monitor while I'm working (in Expert
mode). A w
Then it looks like hugin for measuring errors uses "pixels in the output
image" as unit. Which might be as good as any other potential unit as all
images are distorted during stitching and the definition of "pixels" in the
input images therefore might change depending which part of the image is
mea
Hi,
I think one important thing to observe is the size of the output. By
default Hugin starts with a 3000x1500 equirectangular, and I place CPs and
do many optimizations with this output size. Lter, when I start to generate
bigger "previews", or the biggest, final result, the errors apparentl
Am Donnerstag, 23. Mai 2019 18:27:01 UTC+2 schrieb Dr. Kurt:
>
> After more experimentation with just a pair of images (separated in yaw by
> about 7º), I find that the reported distances are dependent on the size of
> the active area in the quick preview window and the image position within
>
