-
Notifications
You must be signed in to change notification settings - Fork 191
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
Improve time-stepping with bug fixes and performance enhancements #4583
Comments
Is there something in particular you're asking me to do here? |
Closing because I don't know what you want me to do. |
Sorry for the delay in my reply @wthrowe ... this issue simply refers to the work you were already doing to improve the time stepper, including to fix the dense output bug #4399. If this work is already done, I'll close the issue but would like to link the relevant PRs (I looked at your recent PRs but couldn't figure out if any applied to this). |
The other big thing is the predictor-corrector stepper to hopefully speed up the code. I think last time this came up you said it'll come post-IMEX, we mostly just want to track that this is something that could help a lot. |
OK, predictor-corrector is a reasonable request. All of #4399, IMEX, and PC require the history rewrite, which is done except that I'm trying to factor out one of the internal data structures for more general use. (And that git is having issues with the rebase, which I have to work around somehow.) IMEX and PC are otherwise independent, I think, but IMEX is higher priority because someone is already trying to use it. |
Sounds good! I also think IMEX is higher priority than PC. I'll update the original comment to actually list the things we want here :) |
Feature request:
memcpy
type operations. @nilsdeppe doesn't have anything specific in mind here.Component:
Desired feature:
Detailed discussion:
One issue resolved by these improvements is #4399 .
The text was updated successfully, but these errors were encountered: