More control over solver behavior requested.

[svigerske]

Issue created by migration from Trac.

Original creator: dan.gordon

Original creation time: 2006-08-25 04:18:10

Assignee: @mjsaltzman

Version:

When using OsiXpr, I need to be able to use the Newton barrier solver. It's just that much more efficient with my application.

The present behaviour is to use automatic solver selection for initialSolve() and to use dual simplex for resolve().

There is no means of changing this behaviour in OsiSolverInterface or OsiXprSolverInterface. There is no access to the XPRSprob member _prob. Even if there were, this would not help when calling resolve(). Likewise, there are no parameter(s) in OsiSolverInterface to give this kind of control over the solver behaviour.

At present, I'm forced to produce my own version of OsiXprSolverInterface. It would be neater to avoid this, say, by having a parameter in OsiSolverInterface that allows the selection of a preferred method whenever there is a choice available (say interior point/primal simplex/dual simplex).

Thanks, Dan

[svigerske]

Comment by @mjsaltzman created at 2006-10-29 19:37:33

Do you have patches already that we might consider?

[svigerske]

Support to choose interior point algorithms is something that would need to be added to the Osi base class first.