Skip to content
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.

Sign up for GitHub

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

Jump to bottom

AD Framework specific dispatch #8

Open
3 tasks
ThummeTo opened this issue Nov 23, 2023 · 0 comments
Open
3 tasks

AD Framework specific dispatch #8

ThummeTo opened this issue Nov 23, 2023 · 0 comments
Assignees
@ThummeTo

Comments

@ThummeTo
Copy link
Owner

ThummeTo commented Nov 23, 2023 •
edited
Loading

Different AD frameworks have different requirements.
The common ChainRules interface, that is currently used, is not optimal in terms of allocations (there are allocations necessary because of type restrictions to be compliant with all AD frameworks, even if only one specific framework actually needs them).

  • Implement a dedicated ReverseDiff-Dispatch for eval/rrule
  • inplace eval! function for FMU2Output
  • Improve the common (ChainRules) functions eval/frule/rrule, so they don't need to cover for the ReverseDiff case (like e.g. this issue)
@ThummeTo ThummeTo self-assigned this Nov 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ThummeTo ThummeTo

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ThummeTo