-
-
Notifications
You must be signed in to change notification settings - Fork 221
support ForwardDiff 1.0 #2643
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
base: master
Are you sure you want to change the base?
support ForwardDiff 1.0 #2643
Conversation
9212080
to
9745606
Compare
ok we finally have enough to start testing this. |
I really looking forward to this. This currently blocks the upgrade to |
The biggest issue is likely with differentiation of interpolations because we want to make sure it doesn't change the discontinuity handling behavior. So there's a bit to do here. |
9745606
to
8722390
Compare
8722390
to
133d56d
Compare
I think this might be ready now. Let's see if tests agree. The only change needed was a change to the interpolation tests to use a left-derivative since [email protected] makes the derivative a right derivative by default. |
Is it breaking to our users that the ForwardDiff 1.0 uses the right derivative by default? We have a continuity argument, when using ForwardDiff that argument is no longer respected? Is that breaking? Or is that ForwardDiff behavior that is breaking which the user only gets if they bump to v1 as well so it's okay? |
Should we be correcting the forwarddiff branch in our continuity handling? |
I don't think so.
This would be breaking if our interpolations used ForwardDiff internally, but they don't, so it's not a problem. |
Okay so we respect ForwardDiff's branch choice and not the So okay we go with it. |
Is there anything left to do or can this be merged? I think there are plenty of repos waiting for this, such that they can test ForwardDiff v1 in their repos. |
I need to find an actual fix to |
21dca13
to
de4a69a
Compare
e12df77
to
ff0298a
Compare
lets see if the rebase magically fixes the failure? I'm very confused here because this is exactly the test I was running locally and it was passing there... |
No description provided.