[Coin-osi-devel] More params, glpk 4.9, mip gap

[Lou Hafer]

Kendall,

	At one level, there is no general solution, because you're talking about
features specfic to a particular underlying solver.  That said, you might have a
look at the setApplicationData method.  It allows you to pass in a pointer to an
arbitrary data structure, which you could pass along to glpk.

	This doesn't necessarily help for something like your need to call one
of lpx_integer or lpx_intopt from OsiGlpk. A solution adopted by other solvers 
is to provide an extension function, specific to the solver, which handles
solver-specific parameters (OsiClp::setSpecialOptions, 
OsiDylp::dylp_controlfile). The approach is, by definition, solver-specific.

	It's really an open question as to what the appropriate set of
parameters should be.  Solver capabilities vary widely.  Retaining the
`plug-and-play' aspect of the OSI interface binds a bit on issues such as this.

							Lou