TuringLang / TuringLang/AbstractMCMC.jl
Convergence Logging
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 108
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Right now logging in the convergence sampling mode is almost useless. The @logprogress requires passing a fraction from 0 to 1, which isn't conducive to convergence logging at all. I realize this is backed up into the design of ProgressLogging.jl, which is even further backed up into the current logging backends, some parts end up tied directly into base julia. I've tried circumventing the issue by printing out my own statements but they actually get gobbled up due to the @withprogresslogging context.
I'm not sure the best path forward, other than re-introducing the ProgressMeter.jl dependency only for those sampling routines.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the convergence sampling routines and the ProgressLogging.jl design around @logprogress and @withprogresslogging. Compare their behavior with the current logging backends and the suggested ProgressMeter.jl dependency. Done means convergence sampling reports useful progress without messages being swallowed, with the chosen design agreed for the affected logging paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100