Issue 123136 - Solver ignores setting "Assume variables as integer"
Summary: Solver ignores setting "Assume variables as integer"
Status: CONFIRMED
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: 3.4.0
Hardware: PC Windows 7
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2013-08-29 07:21 UTC by Edwin Sharp
Modified: 2013-09-04 10:21 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: 4.0.0
Developer Difficulty: ---

Attachments
Solver example spreadsheet (62.85 KB, application/x-vnd.oasis.opendocument.spreadsheet)
2013-08-29 07:21 UTC, Edwin Sharp 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Edwin Sharp 2013-08-29 07:21:39 UTC 
Created attachment 81408 [details]
Solver example spreadsheet

Tools - Solver... - Options... - check assume variables as integer
check also assume variables as non-negative
Result of cell A1 is 4.6 (not an integer!) when B1 target is -27.
See attachment

Rev. 1516794 Win 7
Comment 1 Rainer Bielefeld 2013-09-04 10:21:20 UTC 
a) Reproducible with  "AOO 4.0.0 – German UI / German locale  [AOO400m3(Build:9702)  -  Rev. 1503704 2013-07-16 14:54:56 (Di, 16 Jul 2013)]" on German German WIN7 Home Premium (64bit)", Common 4.0-dev User Profile.

b) Not a new problem, already reproducible with AOO 3.4.0

c) Still worked fine with OOo 3.1.1, OOo 3.3.0, so REGRESSION

d) Still reproducible with  "AOO 4.1.0-Dev – English  UI / German locale - [AOO410m1(Build:9750)  -  Rev. 1516435  2013-08-24]" on German WIN7 Home
Premium (64bit)", own separate user profile. so FIXED

e) It seems the solver also ignores Limiting conditions? A1 Result "4.6" is not in
   accordance with limitation "A1 >= 25"? But I don't know enough concerning 
   solver. But so, for example, LibO 4.0.3 says "no solution possible" for
   reporter's sample

f) Works fine with LibO 4


@Edwin Sharp:
Can you please do some research concerning 'e' and submit a new bug for that if you also see that a a bug (what has not been reported yet)?