FIX possible detrimental tf api usage #9
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi developers,
When I use your repository, I found that there might be some potential detrimental usage of TensorFlow in your code and I help you modified as below:
tf.to_floathas been deprecated since tf 1.13.0 and removed in tf 2.0.0-alpha. It's better to replace it withtf.cast, otherwise, it might lead to a crash in the future.tf.contrib.framework.get_global_stephas been deprecated since tf 1.4.0 and it's better to replace it with its new version APItf.train.get_global_step.tf.contrib.metrics.streaming_accuracyhas been deprecated since tf 1.5.0 and it's better to replace it withtf.metrics.accuracy.@raviqqe @davidyapdy
Hope you could take my advice and look forward to your reply! 😃