In CPLEX 12.5 to get the default, min, max values for upper and lower limits on the objective value I use
int CPXXinfodblparam(CPXCENVptr env, int whichparam, double * defvalue_p, double * minvalue_p, double * maxvalue_p)
For whichparam = 1026 (CPX_PARAM_OBJULIM) and whichparam = 1025 (CPX_PARAM_OBJULIM), the output defaults are +1e+75 and -1e75 (which are correct), whereas the min and max values are 0.0.
Please correct this trivial bug.
This topic has been locked.
6 replies Latest Post - 2013-01-22T12:15:13Z by SystemAdmin
Pinned topic CPLEX 12.5 with CPX_PARAM_OBJULIM / CPX_PARAM_OBJLLIM
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-01-22T12:15:13Z at 2013-01-22T12:15:13Z by SystemAdmin
Re: CPLEX 12.5 with CPX_PARAM_OBJULIM / CPX_PARAM_OBJLLIM2013-01-21T20:15:26Z in response to SystemAdminNice, it seems to be even worse than a "trivial bug". First, how do you check two doubles for zero. Second, what do you mean with "the parameter has no limit". Please remember that it should work for all platforms.
Re: CPLEX 12.5 with CPX_PARAM_OBJULIM / CPX_PARAM_OBJLLIM2013-01-22T06:27:29Z in response to SystemAdminI'm afraid I don't see your problem here :-(
> Fish2013 wrote:
> Nice, it seems to be even worse than a "trivial bug". First, how do you check two doubles for zero.
You can simply use the '==' operator to do that. Since these are constants there is no round-off impossible and using '==' on floating point numbers is fine here.
> Second, what do you mean with "the parameter has no limit".
It means that you can specify any double precision floating point value here, including positive and negative infinity -- though using a NaN here might result in unexpected behavior.
> Please remember that it should work for all platforms.
I don't see how any of the above would depend on the platform (for the platforms that CPLEX supports).