Skip to content

improvements to glm.ipynb #179

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

Merged
merged 4 commits into from
Jul 30, 2021
Merged

improvements to glm.ipynb #179

merged 4 commits into from
Jul 30, 2021

Conversation

mjhajharia
Copy link
Member

glm.ipynb is not broken anymore after #177, a few minor updates in documentation or markdown cells are still left, doing them in this PR as i get time, nothing urgent, but everyone feel free to make suggestions!!!!

@review-notebook-app
Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

@mjhajharia
Copy link
Member Author

@OriolAbril I've taken care of all the comments, copying this comment from the previous PR over here so it stays in my head.

_

The explanation is great and the link to the family object too. I also have a myst related extra note here (again, so not implement yet) that we could use intersphinx for that link so that if bambi decides to rename master to main, we'll only have to change a link in conf.py and regenerate docs for everything to work again, otherwise we'll have to track down all links and update them. Same thing if documentation is reorganized, files renamed or moved to a different folder structure

_

Copy link
Contributor

@MarcoGorelli MarcoGorelli left a comment

Choose a reason for hiding this comment

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

looks good to me

@review-notebook-app
Copy link

review-notebook-app bot commented Jun 18, 2021

View / edit / reply to this conversation on ReviewNB

OriolAbril commented on 2021-06-18T11:54:05Z
----------------------------------------------------------------

Here is where I think we should add a sentence on what the common key passed to priors means. Maybe

The "common" key in the priors dict defines the prior for all common effects at the same time. As explained in a section below, Bambi supports two types of effects, common and group effects.

@review-notebook-app
Copy link

View / edit / reply to this conversation on ReviewNB

OriolAbril commented on 2021-06-18T11:54:06Z
----------------------------------------------------------------

I would leave the explanation text as it was originally and only remove the link to the source code. I find the extra explanation inside the parenthesis a bit confusing here, because here we are talking about common and group as types of effects, not as keys of the priors argument.


@fonnesbeck
Copy link
Member

@almostmeenal just address Oriol's comment and this is good to merge.

@mjhajharia
Copy link
Member Author

thanks a ton for the help @OriolAbril !!!!

@mjhajharia
Copy link
Member Author

@fonnesbeck this is done, i'm sorry for the delay :((

@OriolAbril OriolAbril merged commit dfbc7de into pymc-devs:main Jul 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants