-
Notifications
You must be signed in to change notification settings - Fork 47
Open
Description
Dear Team,
At the moment AdvancedHMC AbstractMCMC interface pirates AbstractMCMC.Sample function a la Turing.
Currently we are working on allowing Turing to take in AbstractMCMC.AbstractSampler as a sampler. At the moment efforts are focused on these two PR's:
- Turing: allows Turing to take external samplers.
- AdvancedHMC: provides AdvancedHMC with convinience constructors for
AbstractMCMC.AbstractSamplersamplers.
Once these two PR's go through users will be able to do what the current type piracy of AbstractMCMC.Sample does through Turing.
My question is, should we then remove AbstractMCMC.Sample from AdvancedHMC?
Pro's:
- It separates the roles of AdvancedHMC and Turing.
- Avoids type pyracy.
Con's
- Forces users to use Turing for something that previously could be done just within AdvancedHMC.
- Removes a functionality that users might be currently using, potentially breaking their code.
All the best,
Jaime
Metadata
Metadata
Assignees
Labels
No labels