Improve numerical precision of several p-value calculations #1210
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.
Hi there,
This is relatively minor but I was looking at the source code for an unrelated reason and I noticed that in several places you have used the sub-optimal approach to calculating p-values.
You have coded
1 - ...
instead of using thelower.tail = FALSE
argument of the distribution functions. The1 - ...
calculation loses numerical precision.Below are some examples which show this - admittedly you only see this with very large values of a z/t/X^2/F statistic, but it is probably worth using the more precise calculation. For example, for a z-test the
1 - ...
calculation reports0
for approx. abs(Z) > 8.3 , whereas thelower.tail = FALSE
calculation will give you a p-value up to abs(Z) approx 37.5 (which is approxabs(qnorm(.Machine$double.xmin / 2))
).Created on 2024-07-22 with reprex v2.1.1
Also,
abs()
around thestatistic
stats::
qualifier in a few places.Tom