Pyro PPL on NumPy
Project description
NumPyro
Probabilistic programming with NumPy powered by JAX for autograd and JIT compilation to GPU/TPU/CPU.
What is NumPyro?
NumPyro is a small probabilistic programming library that provides a NumPy backend for Pyro. We rely on JAX for automatic differentiation and JIT compilation to GPU / CPU. This is an alpha release under active development, so beware of brittleness, bugs, and changes to the API as the design evolves.
NumPyro is designed to be lightweight and focuses on providing a flexible substrate that users can build on:
 Pyro Primitives: NumPyro programs can contain regular Python and NumPy code, in addition to Pyro primitives like
sample
andparam
. The model code should look very similar to Pyro except for some minor differences between PyTorch and Numpy's API. See the example below.  Inference algorithms: NumPyro currently supports Hamiltonian Monte Carlo, including an implementation of the No UTurn Sampler. One of the motivations for NumPyro was to speed up Hamiltonian Monte Carlo by JIT compiling the verlet integrator that includes multiple gradient computations. With JAX, we can compose
jit
andgrad
to compile the entire integration step into an XLA optimized kernel. We also eliminate Python overhead by JIT compiling the entire tree building stage in NUTS (this is possible using Iterative NUTS). There is also a basic Variational Inference implementation for reparameterized distributions together with many flexible (auto)guides for Automatic Differentiation Variational Inference (ADVI).  Distributions: The numpyro.distributions module provides distribution classes, constraints and bijective transforms. The distribution classes wrap over samplers implemented to work with JAX's functional pseudorandom number generator. The design of the distributions module largely follows from PyTorch. A major subset of the API is implemented, and it contains most of the common distributions that exist in PyTorch. As a result, Pyro and PyTorch users can rely on the same API and batching semantics as in
torch.distributions
. In addition to distributions,constraints
andtransforms
are very useful when operating on distribution classes with bounded support.  Effect handlers: Like Pyro, primitives like
sample
andparam
can be provided nonstandard interpretations using effecthandlers from the numpyro.handlers module, and these can be easily extended to implement custom inference algorithms and inference utilities.
A Simple Example  8 Schools
Let us explore NumPyro using a simple example. We will use the eight schools example from Gelman et al., Bayesian Data Analysis: Sec. 5.5, 2003, which studies the effect of coaching on SAT performance in eight schools.
The data is given by:
>>> import numpy as np >>> J = 8 >>> y = np.array([28.0, 8.0, 3.0, 7.0, 1.0, 1.0, 18.0, 12.0]) >>> sigma = np.array([15.0, 10.0, 16.0, 11.0, 9.0, 11.0, 10.0, 18.0])
, where y
are the treatment effects and sigma
the standard error. We build a hierarchical model for the study where we assume that the grouplevel parameters theta
for each school are sampled from a Normal distribution with unknown mean mu
and standard deviation tau
, while the observed data are in turn generated from a Normal distribution with mean and standard deviation given by theta
(true effect) and sigma
, respectively. This allows us to estimate the populationlevel parameters mu
and tau
by pooling from all the observations, while still allowing for individual variation amongst the schools using the grouplevel theta
parameters.
>>> import numpyro >>> import numpyro.distributions as dist >>> # Eight Schools example ... def eight_schools(J, sigma, y=None): ... mu = numpyro.sample('mu', dist.Normal(0, 5)) ... tau = numpyro.sample('tau', dist.HalfCauchy(5)) ... with numpyro.plate('J', J): ... theta = numpyro.sample('theta', dist.Normal(mu, tau)) ... numpyro.sample('obs', dist.Normal(theta, sigma), obs=y)
Let us infer the values of the unknown parameters in our model by running MCMC using the NoUTurn Sampler (NUTS). Note the usage of the extra_fields
argument in MCMC.run. By default, we only collect samples from the target (posterior) distribution when we run inference using MCMC
. However, collecting additional fields like potential energy or the acceptance probability of a sample can be easily achieved by using the extra_fields
argument. For a list of possible fields that can be collected, see the HMCState object. In this example, we will additionally collect the potential_energy
for each sample.
>>> from jax import random >>> from numpyro.infer import MCMC, NUTS >>> nuts_kernel = NUTS(eight_schools) >>> mcmc = MCMC(nuts_kernel, num_warmup=500, num_samples=1000) >>> rng_key = random.PRNGKey(0) >>> mcmc.run(rng_key, J, sigma, y=y, extra_fields=('potential_energy',))
We can print the summary of the MCMC run, and examine if we observed any divergences during inference. Additionally, since we collected the potential energy for each of the samples, we can easily compute the expected log joint density.
>>> mcmc.print_summary() # doctest: +SKIP mean std median 5.0% 95.0% n_eff r_hat mu 4.14 3.18 3.87 0.76 9.50 115.42 1.01 tau 4.12 3.58 3.12 0.51 8.56 90.64 1.02 theta[0] 6.40 6.22 5.36 2.54 15.27 176.75 1.00 theta[1] 4.96 5.04 4.49 1.98 14.22 217.12 1.00 theta[2] 3.65 5.41 3.31 3.47 13.77 247.64 1.00 theta[3] 4.47 5.29 4.00 3.22 12.92 213.36 1.01 theta[4] 3.22 4.61 3.28 3.72 10.93 242.14 1.01 theta[5] 3.89 4.99 3.71 3.39 12.54 206.27 1.00 theta[6] 6.55 5.72 5.66 1.43 15.78 124.57 1.00 theta[7] 4.81 5.95 4.19 3.90 13.40 299.66 1.00 Number of divergences: 19 >>> pe = mcmc.get_extra_fields()['potential_energy'] >>> print('Expected log joint density: {:.2f}'.format(np.mean(pe))) # doctest: +SKIP Expected log joint density: 54.55
The values above 1 for the split Gelman Rubin diagnostic (r_hat
) indicates that the chain has not fully converged. The low value for the effective sample size (n_eff
), particularly for tau
, and the number of divergent transitions looks problematic. Fortunately, this is a common pathology that can be rectified by using a noncentered paramaterization for tau
in our model. This is straightforward to do in NumPyro by using a TransformedDistribution instance together with a reparameterization effect handler. Let us rewrite the same model but instead of sampling theta
from a Normal(mu, tau)
, we will instead sample it from a base Normal(0, 1)
distribution that is transformed using an AffineTransform. Note that by doing so, NumPyro runs HMC by generating samples theta_base
for the base Normal(0, 1)
distribution instead. We see that the resulting chain does not suffer from the same pathology — the Gelman Rubin diagnostic is 1 for all the parameters and the effective sample size looks quite good!
>>> from numpyro.infer.reparam import TransformReparam >>> # Eight Schools example  Noncentered Reparametrization ... def eight_schools_noncentered(J, sigma, y=None): ... mu = numpyro.sample('mu', dist.Normal(0, 5)) ... tau = numpyro.sample('tau', dist.HalfCauchy(5)) ... with numpyro.plate('J', J): ... with numpyro.handlers.reparam(config={'theta': TransformReparam()}): ... theta = numpyro.sample( ... 'theta', ... dist.TransformedDistribution(dist.Normal(0., 1.), ... dist.transforms.AffineTransform(mu, tau))) ... numpyro.sample('obs', dist.Normal(theta, sigma), obs=y) >>> nuts_kernel = NUTS(eight_schools_noncentered) >>> mcmc = MCMC(nuts_kernel, num_warmup=500, num_samples=1000) >>> rng_key = random.PRNGKey(0) >>> mcmc.run(rng_key, J, sigma, y=y, extra_fields=('potential_energy',)) >>> mcmc.print_summary(exclude_deterministic=False) # doctest: +SKIP mean std median 5.0% 95.0% n_eff r_hat mu 4.08 3.51 4.14 1.69 9.71 720.43 1.00 tau 3.96 3.31 3.09 0.01 8.34 488.63 1.00 theta[0] 6.48 5.72 6.08 2.53 14.96 801.59 1.00 theta[1] 4.95 5.10 4.91 3.70 12.82 1183.06 1.00 theta[2] 3.65 5.58 3.72 5.71 12.13 581.31 1.00 theta[3] 4.56 5.04 4.32 3.14 12.92 1282.60 1.00 theta[4] 3.41 4.79 3.47 4.16 10.79 801.25 1.00 theta[5] 3.58 4.80 3.78 3.95 11.55 1101.33 1.00 theta[6] 6.31 5.17 5.75 2.93 13.87 1081.11 1.00 theta[7] 4.81 5.38 4.61 3.29 14.05 954.14 1.00 theta_base[0] 0.41 0.95 0.40 1.09 1.95 851.45 1.00 theta_base[1] 0.15 0.95 0.20 1.42 1.66 1568.11 1.00 theta_base[2] 0.08 0.98 0.10 1.68 1.54 1037.16 1.00 theta_base[3] 0.06 0.89 0.05 1.42 1.47 1745.02 1.00 theta_base[4] 0.14 0.94 0.16 1.65 1.45 719.85 1.00 theta_base[5] 0.10 0.96 0.14 1.57 1.51 1128.45 1.00 theta_base[6] 0.38 0.95 0.42 1.32 1.82 1026.50 1.00 theta_base[7] 0.10 0.97 0.10 1.51 1.65 1190.98 1.00 Number of divergences: 0 >>> pe = mcmc.get_extra_fields()['potential_energy'] >>> # Compare with the earlier value >>> print('Expected log joint density: {:.2f}'.format(np.mean(pe))) # doctest: +SKIP Expected log joint density: 46.09
Note that for the class of distributions with loc,scale
paramaters such as Normal
, Cauchy
, StudentT
, we also provide a LocScaleReparam reparameterizer to achieve the same purpose. The corresponding code will be
with numpyro.handlers.reparam(config={'theta': LocScaleReparam(centered=0)}):
theta = numpyro.sample('theta', dist.Normal(mu, tau))
Now, let us assume that we have a new school for which we have not observed any test scores, but we would like to generate predictions. NumPyro provides a Predictive class for such a purpose. Note that in the absence of any observed data, we simply use the populationlevel parameters to generate predictions. The Predictive
utility conditions the unobserved mu
and tau
sites to values drawn from the posterior distribution from our last MCMC run, and runs the model forward to generate predictions.
>>> from numpyro.infer import Predictive >>> # New School ... def new_school(): ... mu = numpyro.sample('mu', dist.Normal(0, 5)) ... tau = numpyro.sample('tau', dist.HalfCauchy(5)) ... return numpyro.sample('obs', dist.Normal(mu, tau)) >>> predictive = Predictive(new_school, mcmc.get_samples()) >>> samples_predictive = predictive(random.PRNGKey(1)) >>> print(np.mean(samples_predictive['obs'])) # doctest: +SKIP 3.9886456
More Examples
For some more examples on specifying models and doing inference in NumPyro:
 Bayesian Regression in NumPyro  Start here to get acquainted with writing a simple model in NumPyro, MCMC inference API, effect handlers and writing custom inference utilities.
 Time Series Forecasting  Illustrates how to convert for loops in the model to JAX's
lax.scan
primitive for fast inference.  Baseball example  Using NUTS for a simple hierarchical model. Compare this with the baseball example in Pyro.
 Hidden Markov Model in NumPyro as compared to Stan.
 Variational Autoencoder  As a simple example that uses Variational Inference with neural networks. Pyro implementation for comparison.
 Gaussian Process  Provides a simple example to use NUTS to sample from the posterior over the hyperparameters of a Gaussian Process.
 Statistical Rethinking with NumPyro  Notebooks containing translation of the code in Richard McElreath's Statistical Rethinking book second version, to NumPyro.
 Other model examples can be found in the examples folder.
Pyro users will note that the API for model specification and inference is largely the same as Pyro, including the distributions API, by design. However, there are some important core differences (reflected in the internals) that users should be aware of. e.g. in NumPyro, there is no global parameter store or random state, to make it possible for us to leverage JAX's JIT compilation. Also, users may need to write their models in a more functional style that works better with JAX. Refer to FAQs for a list of differences.
Installation
Limited Windows Support: Note that NumPyro is untested on Windows, and might require building jaxlib from source. See this JAX issue for more details. Alternatively, you can install Windows Subsystem for Linux and use NumPyro on it as on a Linux system. See also CUDA on Windows Subsystem for Linux if you want to use GPUs on Windows.
To install NumPyro with a CPU version of JAX, you can use pip:
pip install numpyro
To use NumPyro on the GPU, you will need to first install jax
and jaxlib
with CUDA support.
To run NumPyro on Cloud TPUs, you can use pip to install NumPyro as above and setup the TPU backend as detailed here.
Default Platform: In contrast to JAX, which uses GPU as the default platform, we use CPU as the default platform. You can use set_platform utility to switch to other platforms such as GPU or TPU at the beginning of your program.
You can also install NumPyro from source:
git clone https://github.com/pyroppl/numpyro.git
# install jax/jaxlib first for CUDA support
pip install e .[dev] # contains additional dependencies for NumPyro development
Frequently Asked Questions

Unlike in Pyro,
numpyro.sample('x', dist.Normal(0, 1))
does not work. Why?You are most likely using a
numpyro.sample
statement outside an inference context. JAX does not have a global random state, and as such, distribution samplers need an explicit random number generator key (PRNGKey) to generate samples from. NumPyro's inference algorithms use the seed handler to thread in a random number generator key, behind the scenes.Your options are:

Call the distribution directly and provide a
PRNGKey
, e.g.dist.Normal(0, 1).sample(PRNGKey(0))

Provide the
rng_key
argument tonumpyro.sample
. e.g.numpyro.sample('x', dist.Normal(0, 1), rng_key=PRNGKey(0))
. 
Wrap the code in a
seed
handler, used either as a context manager or as a function that wraps over the original callable. e.g.with handlers.seed(rng_seed=0): x = numpyro.sample('x', dist.Beta(1, 1)) # random.PRNGKey(0) is used y = numpyro.sample('y', dist.Bernoulli(x)) # uses different PRNGKey split from the last one
, or as a higher order function:
def fn(): x = numpyro.sample('x', dist.Beta(1, 1)) y = numpyro.sample('y', dist.Bernoulli(x)) return y print(handlers.seed(fn, rng_seed=0)())


Can I use the same Pyro model for doing inference in NumPyro?
As you may have noticed from the examples, NumPyro supports all Pyro primitives like
sample
,param
,plate
andmodule
, and effect handlers. Additionally, we have ensured that the distributions API is based ontorch.distributions
, and the inference classes likeSVI
andMCMC
have the same interface. This along with the similarity in the API for NumPy and PyTorch operations ensures that models containing Pyro primitive statements can be used with either backend with some minor changes. Example of some differences along with the changes needed, are noted below: Any
torch
operation in your model will need to be written in terms of the correspondingjax.numpy
operation. Additionally, not alltorch
operations have anumpy
counterpart (and viceversa), and sometimes there are minor differences in the API. pyro.sample
statements outside an inference context will need to be wrapped in aseed
handler, as mentioned above. There is no global parameter store, and as such using
numpyro.param
outside an inference context will have no effect. To retrieve the optimized parameter values from SVI, use the SVI.get_params method. Note that you can still useparam
statements inside a model and NumPyro will use the substitute effect handler internally to substitute values from the optimizer when running the model in SVI.  PyTorch neural network modules will need to rewritten as stax neural networks. See the VAE example for differences in syntax between the two backends.
 JAX works best with functional code, particularly if we would like to leverage JIT compilation, which NumPyro does internally for many inference subroutines. As such, if your model has sideeffects that are not visible to the JAX tracer, it may need to rewritten in a more functional style.
For most small models, changes required to run inference in NumPyro should be minor. Additionally, we are working on pyroapi which allows you to write the same code and dispatch it to multiple backends, including NumPyro. This will necessarily be more restrictive, but has the advantage of being backend agnostic. See the documentation for an example, and let us know your feedback.
 Any

How can I contribute to the project?
Thanks for your interest in the project! You can take a look at beginner friendly issues that are marked with the good first issue tag on Github. Also, please feel to reach out to us on the forum.
Future / Ongoing Work
In the near term, we plan to work on the following. Please open new issues for feature requests and enhancements:
 Improving robustness of inference on different models, profiling and performance tuning.
 Supporting more functionality as part of the pyroapi generic modeling interface.
 More inference algorithms, particularly those that require second order derivaties or use HMC.
 Integration with Funsor to support inference algorithms with delayed sampling.
 Other areas motivated by Pyro's research goals and application focus, and interest from the community.
Citing NumPyro
The motivating ideas behind NumPyro and a description of Iterative NUTS can be found in this paper that appeared in NeurIPS 2019 Program Transformations for Machine Learning Workshop.
If you use NumPyro, please consider citing:
@article{phan2019composable,
title={Composable Effects for Flexible and Accelerated Probabilistic Programming in NumPyro},
author={Phan, Du and Pradhan, Neeraj and Jankowiak, Martin},
journal={arXiv preprint arXiv:1912.11554},
year={2019}
}
as well as
@article{bingham2018pyro,
author = {Bingham, Eli and Chen, Jonathan P. and Jankowiak, Martin and Obermeyer, Fritz and
Pradhan, Neeraj and Karaletsos, Theofanis and Singh, Rohit and Szerlip, Paul and
Horsfall, Paul and Goodman, Noah D.},
title = {{Pyro: Deep Universal Probabilistic Programming}},
journal = {arXiv preprint arXiv:1810.09538},
year = {2018}
}
Project details
Release history Release notifications  RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Filename, size  File type  Python version  Upload date  Hashes 

Filename, size numpyro0.4.1py3noneany.whl (176.4 kB)  File type Wheel  Python version py3  Upload date  Hashes View 
Filename, size numpyro0.4.1.tar.gz (195.5 kB)  File type Source  Python version None  Upload date  Hashes View 