NumPyroConverter makes too many assumptions about the model
See original GitHub issueThe following code is not always runnable:
This will fail for a model involving ImproperUniform
, as sampling for it is not defined.
Would it be possible to add a keyword argument that specifies whether this automatic extraction of observations should be attempt or not, e.g. extract_observations
or something? At the moment it’s stopping me from being able to use arviz with my numpyro-model (unless I just comment out the lines above) 😕
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:9 (6 by maintainers)
Top Results From Across the Web
NumPyro documentation - Pyro
The variational inference implementation supports a number of features, including support for models with discrete latent variables (see.
Read more >How to choose initial values for MeanField sigma, and ...
Hi everyone We have implemented the same model in pymc3, pyro and numpyro ... So, one good option can be to use all...
Read more >arXiv:2206.00093v1 [stat.ML] 31 May 2022
We pursue tractable Bayesian analysis of gen- eralized linear models (GLMs) for categorical data. Thus far, GLMs are difficult to scale.
Read more >An astronomer's introduction to NumPyro
Then we use these parameters to evaluate our model, making sure that we always use jax.numpy functions instead of numpy functions.
Read more >Blog – Laplace-ML
When we have multiple models we can also better analyze overall performance ... Generally speaking, we build a neural network from assumptions about...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sure 👍
That sounds reasonable 👍
This is not true in general, e.g. in the model I’m working with we’re using
ImproperUniform
together with a factor in the prior to make the implementation more efficient.Oh, that’s a good point! I forgot that
factor
can be used this way. 😉