-
-
Notifications
You must be signed in to change notification settings - Fork 269
update Moderation example to best practice and v4 #297
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
Conversation
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
examples/references.bib
Outdated
@online{vandenbergSPSS, | ||
author = {van den Berg, R. G}, | ||
title = {SPSS Moderation Regression Tutorial}, | ||
year = XXXXX, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is breaking the docs build. Can you try removing the year key altogether?
View / edit / reply to this conversation on ReviewNB OriolAbril commented on 2022-03-20T12:52:26Z PyMC3 -> PyMC drbenvincent commented on 2022-03-20T13:35:04Z done |
View / edit / reply to this conversation on ReviewNB OriolAbril commented on 2022-03-20T12:52:27Z PyMC3 -> PyMC |
View / edit / reply to this conversation on ReviewNB OriolAbril commented on 2022-03-20T12:52:27Z Line #2. COORDS = {"obs": np.arange(len(x))} There is no need to define coords with aranges in v4 provided they are first use (and can therefore be inferred automatically) in a drbenvincent commented on 2022-03-20T13:35:29Z have removed coords |
Co-authored-by: Oriol Abril-Pla <[email protected]>
done View entire conversation on ReviewNB |
have removed coords View entire conversation on ReviewNB |
It's not adding the But docs now seems to work :) |
Everything looks good, but still no |
I think we still need to update the style guide, but you can see that CI is passing without them. They should not be present anymore (and should be removed from the ones that have them). |
View / edit / reply to this conversation on ReviewNB OriolAbril commented on 2022-03-20T16:29:34Z I mentioned the explanation category in the myst view because its where I noticed, but I should probably done that here. if both files are updated without syncing them then only the changes in the most recent one are kept :/
The last paragraph about mediation analysis should also have a link to the mediation notebook (and viceversa I guess, not sure if the mediation has been updated already) drbenvincent commented on 2022-03-20T17:14:09Z Have attempted to cross reference the two notebooks |
Have attempted to cross reference the two notebooks View entire conversation on ReviewNB |
Notebook cross references now work fine |
Thanks! How has the extra myst step in pre-commit worked out for you? |
I have never tried that on specific files and the error doesn't make much sense to me, could it be because it was unstaged (before doing git add that then shows in git status in green)? |
Updates the moderation analysis example (see #170) to current best practice.
Because this is just a minor update with no substantive changes, I propose to speed things up that we don't necessarily need 2 reviewers. The only meaningful change was to shift all custom plot functions into a single (hidden) code cell.
Note: in
pm.sample
, I'm currently having to providenuts={"target_accept": 0.9}
rather than justtarget_accept=0.9
(see pymc-devs/pymc#5620)