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
Edward Restructuring #292
Comments
@dustinvtran Edit: My motivation for these questions is to better organise the future python notebooks and to redo the existing tutorials and example code. If there is going to be a big change from the current version in terms of organisation, this should start being reflected in the examples - unless there are going to be many more changes until the next release! |
inference.run
in getting-started
I've changed the name of the issue to better represent my doubt. My main questions are:
Thanks a lot for the patience to hear this out - it'll help me further contribute, and am sure will help others as well. Edit: Found #249, but am not very sure why just running MVFI (as it is a synonym) is not giving me the same results as before. |
The website is updated according to the latest development version of Edward and not the latest stable version. This is because during development we update scripts in the
Note this is all bad practice. We have no guarantees that any code from the latest stable version also works on the latest development version. Edward's infrastructure is in flux, as we're solving open research challenges in the design and implementation of probabilistic programming languages. (But we're slowly but surely converging!) |
@dustinvtran, thanks for the reply! |
Sure. I tried it on a few machines (both Linux and Mac, and on GPU vs CPU) and it does work. Can you provide more details? |
I also occasionally get the |
Looks like inference wasn't run. Have you tried to restart the kernel and run each block sequentially? Alternatively, you can look at the output from the inference run. In the last several hundred iterations the loss function should be close to zero. re: |
Strange things:
|
Would also like to note that the plotting of before running inference and after running it in each case is different. So I am running the inference each time, it's just not working. Also, if you see the current version on the getting-started notebook in the code-base, the last few cells are not run and you cannot see the final plot. I was trying to fix that when I noticed that |
Some steps at reproducibility might be helpful. Could you report a seed via In general, I can only say that repeated application of certain code blocks will certainly produce bugs. Unlike NumPy code, calling TensorFlow lines multiple times adds more tensors to the computational graph, which can break subsequent code. |
Never mind, works now :D |
Ok, figured where I was going wrong - my installations of Edward were all over the place, and the tensorflow graphs were messing with the results. Sorry for the trouble! |
oh, perfect. glad it was sorted out! |
Hello, when I try and redo the getting-started tutorial using the latest github version of the code, it seems as if
ed.MFVI
behaves very differently. Is the current release of edward on PIP and the bleeding-edge version different for this?The model learned now doesn't learn the relationship. I'm sorry if I missed out on something - changes happen very fast on Edward!
Edit: Noticed that MVFI doesn't exist in the
inference.py
file. Where is it right now? And is it different in it's implementation from the older code?Second edit: Noticed the massive restructuring - but still don't know where MVFI is.
The text was updated successfully, but these errors were encountered: