-
Notifications
You must be signed in to change notification settings - Fork 56
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
Clarification of purpose #117
Comments
Thanks for the question. In working on #116 I added a speedier alternative to the Having a separate package seems like it will cause more confusion. Once the |
Great to hear your'e working on that! Sorry for the constant feature requests ;) I found that normal args are faster than keyword args, so having a wrapper with keywords and an internal function where all atol etc are normal args is a good solution. The setup cost on this secant is basically non-existent, maybe a good target:
|
Worth to test on 0.7 where the implementation of keyword args have been overhauled. |
Anyone did that testing at any point? |
It would be good to have a clear idea of the intended use cases for this package.
The solvers are great and fast for large problems run from the REPL. But running
find_zero()
a million times a second doesn't seem to be a good idea at the moment. Unfortunately that's the most common use case in my field. The setup costs can be larger than the total runtime cost, and can't always be cached, like when running inside a solver that is swapping between Dual numbers and normal numbers, for example.A tiny, basic secant or zbrent solver with normal args is much faster for these situations, and I keep ending up back there - with my own custom roots package to maintain! It may be that such a separate SimpleRoots package is actually a good idea to divide up this space, and would have a small maintenance footprint anyway.
Any thoughts on that?
The text was updated successfully, but these errors were encountered: