4 ms·
Where does this leave Keras? Wasn't it supposed to be the new high level interface to TF? EDIT: Also, what about TF-Slim?
by vmsp 10y ago
Where does this leave Keras? Wasn't it supposed to be the new high level interface to TF?
EDIT: Also, what about TF-Slim?
- maccam912 10y agoKeras did make it into tf.contrib now (with the release candidate for 1.1). I don't see it going away any time soon. TF-Slim though I'm not sure about. Never really used it myself.
- eanzenberg 10y agoThat's the big long-term question. The nice thing of this is really just having Google backing. Keras, though, still really incredible for usability.
- dontreact 10y agoGenerally all of these high level interfaces are somewhat interoperable because of the graph nature of Tensorflow. It might make your code harder to read but you can use some layers from slim (for inception-like nets this is a decent reference https://github.com/tensorflow/tensorflow/tree/master/tensorflow/contrib/slim/python/slim/nets https://github.com/tensorflow/tensorflow/tree/master/tensorf...), and some layers from Keras. I don't know as much about sonnet, but it looks like a similar story.
- sbbq 10y agoNot sure. I think Keras is more meant for education and off-the-shelf models, not so much for research due to its abstraction. Or in other words, its less customizable. I think the probably best trade-off between low-level code and coding productivity would be tf.layers, which is also in tf.core now.
- nl 10y agoKeras is heavily used in research.