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
Taking as an example the RecurrenceSeededContiniation, the whole compitation process can take hours if one requires very high solver accuracy, FSM accuracy, or just a lot of initial conditions. Not only that, but it can take an hour to just go from one parameter to another. The progressbar in this case is effectively completely stuck giving no information on the progress.
I think we need to rework the progress bar to not be updated only when the parameter is updated. There are two ways I can think:
Allow for a subprogress bar to be displayed by the internal basins_fractions calls. This would be much more informative for the user, but would also require a bit of findlking with ProgressMeter.jl to see how it is possible. I think ProgressMEter.jl has an offset keyword for something like that.
Re-work the progress code, so that a progress bar is given to the basins_fractions!. The internal function just calls next! on the progressbar and the overarching progressbar has n*spp total stepping values.
The text was updated successfully, but these errors were encountered:
Taking as an example the
RecurrenceSeededContiniation
, the whole compitation process can take hours if one requires very high solver accuracy, FSM accuracy, or just a lot of initial conditions. Not only that, but it can take an hour to just go from one parameter to another. The progressbar in this case is effectively completely stuck giving no information on the progress.I think we need to rework the progress bar to not be updated only when the parameter is updated. There are two ways I can think:
basins_fractions
calls. This would be much more informative for the user, but would also require a bit of findlking with ProgressMeter.jl to see how it is possible. I think ProgressMEter.jl has anoffset
keyword for something like that.basins_fractions!
. The internal function just callsnext!
on the progressbar and the overarching progressbar hasn*spp
total stepping values.The text was updated successfully, but these errors were encountered: