Edward is officially moving into TensorFlow
discourse.edwardlib.org
discourse.edwardlib.org
Edit: Just editing the URL leads to an HTTPS error because the certificate is only valid for *.github.io; you need to use HTTP.
I think this also applies to people on your mailing list. So often I get announcements sent out to a mailing list I signed up for where I forgot what the project is. Just having a sentence or two with a reminder goes a long way toward keeping me interested.
It strikes a great balance between feeling like you're programming with probability distributions, and providing ways of diving under the hood to improve performance when you need to (like tweaking the underlying tf optimizer, or being able to implement your own distribution to use like a native one).
If such a library didn't exist, I would have needed to build my own. Congrats on the move to tf.contrib.
I'm a probabilistic programming enthusiast, and I had the impression it's still an open research field.
Could you (or anyone else) comment on why would you choose Edward over something PyMC3? How does it compare?
So I put together this comparison of PyMC3, Edward, and Stan. It's jut doing bayesian inference on the location and scale of data sampled from a normal distribution. Super simple, but highlights the differences between the libraries.
https://github.com/cshenton/normal-comparison
Having worked with Edward, the LOC difference is deceptive. Edward has really solid abstract base classes, so developing on it is much more expressive for larger projects. I unequivocally recommend using Edward.
Hopefully not a trend of everything being subsumed by Tensorflow.
Why?
Are you really saying those are all monopolies in their categories?
Edward has been a promising addition to the PPL landscape. I actually preferred using it with Theano when I used it but that was a year ago, and it seems to have been developing rapidly. I have mixed feelings about this announcement, although to be honest I don't totally even really understand all the implications of it. In some ways I'm not sure how much Edward incrementally adds above and beyond TF; it has occupied a niche between something like TF and Stan or PyMC which is fine enough but I've sometimes wondered if it was sustainable in the long run. I have appreciated it being around, though, and have hoped it would continue to develop.
R? Eigen? Neanderthal? HMatrix?
(Yes, none of these are exactly 1:1 equivalent with numpy, but there absolutely are options. And from my point of view, having some options which aren’t tied to Python is healthy).
It aims to have more features, and more speed than numpy, with Clojure, on the JVM + Nvidia + AMD + Intel.
Also relevant here is Bayadera, Clojure/GPU Bayesian modeling lib for the JVM: http://github.com/uncomplicate/bayadera
On the JVM, we're trying to do something like pytorch/numpy on the JVM. We also have python bindings:
https://github.com/deeplearning4j/nd4j
https://github.com/deeplearning4j/jumpy
We've been building this since 2014. Of note is we'll also be able to import TF, pytorch,.. in the next few months.
We're also an eclipse foundation project as of recently.
I think point still applies for new developing software: multiple implementations can corroborate each other or help identify bugs.
and then discover that they are all using netlib/lapack under the hood :b
https://research.fb.com/facebook-and-microsoft-introduce-new...
That book’s balance between theory and practice is remarkable, but im no fan of R :/
That being said, Dustin is probably working closely with Google people to do this properly, so it'll probably turn out ok in the end.
Anyone got experience of using Edward for serious inference using MCMC?
[1] http://andrewgelman.com/2017/05/31/compare-stan-pymc3-edward...