I mostly run command line, but every now and then, I get a very slow optimization run. The one I just stopped (good timing) was at loop 29 when I left this morning and was at 30 when back home. So did a loop in about 9 hours.
About one CPU running steadily. Will rerun with less control points (current one has about 22000 for 72 images in stacks of 9. nick On Mon, Jun 21, 2010 at 4:42 PM, Bruno Postle <[email protected]> wrote: > On Mon 21-Jun-2010 at 10:37 +0200, Markus Kuehni TRILAB wrote: > >> >> It detected control points fine (55'035) and now "hangs" for 30 straight >> CPU-hours at "Determining placement of the images". No disk IO taking >> place. >> (i7 620M at boosting 3.33 GHz). >> > > I can't be sure what the problem is, but optimisation shouldn't take this > long. > > I hope you saved the project before optimisation, can you upload the .pto > file somewhere so we can have a look? > > -- > Bruno > > > -- > 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]<hugin-ptx%[email protected]> > For more options, visit this group at > http://groups.google.com/group/hugin-ptx > -- 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
