-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Default target_accept not mentioned anywhere in the docs #7455
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
Comments
can you provide more info about this? |
I think it's pretty self explanatory. |
It's a keyword argument to pm.sample |
Is I mean, it's detailed here, but I assumed that the sampling defaults would be specified deeper in the code, possibly allowing for different default for different sampling algorithms. |
There are at least a couple places where a default is provided deep in the code: Line 730 in 747fda3
Line 478 in 747fda3
pymc/pymc/step_methods/hmc/hmc.py Line 119 in 747fda3
pymc/pymc/step_methods/hmc/base_hmc.py Line 72 in 747fda3
|
Exactly. But those are each specified separately and, it turns out, in a way that creates different defaults for different algorithms. So I'm not sure what's missing from the docs. |
I couldn't figure out what the default is as an advanced user. Since it's common advice to increase it (even automatic in case of divergences) it should be easy to find what the default is. |
This is caused by |
pm.sample 🤷♂️🫠🥹? Or do you have a better idea? |
But ... it's not an argument to |
It is, just hidden inside **kwargs. It's actually a special kwarg, the only one we accept both directly and as usual step kwargs |
See #5622 |
@ricardoV94 do you suggest mentioning the default values of |
Description
...
The text was updated successfully, but these errors were encountered: