Decouple the schedule_fn
from the step function in high-level SgMCMC algorithm
#347
Labels
enhancement
New feature or request
refactoring
Change that adds no functionality but improves code quality
Knowledge of the current iteration is made necessary by the use of
schedule_fn
at the highest level. It shouldn't therefore be propagated down to the algorithms and add stop extra logic there for step counting.I think we should take one step further and remove support for
schedule_fn
altogether in the high-level interface. It complicated the library a little, and having used SGMCMC for #209 I don't see any use for it.The text was updated successfully, but these errors were encountered: