Changes between Initial Version and Version 2 of Ticket #6051


Ignore:
Timestamp:
2020-07-06T23:21:58Z (5 years ago)
Author:
Francesco Casella
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #6051

    • Property Priority high → blocker

  • Ticket #6051 – Description

    initial v2  
    33When the simulation becomes difficult for some reason (e.g. chattering, highly nonlinear behaviour) the step size of adaptive solvers is drastically reduced, and the progress bar remains stuck forever at a particular percentage value, without providing any useful feedback on what is going on.
    44
    5 It would be nice if we also added two textual outputs to the progress bar: one is the current simulation time (with at least 5 significant digits) and one is the value of the current simulation step length, or possibly the average of the last N step lengthts.
     5It would be nice if we also added two textual outputs to the progress bar: one is the current simulation time (with at least 5 significant digits) and one is the value of the current simulation step length, or possibly the average of the last N step lengths.
    66
    77The typical use case is very lengthy simulations (requiring e.g. 20 minutes of CPU times) which get stuck at some specific point. Being able to pinpoint when this happens with high precision helps to speed up the debugging dramatically.