You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The estimation of the density of the null distribution (necessary for calculating the pathway $p$-values) depends on the number of pathways considered. While this is probably fine for 30+ pathways, the quality of this density estimate will be degraded for very small pathway sets (less than 15?).
We should add in a new function that permutes the response for each pathway, and treats that permuted pathway as a new pathway, to "fill out" the number of pathways. I don't know how many times we should do this, but I guess 100 at least.
The text was updated successfully, but these errors were encountered:
Create 5 copies of each pathway, with a parametric bootstrap response, to help creating the null distribution. How do we properly adjust for FDR when we would have 15-20 original pathways, but now 5 x 20 more noise pathways? We should only adjust the original $p$-values, and ignore the $p$-values from these new null (parametric bootstrap) pathways.
Until we fix this, add a warning to the superPCA_pVals() function to the user to avoid using pathway collections with fewer than 30 pathways.
lxw391
changed the title
Supervised PCA null density estimation issue
Supervised PCA function - null density estimation for small number of pathways
Nov 25, 2018
The estimation of the density of the null distribution (necessary for calculating the pathway$p$ -values) depends on the number of pathways considered. While this is probably fine for 30+ pathways, the quality of this density estimate will be degraded for very small pathway sets (less than 15?).
We should add in a new function that permutes the response for each pathway, and treats that permuted pathway as a new pathway, to "fill out" the number of pathways. I don't know how many times we should do this, but I guess 100 at least.
The text was updated successfully, but these errors were encountered: