Closed ramiromagno closed 6 years ago
See the discussion here: https://github.com/StoreyLab/qvalue/commit/f534759bdc462d672744a29230017c9a346021fa#commitcomment-26274105 ... We are discussing internally the best way to handle this. The package is not designed to handle truncated p-value distributions but can easily be extended. We hope to have a solution soon!
Cheers, Andrew
Thanks for the quick reply!
I didn't realise you were already aware of this issue. Nice!
In the meantime you could maybe add a check for truncated p-value distributions... because having that error from smooth.spline
surfacing is a bit unexpected... particularly when using other packages that have qvalue
as dependency.
Is there any update on this issue? Also: how can I check the truncated p-value distributions, I mean practically/code-wise in a script and without drawing a picture?
What I am doing to circumvent this is to use qvalue(p, lambda = seq(0, max(p), 0.05))
. But I am not sure whether it is OK to do so.
If I recall, it seemed like nearly every test was statistically significant. In this case I would be conservative and simply force pi0 = 1
: qvalue(p, pi0 = 1)
... This is also known as the BH procedure from the function p.adjust
.
I get this error:
while running the
qvalue
function:but not with:
This relates to
pi0
estimation (in the fnpi0est
) and howlambda
is defined. If there is not a pvalue beyond the last value (default:0.95
) in the vectorlambda
,qvalue
will give the error abovementioned.Should not line
106
frompi0est.R
:read instead:
?