-
-
Notifications
You must be signed in to change notification settings - Fork 24
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 Adapt.adapt_structure
method for Optimisers.Leaf
#180
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
8077900
Adapt.adapt_structure method for Optimisers.Leaf
vpuri3 8906e50
import Adapt.jl
vpuri3 0c66a52
add Adapt.jl to Project.toml
vpuri3 f48c128
adapt compat
vpuri3 e8ba26e
based on discussion: adapt_structure method does not maintain IdDict …
vpuri3 89c6fd0
Update ext/OptimisersAdaptExt.jl
vpuri3 3269bd9
Merge branch 'master' into patch-1
vpuri3 8c1c073
edit warning to indicate that this is a correctness issue
vpuri3 978ed6f
Update ext/OptimisersAdaptExt.jl
vpuri3 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
module OptimisersAdaptExt | ||
|
||
import Adapt | ||
import Optimisers: Leaf | ||
|
||
function Adapt.adapt_structure(to, leaf::Leaf) | ||
@warn """`Optimisers.Leaf` object does not support device transfer via | ||
`Adapt.jl`. This is because `Adapt.jl` does not handle shared parameters (i.e. the same parameter array | ||
appearing more than once in the model), and in such cases this will lead to incorrect gradient updates. | ||
Avoid this by calling `Flux.gpu/cpu` or `MLDataDevices.cpu_device()/gpu_device()` on the | ||
optimiser state object. | ||
""" maxlog=1 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @mcabbott i edited the warning to say that this is a correctness issue. |
||
|
||
rule = Adapt.adapt(to, leaf.rule) | ||
state = Adapt.adapt(to, leaf.state) | ||
|
||
Leaf(rule, state, leaf.frozen) | ||
end | ||
|
||
end |
Oops, something went wrong.
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.
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.
Do we want this only once? It's a potential correctness bug, not a performance issue.
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.
Is your worry that the message will get lost in the shuffle somehow? My thought was that people may have a valid use for this, and as long as they know what they're getting into the library doesn't have to remind them on every call.
Another practical concern would be what happens when someone tries to call
cu(large state tree)
. Not settingmaxlog
would mean other logging is drowned out because this warning would trigger for everyLeaf
.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 agree that printing 100 times on a big model is too much. Ideal would be once, on every invocation, IMO... but that's hard to make happen.
It's not the world's biggest correctness bug to ignore shared parameters, so maybe we should live with it. Maybe the message should say that's what the problem is?