Skip to content

VI api quickstart #137

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
OriolAbril opened this issue Apr 5, 2021 · 4 comments
Open

VI api quickstart #137

OriolAbril opened this issue Apr 5, 2021 · 4 comments
Labels
high impact Notebooks with most visits on docs.pymc.io tracker id Issues used as trackers in the notebook update project, do not close!

Comments

@OriolAbril
Copy link
Member

File: https://github.com/pymc-devs/pymc-examples/blob/main/examples/variational_inference/variational_api_quickstart.ipynb
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

@OriolAbril OriolAbril added tracker id Issues used as trackers in the notebook update project, do not close! high impact Notebooks with most visits on docs.pymc.io labels Apr 5, 2021
@chiral-carbon
Copy link
Collaborator

can I take this up? I'm not able to self-assign due to maybe some change in permissions.

@ferrine
Copy link
Member

ferrine commented Sep 2, 2021

It might not work on pymc master branch, there are technical issues with upgrade

@Sayam753
Copy link
Member

Sayam753 commented Sep 2, 2021

Hi @ferrine . Right now, the idea is to update notebooks to run on v3.11.2 and follow Best Practices Guide, not on main/v4.

@ferrine
Copy link
Member

ferrine commented Oct 14, 2021

I see

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
high impact Notebooks with most visits on docs.pymc.io tracker id Issues used as trackers in the notebook update project, do not close!
Projects
Development

No branches or pull requests

4 participants