Originally posted by: SystemAdmin
The routines in the C Callable library would be very powerful, except to implement a pivoting rule you typically need information about the reduced costs, values in the tableau, etc., and as far as I can tell, these are only available
after CPXopt has been called (after the problem has been optimized). In some cases, this is just an annoyance- its unnecessary operations. In other cases it could completely block a desired algorithm (for instance, implement a pivoting rule starting with a specific basis).
Its not really an issue for me anymore; it just seems that the CPLEX environment would be more useful if there was this freedom to access tableau information for any arbitrary basis.
#CPLEXOptimizers#DecisionOptimization