SMCPy - Sequential Monte Carlo with Python
Description
SMCPy is an open-source package for performing uncertainty quantification using a parallelized sequential Monte Carlo sampler.
Key Features
- Alternative to Markov chain Monte Carlo for Bayesian inference problems
- Unbiased estimation of marginal likelihood for Bayesian model selection
- Parallelization through either numpy vectorization or mpi4py
Quick Start
Installation
To install SMCPy, use pip.
pip install smcpy
Overview
To operate the code, the user supplies a computational model built in Python 3.6+, defines prior distributions for each of the model parameters to be estimated, and provides data to be used for probabilistic model calibration. SMC sampling of the parameter posterior distribution can then be conducted with ease through instantiation of a sampler class and a call to the sample() method.
The two primary sampling algorithms implemented in this package are MPI-enabled versions of those presented in the following articles, respectively:
Nguyen, Thi Le Thu, et al. "Efficient sequential Monte-Carlo samplers for Bayesian inference." IEEE Transactions on Signal Processing 64.5 (2015): 1305-1319. Link to Article | BibTeX Reference
Buchholz, Alexander, Nicolas Chopin, and Pierre E. Jacob. "Adaptive tuning of hamiltonian monte carlo within sequential monte carlo." Bayesian Analysis 1.1 (2021): 1-27. Link to Article | BibTeX Reference
The first is a simple likelihood tempering approach in which the tempering sequence is fixed and user-specified (FixedPhiSampler). The second is an adaptive approach that chooses the tempering steps based on a target effective sample size (AdaptiveSampler).
This software was funded by and developed under the High Performance Computing Incubator (HPCI) at NASA Langley Research Center.
Example Usage
We'll set up a toy example: estimating the slope and intercept of a line given only noisy observations of points along that line.
import numpy as np
import seaborn as sns
import pandas as pd
from scipy.stats import uniform
from smcpy import AdaptiveSampler, VectorMCMC, VectorMCMCKernel
from smcpy.utils.noise_generator import generate_noisy_data
def model(params):
return params[:, [0]] * np.linspace(0.5, 2.5, 100) + params[:, [1]]
if __name__ == "__main__":
std_dev = 0.5
true_params = np.array([[2, 3.5]]) # true but unknown (to be estimated)
noisy_data = generate_noisy_data(model(true_params), std_dev)
priors = [uniform(-6, 12.0), uniform(-6, 12.0)]
vector_mcmc = VectorMCMC(model, noisy_data, priors, std_dev)
mcmc_kernel = VectorMCMCKernel(vector_mcmc, ("slope", "intercept"))
smc = AdaptiveSampler(mcmc_kernel)
step_list, mll_list = smc.sample(num_particles=500, num_mcmc_samples=10)
print(f"marginal log likelihood = {mll_list[-1]}")
print(f"parameter means = {step_list[-1].compute_mean()}")
sns.pairplot(pd.DataFrame(step_list[-1].param_dict))
sns.mpl.pyplot.savefig("pairwise.png")
Output
[ mutation ratio: 1.0: : 100.00%|███████████████████████████████████████| phi: 1.00000/1.0 [00:00<00:00
marginal log likelihood = -76.27987428009173
parameter means = {'slope': np.float64(2.0148875448007013), 'intercept': np.float64(3.523915137965013)}
Plotting is easy with seaborn:
To run this example in parallel using MPI, the MCMC kernel just needs to be built with the
ParallelVectorMCMC class in place of VectorMCMC. More details can be found in the
MPI example.
Tests
Clone the repo and move into the package directory:
git clone https://github.com/nasa/SMCPy.git
cd SMCPy
Install requirements necessary to use SMCPy:
pip install -r requirements.txt
Optionally, if you'd like to use the MPI-enabled parallel sampler, install the associated requirements:
pip install -r requirements_optional.txt
Add SMCPy to your Python path. For example:
export PYTHONPATH="$PYTHONPATH:/path/to/smcpy"
Run the tests to ensure proper installation:
pytest tests
Contributing
- Fork (https://github.com/nasa/SMCPy/fork)
- Create your feature branch (
git checkout -b feature/fooBar) - Commit your changes (
git commit -am 'Add some fooBar') - Push to the branch (
git push origin feature/fooBar) - Create a Pull Request
Development
NASA Langley Research Center
Hampton, Virginia
This software was funded by and developed under the High Performance Computing Incubator (HPCI) at NASA Langley Research Center.
Authors
- Patrick Leser
- Julia Truong
- Michael Wang
License
Notices: Copyright 2018 United States Government as represented by the Administrator of the National Aeronautics and Space Administration. No copyright is claimed in the United States under Title 17, U.S. Code. All Other Rights Reserved.
Disclaimers No Warranty: THE SUBJECT SOFTWARE IS PROVIDED "AS IS" WITHOUT ANY WARRANTY OF ANY KIND, EITHER EXPRESSED, IMPLIED, OR STATUTORY, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY THAT THE SUBJECT SOFTWARE WILL CONFORM TO SPECIFICATIONS, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR FREEDOM FROM INFRINGEMENT, ANY WARRANTY THAT THE SUBJECT SOFTWARE WILL BE ERROR FREE, OR ANY WARRANTY THAT DOCUMENTATION, IF PROVIDED, WILL CONFORM TO THE SUBJECT SOFTWARE. THIS AGREEMENT DOES NOT, IN ANY MANNER, CONSTITUTE AN ENDORSEMENT BY GOVERNMENT AGENCY OR ANY PRIOR RECIPIENT OF ANY RESULTS, RESULTING DESIGNS, HARDWARE, SOFTWARE PRODUCTS OR ANY OTHER APPLICATIONS RESULTING FROM USE OF THE SUBJECT SOFTWARE. FURTHER, GOVERNMENT AGENCY DISCLAIMS ALL WARRANTIES AND LIABILITIES REGARDING THIRD-PARTY SOFTWARE, IF PRESENT IN THE ORIGINAL SOFTWARE, AND DISTRIBUTES IT "AS IS."
Waiver and Indemnity: RECIPIENT AGREES TO WAIVE ANY AND ALL CLAIMS AGAINST THE UNITED STATES GOVERNMENT, ITS CONTRACTORS AND SUBCONTRACTORS, AS WELL AS ANY PRIOR RECIPIENT. IF RECIPIENT'S USE OF THE SUBJECT SOFTWARE RESULTS IN ANY LIABILITIES, DEMANDS, DAMAGES, EXPENSES OR LOSSES ARISING FROM SUCH USE, INCLUDING ANY DAMAGES FROM PRODUCTS BASED ON, OR RESULTING FROM, RECIPIENT'S USE OF THE SUBJECT SOFTWARE, RECIPIENT SHALL INDEMNIFY AND HOLD HARMLESS THE UNITED STATES GOVERNMENT, ITS CONTRACTORS AND SUBCONTRACTORS, AS WELL AS ANY PRIOR RECIPIENT, TO THE EXTENT PERMITTED BY LAW. RECIPIENT'S SOLE REMEDY FOR ANY SUCH MATTER SHALL BE THE IMMEDIATE, UNILATERAL TERMINATION OF THIS AGREEMENT.
Metadata
Release files for smcpy 0.1.17
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| smcpy-0.1.17.tar.gz | 808.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| smcpy-0.1.17-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 854.2 kB
Release files / smcpy-0.1.17.tar.gz
| Download URL | smcpy-0.1.17.tar.gz |
|---|---|
| Size | 808.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1456df2a6730ec8915e433359c2d448635f27054ea4f5d2f058c7f347acbea98
|
|
BLAKE2b-256 checksum How to use checksums |
0f2fc53ee50b7fe6d510e01c3a21ea927520139500e62a47b87d168651f00f2b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 24, 2026.
Transparency logRelease files / smcpy-0.1.17-py3-none-any.whl
| Download URL | smcpy-0.1.17-py3-none-any.whl |
|---|---|
| Size | 46.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4c3042b2bbec0328d7ce9884429185a29ef787564f98746dfd875e5af5ee0f10
|
|
BLAKE2b-256 checksum How to use checksums |
ffd7328ce1ea9d84f21a2de2383fa04b7715bc7e60d518803ad10a71ed0af1ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 24, 2026.
Transparency logSecurity for smcpy 0.1.17
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for smcpy-0.1.17.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 24, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.