Skip to content

GitLab

Switch branch/tag
  1. 28 Feb, 2020 1 commit
  3. 25 Feb, 2020 1 commit
  5. 21 Feb, 2020 2 commits
  7. 20 Feb, 2020 1 commit
  9. 13 Feb, 2020 1 commit
  11. 29 Jan, 2020 1 commit
  13. 27 Jan, 2020 1 commit
  15. 21 Jan, 2020 1 commit
  17. 17 Jan, 2020 1 commit
  19. 15 Dec, 2019 1 commit
  21. 14 Dec, 2019 2 commits
  23. 11 Dec, 2019 1 commit
  25. 06 Dec, 2019 1 commit
  27. 05 Dec, 2019 1 commit
  29. 04 Dec, 2019 1 commit
  31. 27 Nov, 2019 1 commit
  33. 25 Nov, 2019 1 commit
  35. 21 Nov, 2019 1 commit
  37. 19 Nov, 2019 1 commit
  39. 18 Nov, 2019 1 commit
  41. 11 Nov, 2019 1 commit
  43. 28 Oct, 2019 1 commit
  45. 21 Oct, 2019 1 commit
  47. 16 Oct, 2019 1 commit
    • Reed Wanderman-Milne's avatar
      Add support for the tf.keras.mixed_precision API in NCF · cb913691
      Reed Wanderman-Milne authored 
      To test, I did 50 fp32 runs and 50 fp16 runs. I used the following command:

python ncf_keras_main.py --dataset=ml-20m --num_gpus=1 --train_epochs=10 --clean --batch_size=99000 --learning_rate=0.00382059 --beta1=0.783529 --beta2=0.909003 --epsilon=1.45439e-7 --layers=256,256,128,64 --num_factors=64 --hr_threshold=0.635 --ml_perf --nouse_synthetic_data --data_dir ~/ncf_data_dir_python3 --model_dir ~/tmp_model_dir --keras_use_ctl

For the fp16 runs, I added --dtype=fp16. The average hit-rate for both fp16 and fp32 was 0.6365. I also did 50 runs with the mixed precision graph rewrite, and the average hit-rate was 0.6363. The difference is likely due to noise.

PiperOrigin-RevId: 275059871
      cb913691
  49. 10 Oct, 2019 1 commit
  51. 07 Oct, 2019 1 commit
  53. 24 Sep, 2019 1 commit
  55. 09 Sep, 2019 1 commit
  57. 04 Sep, 2019 1 commit
  59. 30 Aug, 2019 1 commit
  61. 26 Aug, 2019 1 commit
  63. 23 Aug, 2019 2 commits
  65. 21 Aug, 2019 1 commit
  67. 20 Aug, 2019 3 commits
  69. 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