From 6235c2a67adbae9c529256aec21e65a3657e39dc Mon Sep 17 00:00:00 2001 From: StevenWhitaker Date: Thu, 24 Jun 2021 15:23:16 -0400 Subject: [PATCH] Update "Composing Optimisers" docs Use `1` instead of `0.001` for first argument of `ExpDecay` in example. --- docs/src/training/optimisers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/training/optimisers.md b/docs/src/training/optimisers.md index 87a935e45f..7f3ad6bf37 100644 --- a/docs/src/training/optimisers.md +++ b/docs/src/training/optimisers.md @@ -107,7 +107,7 @@ Flux defines a special kind of optimiser simply called `Optimiser` which takes i that will be fed into the next, and the resultant update will be applied to the parameter as usual. A classic use case is where adding decays is desirable. Flux defines some basic decays including `ExpDecay`, `InvDecay` etc. ```julia -opt = Optimiser(ExpDecay(0.001, 0.1, 1000, 1e-4), Descent()) +opt = Optimiser(ExpDecay(1, 0.1, 1000, 1e-4), Descent()) ``` Here we apply exponential decay to the `Descent` optimiser. The defaults of `ExpDecay` say that its learning rate will be decayed every 1000 steps.