There is an undo button. I use it often when an optimization failed. It's hard to know if it failed without looking at the preview, and you have to accept the optimization to do this.
On Jan 4, 12:29 am, Wolfgang Hugemann <[email protected]> wrote: > > I have located the pto file for the project and have uploaded it, you > > should find it here <http://hugin-ptx.googlegroups.com/web/lens-cal- > > tute.pto?gsc=__lf2AsAAACSWoUVkYFVtD9bujJphFH7>. > > In case this link gets mangled, look for lens-cal-tute.pto. > > > Hope this helps. > > Indeed, it did. By comparing my file with your version, I could figure > out the problem: It's the start vector of the optimisation, i.e. (a_0, > b_0, c_0)! > > It seems that the result of the last optimisation, however wrong it may > have turned out, is stored in the PTO file as the start vector for the > next optimisation. So if you went completely wrong in the first run (and > did accept that result), you start the optimisation from an off-point, > such that it will not converge. > > The solution was to activate the check box "Edit script before > optimising" and reset the start vector to (0, 0, 0) again. The > optimisation then converged to the correct values. > > This hint should be given in the tutorial, because my error is pretty > typical for novices: You go completely wrong in your the first attempt > -- and then you are stuck ... > > Thanks for your help! > Wolfgang Hugemann -- 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
