Skip to content

GitLab

Switch branch/tag
  1. 06 Jun, 2021 1 commit
  3. 25 May, 2021 1 commit
  5. 29 Apr, 2021 2 commits
  7. 23 Mar, 2021 2 commits
  9. 01 Mar, 2021 2 commits
  11. 28 Feb, 2021 4 commits
  13. 22 Jan, 2021 2 commits
  15. 19 Oct, 2020 2 commits
  17. 13 Oct, 2020 4 commits
  19. 12 Aug, 2020 2 commits
  21. 06 Aug, 2020 2 commits
  23. 29 Apr, 2020 1 commit
  25. 14 Apr, 2020 1 commit
  27. 09 Apr, 2020 1 commit
  29. 17 Mar, 2020 1 commit
  31. 14 Mar, 2020 1 commit
  33. 29 Jan, 2020 1 commit
  35. 11 Dec, 2019 1 commit
  37. 21 Nov, 2019 1 commit
  39. 19 Nov, 2019 1 commit
  41. 10 Oct, 2019 1 commit
  43. 04 Sep, 2019 1 commit
  45. 21 Aug, 2019 1 commit
  47. 19 Aug, 2019 1 commit
    • Reed Wanderman-Milne's avatar
      Do not expose --max_train_steps in models that do not use it. · 824ff2d6
      Reed Wanderman-Milne authored 
      Only the V1 resnet model uses --max_train_steps. This unexposes the flag in the keras_application_models, mnist, keras resnet, CTL resnet Models. Before this change, such models allowed the flag to be specified, but ignored it.

I also removed the "max_train" argument from the run_synthetic function, since this only had any meaning for the V1 resnet model. Instead, the V1 resnet model now directly passes --max_train_steps=1 to run_synthetic.

PiperOrigin-RevId: 264269836
      824ff2d6
  49. 02 Aug, 2019 2 commits
  51. 23 Jul, 2019 1 commit