Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add step! #1833
base: master
Are you sure you want to change the base?
add step! #1833
Changes from 7 commits
2fa1c7c
c8f147b
1f34fd7
0765010
5b4fc17
12a8284
68a0590
c321e4f
bb7b5c5
cc31acb
5220fe9
fa68993
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is right at the beginning instead of in the
Custom Training Loop Section
. It seems to me like the custom training loop section might either be redundant or demonstrate how to have a custom gradient calculation now.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest
optimstep!
instead oftrainstep!
to indicate that this is the optimiser interface and keep the ML jargon to a minimumThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One vote for something evoking
train!
to stress that they are closely related.If the longer-term plan is to use Optimisers.jl, this may not fit with
train!
at all -- some recent discussion here: #1902 (comment) . In which case there will be an implicit-styletrain!
&Params
story, and an explicit-stylegradient
andOptimisers.update!
. With such a divide, this function wants to be clearly on thetrain!
&Params
side.Maybe it should just be 3-arg
train!
? Without a data iterator, there is no iteration, that's all: