Opened 15 years ago

Closed 3 years ago

#8 closed enhancement (migrated)

More control over solver behavior requested.

Reported by: dan.gordon Owned by: mjs
Priority: minor Milestone:
Component: OsiXpr Version:
Keywords: Cc:


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

Change History (2)

comment:1 Changed 15 years ago by mjs

Do you have patches already that we might consider?

comment:2 Changed 3 years ago by stefan

  • Resolution set to migrated
  • Status changed from new to closed

This ticket has been migrated to GitHub and will be resolved there:

Note: See TracTickets for help on using tickets.