You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the official TensorFlow blog posts, it was said that tf.layers would be depreciated and tf.keras.layers would be the preferred method. However in architectures.pytf.layers has been used everywhere to create the encoder and decoder models. It would be great if these could be modifed to use tf.keras.layers since others would be able to reuse the code without worry.
#feature request
The text was updated successfully, but these errors were encountered:
Our initial focus has been on open-sourcing the exact architectures/implementations that can be used to reproduce the experiments in the study "Challenging Common Assumptions in the Unsupervised Learning of Disentangled Representations" (https://arxiv.org/abs/1811.12359). However, we are looking into ways to make sure disentanglement_lib is compatible with the upcoming changes to TensorFlow. In the meantime, it is very easy to define your own encoder/decoder architectures and to use them via gin with disentanglement_lib.
In the official TensorFlow blog posts, it was said that
tf.layers
would be depreciated andtf.keras.layers
would be the preferred method. However in architectures.pytf.layers
has been used everywhere to create the encoder and decoder models. It would be great if these could be modifed to usetf.keras.layers
since others would be able to reuse the code without worry.#feature request
The text was updated successfully, but these errors were encountered: