Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Improve the mechanism that choses a numerical integration algorithm #351
Currently, if no integration algorithm is chosen, the list of state updaters is tried one after the other until a suitable updater is found. There are several issues with the current system:
We still want to keep the system simple and extensible but maybe something where we don't just order algorithms in a list but instead store some information about their accuracy (and assuming that this is inversely related to their run time)? The user could then chose between a "performance-first" or an "accuracy-first" strategy.
We discussed this a while ago and agreed that the best approach for now is a very simple one: each class that takes a method keyword argument (e.g.