Bug: "Interactive Optimization" resets the computed parameters every time
yuki-koyama opened this issue · comments
I have updated build/run environments and then I found an unintended behavior that the app resets the optimized parameters every time an interaction event happens. This should be a bug.
This seems to happen when the user pushes the button before the first nlopt::solve finishes. (note that nlopt::solve is called multiple times unless the user pushes one of the buttons.)