-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add notebooks to fill the basic CLV grid #25
Comments
I'll work on adding a notebook for the sBG model for discrete/contractual settings. |
I should be able to write something about the continuous contractual setting! I'm feeling inspired 😅 |
I'm making progress on ^... but I'm knocking my head on a sampling error. Hopefully, I create a PR soon! |
Is the goal to add more than one model to each quadrant? The CNC quadrant now has @larryshamalama 's BG/NBD distribution (#16), but there are several other models available in that quadrant. I wasn't sure if the idea was to get one per quadrant max or if the goal was broader than that. Also, the distribution added in #16 is named |
Sorry for not replying to your question initially. Effectively, there are other continuous non-contractual distributions, as I realized later on (e.g. ParetoNBD). We briefly touched upon this point in #128 |
We have a distribution block for Continuous Contractual, but no modeling options per #279. I've gotten questions on LinkedIn about modeling purchases made through active memberships and/or phone app sessions, so there's demand for it. |
Related: #64 |
The idea is to write a notebook with pure PyMC model(s) for each of these CLV scenarios. We can start with the Lifetime part (not-value yet), but ideally we will include value as well by the end. This might be a constant with time-decay penalty in the simplest cases.
Hopefully this will give us a good picture of the building blocks that are necessary for a minimum viable package, and can also serve as the base documentation. Overtime we would replace the custom PyMC code with imports from the CLV sub-package.
The text was updated successfully, but these errors were encountered: