Skip to content

Update VI quickstart and VI LDA notebooks #228

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

Closed
wants to merge 4 commits into from

Conversation

chiral-carbon
Copy link
Collaborator

Addresses issues #135 and #137 and aims to advance it to Best Practices

@review-notebook-app
Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

add references and post directive

fix tag

fix referencing style
}


@misc{sklearn2020topicextraction,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this entry is rendered a bit strangely right now, I think we should add an author like scikit-devs or something of the sort so the inline citation looks better. Or it might be also possible to use a custom text when citing, maybe with type cite:label I think it is (do check the docs please)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does the rendered citation look better now?

"* Rezende, D. J., & Mohamed, S. (2015). Variational inference with normalizing flows. arXiv preprint arXiv:1505.05770.\n",
"* Salimans, T., Kingma, D. P., & Welling, M. (2015). Markov chain Monte Carlo and variational inference: Bridging the gap. In International Conference on Machine Learning (pp. 1218-1226)."
"\n",
":::{bibliography} :filter: docname in docnames\n",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the bibliography is not working. Is the filter think on the same line as the :::{bibliography}?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes it was, have changed it

@review-notebook-app
Copy link

View / edit / reply to this conversation on ReviewNB

OriolAbril commented on 2021-10-13T04:53:38Z
----------------------------------------------------------------

I would default to hiding this output with a toggleable: https://myst-nb.readthedocs.io/en/latest/use/hiding.html.


@review-notebook-app
Copy link

View / edit / reply to this conversation on ReviewNB

OriolAbril commented on 2021-10-13T04:53:39Z
----------------------------------------------------------------

and make this a proper reference, see https://arviz-devs.github.io/arviz/contributing/developer_guide.html#hyperlinks. The complete import path is below, as it's quite long I would use ~ to omit it


@review-notebook-app
Copy link

View / edit / reply to this conversation on ReviewNB

OriolAbril commented on 2021-10-13T04:53:40Z
----------------------------------------------------------------

make minibatch a clickable reference, and hide output or even remove directly the cell below


@review-notebook-app
Copy link

View / edit / reply to this conversation on ReviewNB

Sayam753 commented on 2021-10-17T20:50:10Z
----------------------------------------------------------------

Shouldn't the coords be -

coords = {
    "obs_id": np.arange(X_train.shape[0]),
    "attr": np.arange(X_train.shape[1]),
    "class": np.unique(y_train).shape[0],
}

?


@review-notebook-app
Copy link

View / edit / reply to this conversation on ReviewNB

Sayam753 commented on 2021-10-17T20:50:11Z
----------------------------------------------------------------

Line #1.    coords = {"obs_id": data.shape[0], "col": data.shape[1]}

Same question here. Should data.shape[0] be wrapped in np.arange and then used in coords?


@drbenvincent
Copy link
Contributor

Can you remove all pymc.* or pymc3.* tags in the first code cell (of both notebooks)?

@twiecki
Copy link
Member

twiecki commented Jun 12, 2022

Can someone take over?

@ferrine
Copy link
Member

ferrine commented Jun 13, 2022

The LDA notebook should be deleted, it uses a not implement functionality. I do something similar in #373

@drbenvincent
Copy link
Contributor

The LDA notebook should be deleted, it uses a not implement functionality. I do something similar in #373

@ferrine Will you be deleting this LDA notebook in your PR #373?

Or do you want me to do a PR to remove this notebook?

@ferrine
Copy link
Member

ferrine commented Jun 24, 2022

I will delete it

@OriolAbril OriolAbril closed this Nov 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants