1. 02 Apr, 2020 1 commit
  2. 31 Mar, 2020 1 commit
  3. 30 Mar, 2020 2 commits
  4. 25 Mar, 2020 1 commit
  5. 17 Mar, 2020 1 commit
  6. 15 Mar, 2020 1 commit
  7. 14 Mar, 2020 1 commit
  8. 12 Mar, 2020 2 commits
  9. 11 Mar, 2020 1 commit
  10. 09 Mar, 2020 3 commits
  11. 25 Feb, 2020 1 commit
  12. 13 Feb, 2020 1 commit
  13. 01 Feb, 2020 1 commit
  14. 29 Jan, 2020 1 commit
  15. 27 Jan, 2020 1 commit
  16. 21 Jan, 2020 1 commit
  17. 04 Jan, 2020 1 commit
  18. 19 Dec, 2019 1 commit
  19. 18 Dec, 2019 1 commit
  20. 14 Dec, 2019 2 commits
  21. 11 Nov, 2019 1 commit
  22. 05 Nov, 2019 1 commit
  23. 12 Oct, 2019 1 commit
  24. 11 Oct, 2019 3 commits
  25. 10 Oct, 2019 1 commit
  26. 17 Sep, 2019 1 commit
  27. 09 Sep, 2019 1 commit
  28. 04 Sep, 2019 1 commit
  29. 26 Aug, 2019 1 commit
  30. 23 Aug, 2019 2 commits
  31. 20 Aug, 2019 1 commit
  32. 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