Skip to content

Guide for writing custom distributions #184

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

Open
ally-lee opened this issue Jun 20, 2021 · 1 comment
Open

Guide for writing custom distributions #184

ally-lee opened this issue Jun 20, 2021 · 1 comment
Labels
tracker id Issues used as trackers in the notebook update project, do not close!

Comments

@ally-lee
Copy link
Contributor

ally-lee commented Jun 20, 2021

I would like to contribute a guide for defining custom PyMC3 distributions. I was working with count data and realized that the Poisson distribution didn't offer the flexibility in dispersion I needed since the mean and variance are fixed to each other. I decided that the Generalized Poisson was a better likelihood for my model, so I wrote a custom distribution for it. I have put together a notebook outlining this, and I'll link my PR to this issue.

I posted about this on discourse a while back, so it would be great to post updates for the community in this thread:
https://discourse.pymc.io/t/generalized-poisson-distribution/6535

Since I have now worked with the Generalized Poisson in PyMC3, I would also like to contribute this distribution to the main project: pymc-devs/pymc#4775

File:
Reviewers:

The sections below may still be pending. If so, the issue is still available, it simply doesn't
have specific guidance yet. Please refer to this overview of updates

Known changes needed

Changes listed in this section should all be done at some point in order to get this
notebook to a "Best Practices" state. However, these are probably not enough!
Make sure to thoroughly review the notebook and search for other updates.

General updates

ArviZ related

Changes for discussion

Changes listed in this section are up for discussion, these are ideas on how to improve
the notebook but may not have a clear implementation, or fix some know issue only partially.

General updates

ArviZ related

Notes

Exotic dependencies

Computing requirements

@ally-lee ally-lee added the tracker id Issues used as trackers in the notebook update project, do not close! label Jun 20, 2021
@drbenvincent
Copy link
Contributor

Just flagging up that this notebook is still needs to be updated from PyMC3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tracker id Issues used as trackers in the notebook update project, do not close!
Projects
None yet
Development

No branches or pull requests

2 participants