Cameron Pfiffer

Results 148 comments of Cameron Pfiffer

You can give it a `Function` which supports literally any type of proposal, and anything that inherits `Distribution` from Distributions.jl.

No change, happy to accept PRs!

The sampler API simplification you noted is indeed still ongoing, so anything you build now will probably be invalidated and require some nontrivial modifications once TuringLang/Turing.jl#793 goes through. That said,...

I am not sure about the name -- I hadn't heard about it until the astro people showed up. I'm preferential to `sample(model, Ensemble(), 100)` or `sample(model, AffineInvariant(), 100)`. As...

> Unless you or @cpfiffer see any advantages in separating out the adaptor logic (I don't really) we can just keep it as it is. For right now, I think...

Cool. I like it. I've turned on the test suite so we can see how the tests run.

I'll approve for now. Could you add a little bit of usage info to the README file?

More generally I think it'd be nice if we had a more fine-tuned ability to talk to gradient evaluations. For example, I had a use case where I wanted to...

> doesn't one need to compile anyway? Not in the sense that Stan does it. Turing is all JIT compiled, so the initial timings would be very poor anyways. >...