Here is the nonlinear programming solver. NLP-Solver

Suggestions Plugins
1

Hi everyone,

I noticed OnlyOffice was missing a nonlinear programming solver, so I built one.

GitHub: GitHub - Karl1b/only-office-nlp-solver: NLP Solver plugin for OnlyOffice Spreadsheet. Optimizes a target cell by adjusting parameter cells within bounds using numerical nonlinear programming (Go/WebAssembly). Keywords: NLP, solver, optimization, OnlyOffice plugin, spreadsheet, nonlinear programming, WebAssembly, Go, parameter fitting, minimization. · GitHub

The repo includes an example spreadsheet with two real-world optimization problems and the Himmelblau function as a test case.

A and the download of course, I can not share the link directly here. Cause I am a new user :wink:

I’m planning to submit this to the plugin marketplace later, but still this year, and your feedback would really help shape the final version. Specifically, I’d love to hear:

  • What optimization problems are you solving? (Always looking for edge cases to test)
  • How does it compare to Excel Solver or LibreOffice Calc on your data?
  • What’s missing, broken, or could be better?

Looking forward to hearing what you think!

Karl karlbreuer.com
demo

SOLVER fails to find optimal solution
Spreadsheet tools (solver, trendline and scenario management)
Solver development
3

The solver now supports side conditions and is basically ready for the store.

Just some polishing left.

Project page here:

demo-solver_550_1077

- Still open for feedback :crossed_fingers: :grinning:

1 Like
4

The solver now has a new mode that can also fit the function itself by brute forcing polynoms.

6

Hello @KarlBreuer
We’ll review your plugin. I’ll contact you once we have something to share.

7

Hi Alexandre,

thanks, but this is not really needed.

What I would appreciate is if you could fix the plugin manager / loader.

There is definetely bug, but the greater issue is that there is no error logging with correct stacktrace so the bugs and or mistakes are hard to spot and fix.

Thanks and KR
Karl

How the behaviour is:

  1. start oo with console
    /usr/bin/desktopeditors --ascdesktop-support-debug-info
  2. open the dev tools, by clicking on some specific fields :wink:
  3. produce the error, for example by loading a plugin.
  4. There is only the message that there was an error, but not what and where it came from.

OUTPUT:
code.js:1233
Error: Problem with plugin installation.
at code.js:1635:16
at index.html?lang=en-US&theme-type=dark:1:22
at index.html?lang=en-US&theme-type=dark:1:167
createError @ code.js:1233
(anonymous) @ code.js:1635
(anonymous) @ index.html?lang=en-US&theme-type=dark:1
(anonymous) @ index.html?lang=en-US&theme-type=dark:1

How the behaviour should be:
4. should be a complete error object with stacktrace and lots of info of what went exactly wrong and where. This will help fix bugs in the future and frankly this should be standard in all places as it makes life ez for us devs :wink: