Skip to content
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

Automatic marginalization in PG #126

Closed
devmotion opened this issue Nov 19, 2019 · 4 comments
Closed

Automatic marginalization in PG #126

devmotion opened this issue Nov 19, 2019 · 4 comments

Comments

@devmotion
Copy link
Member

Some of my colleagues just published a paper in which they use Birch (another PPL) to automatically marginalize out the parameters from the state update in PG (with and without ancestor sampling). Maybe that could be done in Turing as well?

Reference

Anna Wigren, Riccardo Sven Risuleo, Lawrence Murray, Fredrik Lindsten: Parameter elimination in particle Gibbs sampling. https://arxiv.org/abs/1910.14145

@yebai
Copy link
Member

yebai commented Nov 19, 2019

Certainly - I think it is a good idea to improve the vanilla PG sampler with AS, looking-ahead proposal and marginalisation when possible.

Actually, we talked about separating the PG (and other particle samplers) into a standalone package called AdvancedPS.jl (like AdvancedHMC.jl, and AdvancedMH.jl), so that

  1. sampling algorithms are decoupled from Turing's DSL
  2. provide better support for algorithmic research on sampling algorithms.

@yebai
Copy link
Member

yebai commented Nov 19, 2019

Ps. I like Birch a lot, it would be great if we can make Turing and Birch compatible in the future, e.g. sharing some sampling algorithms, MCMC diagnostics, and/or create a common DSL.

@yebai
Copy link
Member

yebai commented Nov 19, 2019

cc @donhausk

@yebai yebai transferred this issue from TuringLang/Turing.jl Jan 28, 2021
@yebai yebai transferred this issue from TuringLang/AdvancedPS.jl Oct 23, 2023
@yebai
Copy link
Member

yebai commented Apr 1, 2024

Closing for similar reasons to #40

@yebai yebai closed this as completed Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants