You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Different solvers can handle different kinds of problems: constrained or unconstrained, support for equality constraints etc. I guess we could find a way to help filter relevant problems for a given solver, rather than trying to launch the whole Schittkowski test suite or expect the developer to go through each problem to find the ones that could work.
We could also imagine something related: exporting the result of tests sorted by types to the RobOptim website. This may help users choose an adequate solver when considering a specific problem. We could add some JQuery magic with tick boxes (e.g. bounded arguments, nonlinear constraints, global solution) and display the results in an array for the problems that correspond to this query.
Did you have the Schittkowski original PDF, actually they do have tests types. For instance, PQR-T1-1 but I didn't have enough time yet to see what it means in detail. This may be a good way to put tests in different categories.
For the web/JQuery part, I am considering using the Google Charts API and making a bench generating JSON so that I can load it on the website directly. I just hope I will have enough time to do that ;)
Different solvers can handle different kinds of problems: constrained or unconstrained, support for equality constraints etc. I guess we could find a way to help filter relevant problems for a given solver, rather than trying to launch the whole Schittkowski test suite or expect the developer to go through each problem to find the ones that could work.
I guess that information could be processed by tests.cmake or Schittkowski's CMakeLists.txt to only use relevant problems.
The text was updated successfully, but these errors were encountered: