Hoi Harry, Thank you for the whole information about sieve size width height. We need more such practical info and we should expect this to be a "frequently asked question" (i.e. add it to the Hugin FAQ [0] ).
We need to determine whether the optimal sieve parameters depend on only on the lens type (fisheye vs. rectilinear lens); or if they also depend on focal distance; on image size; and maybe on other factors as well. With such a body of knowledge, maybe it is possible to expand cpfind with an "auto" mode that automatically adjusts the sieve based on the type of input images? On December 25, 2010 05:03:24 pm Harry van der Wolf wrote: > Then I did a final run with "--sieve1width 50 --sieve1height 50 > --sieve1size 300" (no fullscale). This generated 64 CPs with only one > image not connected: the 20101109_IMGP1465_KX.jpg, which is the nadir > image. (From my limited knowledge this is always a hard image for the CPs, > or not?) well, yes, the nadir is a difficult image, but not necessarily in terms of CP detection. It is difficult because often we move the tripod or monopod to take it and so it may have more parallax. In terms of feature detection it is the same as any other picture, and depends on the availability of features. > Optimization of the panos was weak to rubbish, be it that I don't have > experience with fisheye panos, so maybe I did something not completely > right. possible. did you check visually if the detected CP correspond? this is what we need now. > Is there a way to make a poll to check the percentages of: > - 360x180 degree only pano makers > - 360 degree pano makers > - wide angle pano makers. I don't think we need such a poll. There are enough users in all of these categories (or at least at the two extremes) to warrant support for both. For now it will be FAQ-support, until some logic will come along to automagically determine the right sieve parameters. I started [1]. Yuv [0] <http://wiki.panotools.org/Hugin_FAQ> [1] <http://wiki.panotools.org/Hugin_FAQ#cpfind:_not_enough_control_points_generated>
signature.asc
Description: This is a digitally signed message part.
