Robert Krawitz wrote:
On Sun, 23 Oct 2011 10:25:02 -0700 (PDT), kfj wrote:
On 23 Okt., 17:17, Robert Krawitz <[email protected]> wrote:
On Sun, 23 Oct 2011 00:59:27 -0700 (PDT), kfj wrote:
On 22 Okt., 16:49, Robert Krawitz <[email protected]> wrote:
2) I'd like a more convenient way to delete all control points in a
region in an image, with a choice of just deleting all points in
that region between a pair of images or all control points.
...
The use case I have for this is that I frequently take hand-held
landscape panoramas where the foreground is not in alignment
I do the same. What I find is that I get good results by simply
removing all CPs outside a strip along the horizon. I do this using
my 'crop CPs' plugin. It's a bit of a crutch since you can't select
a random area - instead it misuses hugin's output cropping feature
by removing the CPs inside or outside the cropping area. So you're
restricted to rectangular areas - but usually I find throwing away
all CPs outside a strip near the horizon does the trick.
That sounds like a useful starting point (although I often have to
remove points from the sky also, when celeste doesn't do what it
should, and in mountainous regions a rectangle isn't sufficient). Is
this part of the hugin repo, or is it a separate download?
It's in the repo. I've written a bunch of plugins to be distributed
with hugin so as to demonstrate what can be done and provide templates
which can be modified by other plugin authors. If you get the main
branch from the repo, you should have all these plugins. If the
wxPython call gives any troubles, it's easy enough to just duplicate
the plugin, take out the wx code and make one which removes CPs inside
the ROI and one which removes them outside. I wrote the version using
wxPython to help fathom on which platforms this technique will be
usable - it's really cool to let a plugin display GUI elements like
dialog boxes, but if I remember rightly it didn't work everywhere.
Since the plugins themselves are pure python code, it should be easy
enough to make them do what you want.
Well, it works on openSUSE just fine.
For my test panorama, I had to do it a few times, because part of the
foreground protruded much closer to the horizon than in the rest of
the scene (this was a 360 degree pano from an overlook just west of
Mono Lake; to the east, there was very little foreground, but to the
west, looking toward Tioga Pass, there was much more). But I didn't
have a lot of difficulty getting the max error down to 1.15 units (I
saw no point to trying any harder), especially with a 22 mm equivalent
lens (I optimized for everything except translation).
Most of the remaining bad points were either in the sky just above the
mountains, or on the lake just above the shoreline. I guess celeste
doesn't try to kill points that are close to edges, unfortunately.
These aren't very good points anyway, and I had so many there was no
sense trying to tune them by hand.
The other problem is that in the very early stages, when this would be
most useful, sometimes it's not possible to get something well enough
aligned to do this.
I use a sort of brute-force approach. I detect lots of CPs using
cpfind with this parameter set in an 'all images at once' setup:
--fullscale --sieve2size 5 -o %o %s
this gives me around a hundred CPs per matching pair, and cpfind
delivers very nicely with few outliers. With this many CPs I usually
get the pano to align roughly quite well on the first try. Then I take
it from there - I remove the 'worst' CPs and use my 'crop CPs' plugin,
sometimes iterating these steps. Often after just one iteration I have
a pano that's near perfect along the horizon.
Eek. I'm going to need more memory to use --fullscale. It got up to
14 GB, and that was only while working on the first 8 out of 16
images. I'm going to need to add at least another 8 GB (or an SSD) to
make this practical, but I suspect it would help quite a lot.
The one time I tried to use the --fullscale option (on my archaic
hardware w/ 2GB memory max), I had to switch to Fluxbox to free enough
memory to work on just one image. And the system was still swapping to
disk ...
--
Gnome Nomad
[email protected]
wandering the landscape of god
http://www.cafepress.com/otherend/
--
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
