On 06/27/2014 10:46 PM, Guy wrote:
Ha! You should try this when you have 30698 control points. So far mine
has taken about 78 hours with nothing else going on, and a devoted
Samsung Notebook with Windows 8.1. Out of interest, I tried the exact
same set of photos using Microsoft ICE, it took 15 minutes, and I had a
load of background stuff going on at the same time. The results look
really good, I was doing an extremely high focus 360 by 180 degree
panorama and needed about 250 photos. I am yet to see the results from
Hugin, but my best guess is that for pretty good quality result that can
be achieved much faster, use a different software (Microsoft ICE is also
free).
Microsoft ICE is not free. It requires purchasing Microsoft Windows. ;)
Similar to your results, by the time I reached the 255 iteration for
strategy 2, the difference was from 6.17328487072292 units
to 6.17328283689973 units.
Since I really don't understand what those "units" really are, all I can
say is that refining them to such a small decimal value seems a little
silly ...
On Tuesday, March 11, 2014 6:21:49 PM UTC, Tim wrote:
Hello!
I've used Hugin in the past with pretty good success to create
360x180 panoramas but recently I've been having performance problems.
I'll start with system info:
- Windows 7 Home Premium 64-bit SP1
- CPU Intel i7 2600K
- 8GB RAM
- Video Card 1GB ATI AMD Radeon HD 6700 (not sure if this is relevant)
- Hugin version 2013.0.0.0d404a7088e6
In one situation I'm shooting a fairly large interior space, +/- 2
bracketed, using a Panosaurus 2.0 tripod head. I've loaded my 55
images into Hugin (yes 55, I've already masked off the tripod in the
nadir shot in Photoshop and don't feel like I need the other two
exposures), masked of some areas, and used autopano-sift-c on
different selections of photos to create control points. I then
aligned and it worked fine but wasn't perfect so I manually modified
control points, optimized position/view/barrel, and went to align
but it is taking quite a while. It is definitely running because
autooptimiser.exe is consuming a full CPU so it hasn't frozen. The
Optimizing Variables iterations are chugging right now at the 28th
iteration but each iteration seems to take about twice as long as
the last with the last taking 15-20 minutes. The Average (rms)
distance of iteration 27 was 1.43535468375691 and iteration 28 moved
just to 1.43510034667803 so it isn't really doing much any longer.
I have 1526 total control points with mean error of 2.35 pixels and
max 80.17. Something to note is that before optimizing
position/view/barrel I optimized using the Positions (incremental,
starting from anchor) option and Hugin crashed. I reloaded the pto
and the position/view/barrel option ran fine.
Another series of shots that I was processing over the weekend I let
run for over 30 hours and it still hadn't finished so I killed it
and scrapped that series of photos (at least for now).
Does anyone have thoughts on what could cause this? Could my
configuration be screwy? What causes Optimize Variables to stop?
Is it a set number of iterations? Is there a way to make it stop
after less than 1/100th of a unit changes between iterations or
something?
Thanks,
Tim
--
David W. Jones
[email protected]
wandering the landscape of god
http://dancingtreefrog.com
--
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/hugin-ptx/53AF574D.7060104%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
