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
What's the problem this feature will solve?
In some of my simulations, I have implemented logic to detect when the model has converged and should stop running. I would like some short version of the status and detected convergence value displayed to the user, so that they know explicitly when the model is running or has stopped, and so they have a bit of information about why it stopped.
Describe the solution you'd like
I was thinking that a solara markdown output of a model property wouldn't be too hard to do, and on larger screens there may be space in the same row after the current step count - but I can't figure out an easy way to customize that ModelController. Another option could be an additional row after the controller row.
The text was updated successfully, but these errors were encountered:
There is currently no builtin mechanism to customize components on the left sidebar, but there could be an optional argument to JupyterViz for components that are then rendered in the left sidebar. This should be a few lines of code of implementation.
What's the problem this feature will solve?
In some of my simulations, I have implemented logic to detect when the model has converged and should stop running. I would like some short version of the status and detected convergence value displayed to the user, so that they know explicitly when the model is running or has stopped, and so they have a bit of information about why it stopped.
Describe the solution you'd like
I was thinking that a solara markdown output of a model property wouldn't be too hard to do, and on larger screens there may be space in the same row after the current step count - but I can't figure out an easy way to customize that
ModelController
. Another option could be an additional row after the controller row.The text was updated successfully, but these errors were encountered: