[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Help-glpk] interrogating (and emptying) GLPK glp_prob instances
From: |
Robbie Morrison |
Subject: |
[Help-glpk] interrogating (and emptying) GLPK glp_prob instances |
Date: |
Thu, 05 Jun 2008 20:45:22 +0200 |
User-agent: |
Thunderbird 1.5.0.14ubu (X11/20080306) |
Hello Andrew and fellow API users
I am writing some code to display the state of a GLPK
'glp_prob' instance using machine-generated HTML. The
code is complete and I will post details and some
sample output back to this list after I resolve a
couple of small questions, namely:
Can I find out what kind of solvers ('glp_simplex',
'lpx_interior', 'lpx_intopt', 'glp_intopt') have been
run on a particular problem instance by interrogating
that instance -- or does the client code have to keep
track of the solver calls it makes?
Can I find out if the problem has changed since the
solver last ran. I suspect not (and thereby suggest a
new status variable 'GLP_MOD' meaning "the problem has
subsequently been modified" .. or perhaps even a new
status function 'glp_get_prob_status' if you want to
retain access to the now stale solution status
information).
Finally, what is the best way to empty a problem object
of input data -- I currently remove all the rows and
cols but is there a more elegant method? And does this
mean I can rebuild a similar problem of identical size
and have it warm start?
many thanks in advance, best wishes
---
Robbie Morrison
PhD student -- policy-oriented energy system simulation
Technical University of Berlin (TU-Berlin), Germany
University email (redirected) : address@hidden
Webmail (preferred) : address@hidden
[from IMAP client]
- [Help-glpk] interrogating (and emptying) GLPK glp_prob instances,
Robbie Morrison <=