This builds the following graph:pic.twitter.com/WQzvf6bJZh
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
I guess you mean only saving the weights, and always re-executing the original code when loading the model. This is definitely better than saving the bytecode, but it's limited: it implies you will still have access to the original code, and it won't work across platforms.
So if you want to load your model in JavaScript, you'd have to write a JS version of your model first, then you'd load your saved weights. This is potentially error-prone. With the Functional API, you can save your model in Python then reload it in JS w/o writing any model code.
Honestly I don’t know what I’m talking about but my preference would always be to create that abstraction and yes, serialize the weights and couple that to a bound representation. Out of curiosity do you guys ever define architectures by just zeroizing large parts of the matrix?
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.