-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sensible Defaults #184
Labels
Comments
Merged
I'd like to bump this issue. I'm planning to use For my own use I wrote this wrapper function below (more or less directly from the Readme). Is something like this of scope for this package? It would make it much easier for users not using Turing to profit from your work.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While the example in the README is important in that it exposes all of the useful bits of AdvancedHMC, it would be nice if it were possible to define a couple of sensible defaults. e.g.
I think that this kind of thing would be a helpful addition to the package, as it makes it more straightforward for a new user to get up and running with their first sampler / for an expert to prototype stuff before optimising.
In particular, it would make writing examples for
Stheno.jl
s documentation quite a lot less verbose.edit:
I think the above would likely tie a sampler and an adapter together. The sampling API would be something like
and by default it would maybe spend
n_samples_to_draw
steps burning in / adapting, then draw the samples.The text was updated successfully, but these errors were encountered: