Introduce absstep to specify the stepsize to use close to zero #55
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.
and rename epsilon_factor to relstep. Since we just introduced the
epsilon_factor
argument, I haven't deprecated it.Setting the step size around zero can be important in applications and indeed I'm working on a project where the current default isn't a good choice.
The current version of this PR should have almost unchanged behavior for the current uses of the library. However, we might want to consider using a smaller absolute step size. This is effectively what https://cran.r-project.org/web/packages/numDeriv/numDeriv.pdf does and this can also be motivated by computing derivatives of
log
andabs2
around zero, seeWhere "new" uses the square of the relative step size for the absolute step size. However, Pareto improvements only exist in books so some functions can lose on such a change.
though I'm not sure if new error is really worrying.