Skip to content

GitLab

Switch branch/tag
  1. 06 May, 2021 1 commit
  3. 05 May, 2021 2 commits
  5. 04 May, 2021 2 commits
  7. 03 May, 2021 2 commits
  9. 30 Apr, 2021 2 commits
  11. 28 Apr, 2021 3 commits
  13. 27 Apr, 2021 5 commits
  15. 26 Apr, 2021 1 commit
  17. 24 Apr, 2021 1 commit
  19. 22 Apr, 2021 2 commits
  21. 21 Apr, 2021 4 commits
  23. 19 Apr, 2021 1 commit
  25. 17 Apr, 2021 1 commit
  27. 16 Apr, 2021 1 commit
  29. 15 Apr, 2021 2 commits
  31. 14 Apr, 2021 1 commit
  33. 13 Apr, 2021 4 commits
    • Rebecca Chen's avatar
      Internal change · 87796817
      Rebecca Chen authored 
      PiperOrigin-RevId: 368157180
      87796817
    • Jaehong Kim's avatar
      Internal change · 0c814fa2
      Jaehong Kim authored 
      PiperOrigin-RevId: 368130039
      0c814fa2
    • Fan Yang's avatar
      Add more pytype checking. · f8f4845c
      Fan Yang authored 
      PiperOrigin-RevId: 368129317
      f8f4845c
    • Reed Wanderman-Milne's avatar
      Use nonexperimental mixed precision API. · 4334a892
      Reed Wanderman-Milne authored 
      This replaces symbols in tf.keras.mixed_precision.experimental with the corresponding nonexperimental symbols. In some cases, passing a Policy is replaced with passing a policy name for conciseness.

Additionally, for the Shakespeare model, the loss_scale flag is removed, since supporting it with the nonexperimental API is slightly more verbose and it is recommended users use the default loss scale.

PiperOrigin-RevId: 368123944
      4334a892
  35. 12 Apr, 2021 4 commits
  37. 09 Apr, 2021 1 commit
    • Reed Wanderman-Milne's avatar
      Remove dynamic_loss_scale argument to define_performance. · e353e4e5
      Reed Wanderman-Milne authored 
      All models which support loss scaling support dynamic loss scaling, so the argument has no purpose. It used to be that some models scaled the loss manually instead of using a LossScaleOptimizer, and so did not support dynamic loss scaling.

PiperOrigin-RevId: 367719521
      e353e4e5