Pyro Discussion Forum
Aug 19, 2025 · Forum For Pyro Developers
numpyro - Pyro Discussion Forum
Jun 3, 2019 · Forum For Pyro Developers
Help post，shape problem - Pyro Discussion Forum
Apr 25, 2025 · with pyro.plate("data", x.size(0)): pyro.sample("obs", dist.Normal(mu, sigma), obs=y.squeeze(-1),infer={"scale": annealing_factor}) #obs，真实数据+噪声
Model and guide shapes disagree at site - Pyro Discussion Forum
May 1, 2019 · Model and guide shapes disagree at site ‘z_2’: torch.Size ( [2, 2]) vs torch.Size ( [2]) Anyone has the clue, why the shapes disagree at some point? Here is the z_t sample site in the …
Bayesian ResNet: Invalid log_prob shape - Pyro Discussion Forum
Jan 31, 2022 · Reading Tensor shapes in Pyro — Pyro Tutorials 1.8.4 documentation I get that the log_prob tensor should have a shape of batch_shape. So why is the expected batch_shape instead …
NAN log_prob_sum in Poisson model? - Pyro Discussion Forum
Jun 10, 2018 · Hello Pyro community! I’m a Pyro noob, just getting my feet wet with some simple models, and ran into a warning that I could use some help understanding. I’m attempting to use …
Reducing MCMC memory usage - numpyro - Pyro Discussion Forum
Oct 15, 2023 · I am running NUTS/MCMC (on multiple CPU cores) for a quite large dataset (400k samples) for 4 chains x 2000 steps. mcmc.run actually ran until the end, but then died with an out-of …
AutoGuide For a deep learning MLP Model - Pyro Discussion Forum
Nov 21, 2023 · Hello, I am not sure that I understand well how the AutoDiagonalNormal AutoGuide works. I have a MLP model and I want to do an SVI on this model. Given that my model uses …
Implementation & normalizing flow in matrix normal distribution
Nov 1, 2024 · Hi, I’m working on a model where the likelihood follows a matrix normal distribution, X ~ MN_{n,p} (M, U, V). I’m using conjugate priors: M ~ MN U ~ Inverse Wishart V ~ Inverse Wishart As …
GPU available but slow compared to CPU on BNN example - numpyro
Nov 25, 2021 · Well, It is a VI + NeuraReparametrisation to perform a NUTS. Currently, we have found that the job runs 100% on CPU while GPU memory is activated. it’s as if the CPU was going back …