mass matrix I for DynamicalODEFunction #536
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
You know how sometimes you later think that some idea was a really really bad idea? Yes, this was one of them. "It's a pair of ODEs, so it's a pair of mass matrices!". Yeah, but that breaks all implicit solver fallbacks, and even when implicit methods specialized to second order ODEs exist, mass_matrix=I will still work as the special case to catch, so it's just better...
Anyways, it didn't matter until last week when ArrayPartition suddenly became compatible with all implicit solvers, except for the fact that it would fail because the mass matrix was by default a tuple. So, let's fix this and yay, 2nd order ODEs are now better.
Fixes #536