You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Raghu Rangarajan (JIRA)" <ji...@apache.org> on 2012/07/13 12:44:34 UTC
[jira] [Comment Edited] (MATH-819) SimplexSolver -
InfeasibleSolution when feasible
[ https://issues.apache.org/jira/browse/MATH-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413643#comment-13413643 ]
Raghu Rangarajan edited comment on MATH-819 at 7/13/12 10:42 AM:
-----------------------------------------------------------------
Hi Thomas,
I will check out Octave. But glpk is able to solve this problem with those large coeffs. I used the standalone solver (glpsol) that comes with glpk. I have attached the input, output and solution files (test.*) for the same problem. Please look into it.
Also please tell me if there is a way to specify "no bounds" for lower and upper bounds for a variable and if that would help the solver. We specify +/-1e10 for those in LinearConstraints since we don't know better.
Again, thanks for looking into this issue.
--
Raghu
was (Author: vidyaraghu):
Hi Thomas,
I will check out Octave. But glpk is able to solve this problem with those large coeffs. I used the standalone solver (glpsol) that comes with glpk. I have attached the input, output and solution files (test.*) for the same problem. Please look into it.
Again, thanks for looking into this issue.
--
Raghu
> SimplexSolver - InfeasibleSolution when feasible
> ------------------------------------------------
>
> Key: MATH-819
> URL: https://issues.apache.org/jira/browse/MATH-819
> Project: Commons Math
> Issue Type: Bug
> Affects Versions: 3.1
> Environment: Windows 7, JDK 1.7.0_03
> Reporter: Raghu Rangarajan
> Attachments: CommonsSolver2.java, lp-octave.txt, test.log, test.mod, test.out
>
>
> I am seeing an odd behavior with the latest code in the main trunk (Directory revision: 1358535). The solver throws "NoFeasibleSolutionException" for a problem which has a feasible solution. Just by commenting out the last constraint, we get a feasible solution. And for that solution, the constraint in question does not seem to be playing a role.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira