Dashboard loses data when refreshed. about estimagic HOT 4 CLOSED

@roecla Do you have any explanation for this or a hint how I can fix it?

from estimagic.

When I looked at this the last time, I had the impression that the dashboard keeps the first and incoming fitness values and parameter values.

Maybe it has something to do with the following lines, because your callback receives the initial data (params and fitness) as a partialed argument and maybe it is never updated during optimization.

I have never fully explored this idea, but maybe it helps.

from estimagic.

PR #132 improves this situation substantially because the data are permanently stored in the database.
However, at the moment when the browser tab is refreshed, the past iterations are skipped:

Before the refresh:

After the refresh:

I don't understand the bokeh behavior when the tab is refreshed yet. Periodic callbacks seem to continue running but cannot be removed by the handles from before the refresh.

I am going to address this in a future pull request. Until then, users can either content themselves with the iterations after the refresh or open up a new dashboard of the database. In that case replay mode will kick in.

from estimagic.

With the switch to the dashboard monitoring the database, the loss of data is no problem anymore.

As of PR #169 after reloading there is no problem with the line as shown above. Instead the plots are emptied and the user is back at the "start" setup (except for the jump argument).

After reloading starting the convergence tab visualization anew works about 80% of the time with no apparent patterns. If it fails, another refresh sometimes fixes the problem and allows the user to restart the playback of the optimization.

Also, simply restarting the dashboard from the command line would be an easy fix in case the restarting from within the convergence tab does not work.

from estimagic.