Skip to content

GitLab

Switch branch/tag
  1. 16 Nov, 2021 2 commits
  3. 05 Nov, 2021 1 commit
  5. 03 Sep, 2021 1 commit
  7. 30 Aug, 2021 1 commit
  9. 06 Jun, 2021 2 commits
  11. 28 May, 2021 1 commit
  13. 13 Apr, 2021 1 commit
    • 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
  15. 29 Mar, 2021 1 commit
  17. 22 Mar, 2021 1 commit
  19. 05 Mar, 2021 1 commit
  21. 21 Dec, 2020 1 commit
  23. 02 Dec, 2020 1 commit
  25. 30 Nov, 2020 2 commits
  27. 27 Nov, 2020 1 commit
  29. 26 Nov, 2020 2 commits
  31. 24 Nov, 2020 1 commit
  33. 03 Nov, 2020 1 commit
  35. 13 Sep, 2020 1 commit
  37. 10 Sep, 2020 1 commit
  39. 12 Aug, 2020 2 commits
  41. 04 Aug, 2020 2 commits
  43. 03 Aug, 2020 2 commits
  45. 31 Jul, 2020 3 commits
  47. 30 Jul, 2020 2 commits
    • Tomer Kaftan's avatar
      Pre-emptively disable the KerasTensors refactoring for the detection models in... · 071bb243
      Tomer Kaftan authored 
      Pre-emptively disable the KerasTensors refactoring for the detection models in tensorflow models/official/vision/detection, because they rely on several unsupported things that will stop working entirely when the refactoring goes live.

Specifically:
* The custom layers implement `__call__` instead of `call` and rely on manually enter the keras backend graph
* The vision models try to use `tf.while_loop` as Keras op layers during functional API construction, which is unsupported.

Updating the models to avoid this would subtly change the variable names and break the pre-existing tf1-style name-based checkpoints, so for now we will just disable the KerasTensors refactoring for these models.

PiperOrigin-RevId: 323937426
      071bb243
    • Tomer Kaftan's avatar
      Pre-emptively disable the KerasTensors refactoring for the detection models in... · ccc60760
      Tomer Kaftan authored 
      Pre-emptively disable the KerasTensors refactoring for the detection models in tensorflow models/official/vision/detection, because they rely on several unsupported things that will stop working entirely when the refactoring goes live.

Specifically:
* The custom layers implement `__call__` instead of `call` and rely on manually enter the keras backend graph
* The vision models try to use `tf.while_loop` as Keras op layers during functional API construction, which is unsupported.

Updating the models to avoid this would subtly change the variable names and break the pre-existing tf1-style name-based checkpoints, so for now we will just disable the KerasTensors refactoring for these models.

PiperOrigin-RevId: 323937426
      ccc60760
  49. 24 Jul, 2020 1 commit
    • Srihari Humbarwadi's avatar
      Fixed typos · b3f63b00
      Srihari Humbarwadi authored 
       - Fixed `intermediate_scale` in  `Anchor`
 - "ratio" and "divisible" in doc string
      b3f63b00
  51. 20 Jul, 2020 2 commits
    • Tomer Kaftan's avatar
      Make hack in official/vision/detection models that enters the backend keras... · 363a36cd
      Tomer Kaftan authored 
      Make hack in official/vision/detection models that enters the backend keras graph stop happening once we enable the Functional API KerasTensors refactoring:

As a workaround hack for the tf op layer conversion being fragile, the detection models have to explicitly enter the Keras backend graph.

When we enable the KerasTensors refactoring of the Functional API internals, the op layer conversion will be much more reliable and this hack will not be necessary. In addition, the hack actually causes the models to break when we enable the refactoring (because it causes tensors to leak out of a graph).

So, this CL changes the existing hack to stop applying once we've enabled the KerasTensors refactoring.

PiperOrigin-RevId: 322229802
      363a36cd
    • Tomer Kaftan's avatar
      Make hack in official/vision/detection models that enters the backend keras... · ae8845ce
      Tomer Kaftan authored 
      Make hack in official/vision/detection models that enters the backend keras graph stop happening once we enable the Functional API KerasTensors refactoring:

As a workaround hack for the tf op layer conversion being fragile, the detection models have to explicitly enter the Keras backend graph.

When we enable the KerasTensors refactoring of the Functional API internals, the op layer conversion will be much more reliable and this hack will not be necessary. In addition, the hack actually causes the models to break when we enable the refactoring (because it causes tensors to leak out of a graph).

So, this CL changes the existing hack to stop applying once we've enabled the KerasTensors refactoring.

PiperOrigin-RevId: 322229802
      ae8845ce
  53. 01 Jul, 2020 1 commit
  55. 30 Jun, 2020 2 commits