Why even in the era of TF2.x does ART not like eager execution enabled? Why stick to TF1.x style code? #1906
-
This line assumes you have eager execution disabled. However, for custom models, disabling eager execution leads to a lot of error. For example: tensorflow/tensorflow#39908 Why does ART still rely on out-of-date TF1.x style code? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Hi @swapnilsayansaha ART does not rely on out-of-date TF1.x style code as you call it. For the era of TF2.x, also as you call it, and because ART likes eager execution we have created |
Beta Was this translation helpful? Give feedback.
-
Thanks. That function provided a lot of help! |
Beta Was this translation helpful? Give feedback.
Hi @swapnilsayansaha ART does not rely on out-of-date TF1.x style code as you call it. For the era of TF2.x, also as you call it, and because ART likes eager execution we have created
art.estimators.classification.TensorFlowV2Classifier.
but keptKerasClassifier
for backward-compatibility.