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
Section 2 pymc3 error #14
Comments
Yep, we changed that namespace, easy fix. |
@krispy1946 Maybe do a PR. |
Some advice please as I'm not a regular 'user' of git.
I've committed my local changes to my cloned repository but when I make a
pull request I get every change made (whether relevant or not). Is it
possible to isolate the one simple code change made or do I send the lot?
Thanks.
Chris
…On 2 February 2017 at 10:08, Thomas Wiecki ***@***.***> wrote:
@krispy1946 <https://github.com/krispy1946> Maybe do a PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AECpBbortCc7_4e2mTokWN6lpUVoMgjNks5rYZz1gaJpZM4L025A>
.
|
Thanks for flagging Chris. I'm re-running all notebooks now and fixing issues. Been a while and PYMC3 has come on even further since I last used it. Will push later this weekend. |
Pushed updated notebooks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Section 2 - Model Check II - Bayes Factor
Model fails
Found a fix suggested by Cameron Davidson-Pilson which looks like it was intended to be merged into your code (but seems it wasn't?). The suggested revision to lambda works fine.
The text was updated successfully, but these errors were encountered: