-
-
Notifications
You must be signed in to change notification settings - Fork 75
Mooncake, LinearSolve integration - 1 #791
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
Conversation
include("wrappers.jl") | ||
|
||
import Base: (\), size, getproperty, setproperty!, propertynames, show, | ||
import Base: size, getproperty, setproperty!, show, |
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.
what's this about?
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 was getting ExplicitImports, Aqua errors in all / Tests - NoPre
since the import were not being technically directly used. In the same file, they are used as Base.propertynames etc. so I removed the imports.
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.
after this we get the errors : https://github.com/SciML/LinearSolve.jl/actions/runs/18461238570/job/52593055519?pr=791. (dont seem PR related)
Checklist
The current PR handles differentiating when using Mooncake for functions tested in
test/adjoint.jl
,solve()
. We reuse the currentChainrules
rules defined insrc/adjoint.jl
. These rules are now used byZygote
andMooncake
.An rrule for
solve!
are required, followed by tests forMooncake
(relevant to the ones in theEnzyme.jl
Extension testfile). I will add this is a subsequent seperate PR.NOTE : Mooncake only works with Julia (lts) as of now, due to how it handles IR changes in different Julia versions
contributor guidelines, in particular the SciML Style Guide and
COLPRAC.
Additional context
Add any other context about the problem here.