Closed hemilpanchiwala closed 4 years ago
@matthiaskoenig @draeger As now we know where the error was for this issue and it's resolved in the forked repository. So should I link this issue to the PR so that it closes on the merge of the PR?
Yes, link the issue.
On Thu, Jul 2, 2020 at 11:06 AM Hemil Panchiwala notifications@github.com wrote:
@matthiaskoenig https://github.com/matthiaskoenig @draeger https://github.com/draeger As now we know where the error was for this issue and it's resolved in the forked repository. So should I link this issue to the PR so that it closes on the merge of the PR?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/draeger-lab/SBSCL/issues/51#issuecomment-652886129, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAG33OTY7LGKKFCVPNGHJ2DRZREYHANCNFSM4OLCQXJQ .
-- Matthias König, PhD. Junior Group Leader LiSyM - Systems Medicine of the Liver Humboldt Universität zu Berlin, Institute of Biology, Institute for Theoretical Biology https://livermetabolism.com konigmatt@googlemail.com https://twitter.com/konigmatt https://github.com/matthiaskoenig Tel: +49 30 2093 98435
This issue occurs while testing the SBML models with FBC extension from the SBML Test Suite.
The main problem behind this seems to be due to the GLPK Solver. @matthiaskoenig also pointed out this: