[Top][All Lists]

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

Re: [Bug-glpk] regarding glpk49

From: Brady Hunsaker
Subject: Re: [Bug-glpk] regarding glpk49
Date: Wed, 17 May 2006 12:24:14 -0400
User-agent: Thunderbird (X11/20060501)

I would suggest an option that a user can specify, which will (over)write the current incumbent solution in a file whenever a new incumbent is found.

This should not be hard to implement. It would not have the same information as at the time of termination (since the LP bound may have been decreased since the incumbent was found), but it would not require much I/O in most cases.

A more aggressive option would be to update a file each time the gap was reduced. This would slow down the code a lot more, and I would not recommend implementing it.

If you like, I could probably write and contribute the necessary code for the incumbent file (or ask a student to do so).


Andrew Makhorin wrote:
By seeing the above said text file I am able to understand that this
might be the best result. I want to stop the solver glpsol.exe
manually right now but at the same time I want to get the best
result what ever it had in its memory like the "--tmlim 999" option.
In simple word is there any option to stop the solver at any
perferred time manualy but I want to get the best result to be
written in the out.txt as usual. Dear team if the solution is
already available kindly guide me how to use it. other wise kindly
inculde my request for your future enhancement.

There is no way to prematurely stop the solver but cancellation.
In order to implement that feature the solver routine containing a
main loop should be able to receive signals asynchronously posted
from other processes. A complete implementation would be very
platform specific, so the only thing which might be implemented is
a user-exit routine called, say, whenever the mip solver finishes
processing a node subproblem.

Bug-glpk mailing list

Brady Hunsaker
Assistant Professor
Industrial Engineering
University of Pittsburgh

reply via email to

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