As PyMC continues to mature and expand its functionality to accommodate more domains of application, we increasingly see cutting-edge methodologies, highly specialized statistical distributions, and complex models appear.
While this adds to the functionality and relevance of the project, it can also introduce instability and impose a burden on testing and quality control.
To reduce the burden on the main pymc repository, this pymc-experimental repository can become the aggregator and testing ground for new additions to PyMC.
This may include unusual probability distributions, advanced model fitting algorithms, innovative yet not fully tested methods or any code that may be inappropriate to include in the pymc repository, but may want to be made available to users.
The pymc-experimental repository can be understood as the first step in the PyMC development pipeline, where all novel code is introduced until it is obvious that it belongs in the main repository.
We hope that this organization improves the stability and streamlines the testing overhead of the pymc repository, while allowing users and developers to test and evaluate cutting-edge methods and not yet fully mature features.
pymc-experimental would be designed to mirror the namespaces in pymc to make usage and migration as easy as possible.
For example, a ParabolicFractal distribution could be used analogously to those in pymc:
import pymc as pm
import pymc_experimental as pmx
with pm.Model():
alpha = pmx.ParabolicFractal('alpha', b=1, c=1)
...- newly-implemented statistical methods, for example step methods or model construction helpers
- distributions that are tricky to sample from or test
- infrequently-used fitting methods or distributions
- any code that requires additional optimization before it can be used in practice
- Case studies
- Implementations that cannot be applied generically, for example because they are tied to variables from a toy example
Since there is a lot of code that we may not want in the main repository, does it make sense to have more than one additional repository?
For example, pymc-experimental may just include methods that are not fully developed, tested and trusted, while code that is known to work well and has adequate test coverage, but is still too specialized to become part of pymc could reside in a pymc-extras (or similar) repository.
This project is still young and many things have not been answered or implemented. Please get involved!
- What are guidlines for organizing submodules?
- Proposal: No default imports of WIP/unstable submodules. By importing manually we can avoid breaking the package if a submodule breaks, for example because of an updated dependency.
- How can we minimize the additional burden of additional project repositories?
- ToDo: Setting up a basic CI pipeline