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

Explore interoperability with other step samplers #32

Open
ricardoV94 opened this issue Jan 6, 2023 · 2 comments
Open

Explore interoperability with other step samplers #32

ricardoV94 opened this issue Jan 6, 2023 · 2 comments

Comments

@ricardoV94
Copy link
Member

Would be neat if we could use nutpie as a step sampler with the other PyMC samplers (without killing performance too much)

Might justify refactoring the trace backend CC @michaelosthege

@aseyboldt any hints how one could start investigating this?

@aseyboldt
Copy link
Member

I think we could do this by using a somewhat lower-level interface in nuts-rs. Right now we just call sample_parallel, which takes care of multithreading of the different chains and gives us draws from any chain when they become available.
But we can also directly instantiate the individual chains, and call those in a pymc step-method.

@ricardoV94 ricardoV94 changed the title Explore iterop with other step samplers Explore interoperability with other step samplers Jan 6, 2023
@michaelosthege
Copy link
Member

I don't know about rust/Python interop, but I assume that refactoring the trace backend is the right first step regardless.
I'll try to make another step in that direction as my next PR.

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

3 participants