venkatkalyan/lpsolver

Automatically exported from code.google.com/p/lpsolver

lpsolver's Issues

Solver can not handle more than 20 variables

What steps will reproduce the problem?
1. Input a 21 variable problem.
2. Solve.

What is the expected output? What do you see instead?
Would expect to see a moderately fast solution.  Instead Java encounters
memory overload errors on ArrayList capacities when calculating the power
set of variables.

Anticipated Solution Method:  Rather than calculate the entire power set,
the optimal method will be to individually calculate each element of the
power set, run a test to see if it is the correct size or represents a
basic feasible solution.  Eliminating the power set ArrayList will resolve
most of the current performance issues.

Original issue reported on code.google.com by [email protected] on 19 Apr 2009 at 4:46

Selecting a cell in one table does not deselect currently selected cell in the other table.

What steps will reproduce the problem?
1. Select a cell in Objective Function Table.
2. Select a cell in the Constraint Table.

What is the expected output? What do you see instead?
The cell in the Objective Function Table should deselect when a cell in the 
Constraint Table is 
selected.  Currently cross-table selections do not cross-deselect.

Please use labels and text to provide additional information.
JTable Cell Editors/Frame Class

Original issue reported on code.google.com by [email protected] on 7 Apr 2009 at 3:34

Bad Solution for Simple LPP

What steps will reproduce the problem?
1. Obj Func: 3,4,5,2,7,8 Minimize
2. Constraints:
1,1,1,0,0,0,=,5
0,0,0,0,1,1,=,5
1,0,0,-1,0,0,=,0
0,1,0,1,-1,0,=,0
0,0,1,0,0,-1,=,0
3. Solve

What is the expected output? What do you see instead?
Expect Solution: 0,5,0,0,5,0 for OFV = 55.  Instead get 0,0,0,0,5,0 for OFV = 
55.
LaTeX Output has variant solution; suspect failure in pivot variable choosing 
method.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by [email protected] on 24 Apr 2009 at 2:22

Revising input in a table cell should initialize with the previous input all selected

What steps will reproduce the problem?
1. Enter a value in a double-based table cell.
2. Deselect the cell.
3. Reselect the cell with a single click to highlight, and enter new values.

What is the expected output? What do you see instead?
The newly entered values should replace the pre-existent values.
Currently, the newly entered values append on the pre-existent values.

Please use labels and text to provide additional information.
JTable Cell Editors/Frame Class

Original issue reported on code.google.com by [email protected] on 7 Apr 2009 at 3:32

Aux text file to output simplex tableaus

Planned implementation: Should have user-selected option to generate a 
auxiliary text file 
displaying simplex tableaus whenever an lp is solved.

Original issue reported on code.google.com by [email protected] on 7 Apr 2009 at 3:36

Constraint Labels and Ability to Name Variables

Want to include an optional column in the table to label constraints and
ability to rename decision variables in the column headers.

Original issue reported on code.google.com by [email protected] on 16 Apr 2009 at 7:57

Constraint Information Output - Binding/Non-Binding, Slack Surplus, Shadow Price

Plan to implement an Option Menu Item that will display additional information 
about each 
constraint.

To include:
Binding/Not-binding
If not-binding, Slack/Surplus
Shadow Price
Range of Feasibility

Original issue reported on code.google.com by [email protected] on 7 Apr 2009 at 3:23

Decision Variable Restrictions - Unrestricted, Binary

Planned Implementation: Create interface and solver structure to handle 
different types of decision 
variables (unrestricted, binary).

Original issue reported on code.google.com by [email protected] on 7 Apr 2009 at 3:27

Add Delete Variable/Constraint Submenus

Want to implement submenus to choose which variable/constraint to delete
rather than JOptionPanes.

Original issue reported on code.google.com by [email protected] on 14 Apr 2009 at 2:22

"Bad LPP Input" Error Messages

What steps will reproduce the problem?
1. Input an infeasible LPP, solve.
2. Input an unbounded LPP, solve.
3. Input a pivot out-timing LPP, solve.

What is the expected output? What do you see instead?
Expect separate error messages.  Currently produces the same error message.

Original issue reported on code.google.com by [email protected] on 7 Apr 2009 at 3:10