I think these CP strategies are interesting. APSC tended to give me 5 points in a corner a bit too often. So CPfind seems to be the way forward even if it will need some more options.
It should be fairly straghtforward to limit the number of CP's per image pair by some more or less clever strategy to throw away CP. My question on this discussion is: Are the buckets here referring to "feature points" in each image, or the actually paired feature points that become Control Points between images? To me it seems like the bucket-model is a good way to distribute feature-points, but actual Controll Point distribution depend utimately on actual overlap. And I would like the CPfind to find thousands of feature-points in order to eventually match tens of control points. Cheers /O 2011/8/30 Jeffrey Martin <360cit...@gmail.com> > Sorry Yuv but this is a completely useless strategy, either you get too > many points or not enough. there is no way to specify that you want 50 > points but not 5000? That seems like a significant limitation. I wish I > could do something besides point out this problem :( > > > > > On Monday, August 29, 2011 2:52:55 AM UTC+2, Yuv wrote: >> >> On August 22, 2011 11:55:17 AM Jeffrey Martin wrote: >> > Is there a way to limit the number of CP's as a-s-c does ? >> >> First, you can limit the max number of points per bucket with --sieve1size >> >> CPfind partitions the images into a grid of buckets with --sieve1width and >> >> --sieve1height. Both have a default value of 10, which means that each >> image is sliced into 10 rows and 10 columns, yielding 100 buckets. >> >> --sieve1size is the maximum number of points to be added for each bucket. >> >> Of course no points will be added to a bucket if it is not in an overlap >> area. >> >> So there is no way to limit the number of CP's in absolute terms as APSC >> does, but modulating the three parameters should help. >> >> If after reducing --sieve1size there are still too many points, try >> decreasing --sieve1width and --sieve1height >> >> >> High values of --sieve1width and --sieve1height are recommended for small >> overlaps (because more buckets fall into the overlap area). >> >> HTH >> Yuv >> >> -- > You received this message because you are subscribed to the Google Groups > "Hugin and other free panoramic software" group. > A list of frequently asked questions is available at: > http://wiki.panotools.org/Hugin_FAQ > To post to this group, send email to hugin-ptx@googlegroups.com > To unsubscribe from this group, send email to > hugin-ptx+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/hugin-ptx > -- /O -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
