Update layers and losses for mixed precision compatibility. #490
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.
What
K.floatx
to refer toinputs.dtype
orcompute_type
.y_true
toy_pred.dtype
to preserve dtype inlosses.py
.Why
floatx
to float16 is not recommended for training, and instead the global precision policy should be changed tomixed_float16
. However, theLocation
andNormalization
layers were set to outputK.floatx()
which conflicts with the global precision policy. Instead, setting the dtype to the internalcompute_type
orinputs.dtype
preserves the mixed dtype policy.