You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
14
14
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.
15
-
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.
15
+
To reduce the burden on the main `pymc` repository, this `pymc-extras` repository can become the aggregator and testing ground for new additions to PyMC.
16
16
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.
17
17
18
-
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.
18
+
The `pymc-extras` 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.
19
19
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.
20
20
21
-
`pymc-experimental` would be designed to mirror the namespaces in `pymc` to make usage and migration as easy as possible.
21
+
`pymc-extras` would be designed to mirror the namespaces in `pymc` to make usage and migration as easy as possible.
22
22
For example, a `ParabolicFractal` distribution could be used analogously to those in `pymc`:
23
23
24
24
```python
25
25
import pymc as pm
26
-
importpymc_experimentalas pmx
26
+
importpymc_extrasas pmx
27
27
28
28
with pm.Model():
29
29
@@ -35,23 +35,23 @@ with pm.Model():
35
35
36
36
## Questions
37
37
38
-
### What belongs in `pymc-experimental`?
38
+
### What belongs in `pymc-extras`?
39
39
40
40
- newly-implemented statistical methods, for example step methods or model construction helpers
41
41
- distributions that are tricky to sample from or test
42
42
- infrequently-used fitting methods or distributions
43
43
- any code that requires additional optimization before it can be used in practice
44
44
45
45
46
-
### What does not belong in `pymc-experimental`?
46
+
### What does not belong in `pymc-extras`?
47
47
- Case studies
48
48
- Implementations that cannot be applied generically, for example because they are tied to variables from a toy example
49
49
50
50
51
51
### Should there be more than one add-on repository?
52
52
53
53
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?
54
-
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.
54
+
For example, `pymc-extras` 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.
We welcome contributions from interested individuals or groups! For information about contributing to PyMC experimental check out our instructions, policies, and guidelines `here <https://github.com/pymc-devs/pymc-experimental/blob/main/CONTRIBUTING.md>`_.
38
+
We welcome contributions from interested individuals or groups! For information about contributing to PyMC Extras check out our instructions, policies, and guidelines `here <https://github.com/pymc-devs/pymc-extras/blob/main/CONTRIBUTING.md>`_.
39
39
40
40
Contributors
41
41
============
42
-
See the `GitHub contributor page <https://github.com/pymc-devs/pymc-experimental/graphs/contributors>`_.
42
+
See the `GitHub contributor page <https://github.com/pymc-devs/pymc-extras/graphs/contributors>`_.
0 commit comments