Re: gnumeric's solver and parallel computing

Ouch.  600 is well outside the design range.

You might have to play with neutering parts of the non-linear
solver.  For example, basically turning off the newton steps
because computing the Hessian means something like
2*600*600 recalculations of your target cell.

Also, the polishing steps are probably a waste of time for you.

See also -- that is written
about a different solver but the basic points apply here too.

If the problem is convex, you can have very high confidence
that the solutions obtained are globally optimal.  If the problem
is non-convex, you can have reasonable confidence that the
solutions obtained are locally optimal, but not necessarily
globally optimal.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]