Skip to content

[WIP]Start experimenting with DI #31

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

Closed
wants to merge 17 commits into from
Closed

[WIP]Start experimenting with DI #31

wants to merge 17 commits into from

Conversation

Vaibhavdixit02
Copy link
Member

Checklist

  • Appropriate tests were added
  • Any code changes were done in a way that does not break public API
  • All documentation related to code changes were updated
  • The new code follows the
    contributor guidelines, in particular the SciML Style Guide and
    COLPRAC.
  • Any new documentation only uses public API

Additional context

Add any other context about the problem here.

@gdalle
Copy link
Contributor

gdalle commented Apr 17, 2024

@Vaibhavdixit02 DifferentiationInterface v0.2 is out, and we got rid of the bang-bang in favor of always mutating the provided storage. This will make all of our lives easier

@gdalle
Copy link
Contributor

gdalle commented Apr 29, 2024

@Vaibhavdixit02 DI v0.3 is out, and it even removes the need for SparseDiffTools in the simplest cases. Take it for a spin!

@gdalle
Copy link
Contributor

gdalle commented May 31, 2024

You need a more recent version of DI, at least 0.5.1 for Enzyme to work in second order and 0.5.2 for it to be fast. The tests are still running with 0.5.0.

@Vaibhavdixit02
Copy link
Member Author

Come on, I run all tests against DI master locally depending on releases is for p******! 🤣

@gdalle
Copy link
Contributor

gdalle commented May 31, 2024

It seems the last tests were run 3 days ago, you closing and reopening has apparently not re-triggered CI

@Vaibhavdixit02
Copy link
Member Author

Because of the merge conflict

Enzyme v0.12 now requires that all inputs are marked with an activity, and so these need to manually be marked const.
@Vaibhavdixit02 Vaibhavdixit02 marked this pull request as ready for review May 31, 2024 14:54
@gdalle
Copy link
Contributor

gdalle commented May 31, 2024

Indeed you pushed a merge conflict at least in the project file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants