3 ms·
I've had the pleasure of working with Edward for the last couple of months, and it's been the first PPL I've felt comfortable building a stable production codeb
by cshenton 9y ago
I've had the pleasure of working with Edward for the last couple of months, and it's been the first PPL I've felt comfortable building a stable production codebase on top of.
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.
- nextos 9y agoWhat kind of production stuff are you developing? I'm a probabilistic programming enthusiast, and I had the impression it's still an open research field.
- splike 9y agoI've only seen Edward for the first time today, and it looks quite nice. Could you (or anyone else) comment on why would you choose Edward over something PyMC3? How does it compare?
- cshenton 9y agoI had the same question when I was first choosing libraries for my current project! 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 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.
- splike 9y agoThat's useful, thanks!