[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Help-glpk] Re: computational efforts, message level and KKT check

From: Ali Baharev
Subject: [Help-glpk] Re: computational efforts, message level and KKT check
Date: Wed, 1 Dec 2010 12:25:17 +0100

Hi Robbie,

Thanks for your response.

>  int niter = lpx_get_int_parm(d_prob, LPX_K_ITCNT);  // lpx is correct
> Are you sure the call is broken?  But I agree, it would
> be better if the API was updated.

Last time I checked it always returned zero. Maybe I messed up something...

Anyhow, it would be nice to have a glp_get_int_parm function.

> If you need another work around, the terminal output records
> this information in line-oriented form .. which you could parse
> if truly desperate.

Not an option. I need the C API.

Note that I can fix these issues myself but I am looking for an
official solution.


On Mon, Nov 29, 2010 at 2:01 AM, Ali Baharev <address@hidden> wrote:
> Dear Andrew,
> In my application I would like to get the computational efforts
> through the C API. In the previous releases I could use
> lpx_get_int_parm with LPX_K_ITCNT but it does not seem to work
> anymore. Please provide API functions to get the computational efforts
> such as iteration count.
> If I set the message level to GLP_MSG_ERR I still get the output of
> the scaling routines. Please disable this if the message level is
> warning and error messages only. (It is causing me problems.)
> Is there a reason why lpx_check_kkt is not glp_check_kkt? I use this
> function very often and I hope it will not be removed from the API.
> Many thanks,
> Ali

reply via email to

[Prev in Thread] Current Thread [Next in Thread]