Testing new progress bars #83
Conversation
We replaced it with ProgressLogging 😛 The main advantage of ProgressLogging is that it uses the Julia logging system and works with different frontends (eg TerminalLogger, ConsoleProgressMonitor, Juno, VSCode). However, there are still things missing/unpolished in the ProgressLogging API, as the references in the linked issue show, and some things are not supported by the loggers. |
|
|
||
| ## | ||
|
|
||
| using ProgressLogging: _asprogress, ProgressString, ProgressLevel, uuid4 |
There was a problem hiding this comment.
IMO the use of these internals indicates that these extensions should be discussed and potentially be added in ProgressLogging but not in AbstractMCMC.
There was a problem hiding this comment.
No doubt, I will test these extensions and may open a PR in ProgressLogging later, this is just a quick hack
2 participants
This is a proposed fix for #82 (definitely WIP). I created variants of some ProgressLogging macros that can be used to add children to the current progress bar, see src/logging.jl; these probably belong elsewhere. The main progress bar showing the # of chains completed is still there, but it might make more sense to update it with the avg. % of work done on each process (that will render the ETA more helpful).
I don't have experience with
Distributedso some slight modifications might be needed in that case.EDIT: Any opinions about ProgressMeter.jl?