Created attachment 119910 [details] An example spreadsheet to use for duplication of the error 0) Download the attached example.ods. 0.5) Install nlpsolver if you haven't already. (http://extensions.openoffice.org/en/project/solver-nonlinear-programming-beta) 1) Summon Solver. 2) Select $B$7 as your target cell. 3) Optimize the result to maximize that cell. 4) Select $B$6 as the cells to change. 5) If we solved now, we'd get the absolute maxima. We want a local maxima instead, so add in two limiting conditions, one for $B$6 <= 2, and one for $B$6 => 3. 6) Solve. 7) You can either wait out the 2000 iterations, or stop shortly after starting. Either way, Solver will have arrived at the answer (Should say 2.90). It should be noted that $B$6 will be (approximately) equal to $B$11, and $B$7 will be (approximately) equal to $B$12. This is the answer we want. 8) After hitting OK, Solver will declare that "No solution was found." and revert the two cells to what they were before Solving. I don't know if this is an edge case on Solver, or the result of weirdness from the NLP Solving plugin, but even if Solver couldn't be convinced that this is the answer I want, it'd be nice to have the "No solution was found." box give me the option to keep the answers, rather than reverting them with no recourse. The answer can still be extracted (as you can see), but it requires typing everything out manually outside of LibreOffice, which is a pain.
Migrating Whiteboard tags to Keywords: (needAdvice)
(In reply to whiys from comment #0) > Created attachment 119910 [details] > An example spreadsheet to use for duplication of the error > > 0) Download the attached example.ods. > 0.5) Install nlpsolver if you haven't already. > (http://extensions.openoffice.org/en/project/solver-nonlinear-programming- > beta) > 1) Summon Solver. > 2) Select $B$7 as your target cell. > 3) Optimize the result to maximize that cell. > 4) Select $B$6 as the cells to change. > 5) If we solved now, we'd get the absolute maxima. We want a local maxima > instead, so add in two limiting conditions, one for $B$6 <= 2, and one for > $B$6 => 3. > 6) Solve. > 7) You can either wait out the 2000 iterations, or stop shortly after > starting. Either way, Solver will have arrived at the answer (Should say > 2.90). It should be noted that $B$6 will be (approximately) equal to $B$11, > and $B$7 will be (approximately) equal to $B$12. This is the answer we want. > 8) After hitting OK, Solver will declare that "No solution was found." and > revert the two cells to what they were before Solving. > > I don't know if this is an edge case on Solver, or the result of weirdness > from the NLP Solving plugin, but even if Solver couldn't be convinced that > this is the answer I want, it'd be nice to have the "No solution was found." > box give me the option to keep the answers, rather than reverting them with > no recourse. The answer can still be extracted (as you can see), but it > requires typing everything out manually outside of LibreOffice, which is a > pain. Did you try version 5.3.2? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested information is provided.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20180502
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20180530