-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
Fast path for Two Point BVPs #109
Conversation
avik-pal
commented
Sep 12, 2023
•
edited
Loading
edited
- Tests from ODEInterface.jl
Looks reasonable but tests fail? |
This needs to wait on SciML/SciMLBase.jl#477 I will prototype a version using ODEInterface.jl. We should be ready to merge the SciMLBase one once that is done. |
3571258
to
0f4b1df
Compare
0f4b1df
to
5f0564b
Compare
This will have to wait till we release the NonlinearSolve 2.0. The released versions can't handle residual prototype it seems so they wont work for two point BVPs. |
const DEFAULT_NLSOLVE_SHOOTING = TrustRegion(; autodiff = Val(true)) | ||
const DEFAULT_NLSOLVE_MIRK = NewtonRaphson(; autodiff = Val(true)) | ||
const DEFAULT_NLSOLVE_SHOOTING = NewtonRaphson() | ||
const DEFAULT_NLSOLVE_MIRK = NewtonRaphson() |
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.
Not so sure about that.
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 change to NewtonRaphson was before the TR bugs were fixed. We can revert this part. The autodiff = true
is redundant wince that is the current default.
Is there a reason colnew isn't supported here? Have you checked its interface to see that it'll be fine? |
|