Skip to content
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

Multiple Testing Correction in BUSTED vs absREL #1707

Open
NicMAlexandre opened this issue May 13, 2024 · 4 comments
Open

Multiple Testing Correction in BUSTED vs absREL #1707

NicMAlexandre opened this issue May 13, 2024 · 4 comments

Comments

@NicMAlexandre
Copy link

Hi Sergei,

Could you point me to a preferred method and rationale for multiple testing correction using BUSTED and absREL. I am having trouble finding these resources.

@spond
Copy link
Member

spond commented May 14, 2024

Dear @NicMAlexandre,

There really isn’t anything formal that I ever wrote. Your specific application matters quite a bit. Not knowing anything else, I would recommend FDR for BUSTED. aBSREL is a bit more complicated, because it does multiple testing correction at the level of branches for each run. You can layer another correction on top of that if you want, probably another FDR. Can you give me any details?

Best,
Sergei

@NicMAlexandre
Copy link
Author

NicMAlexandre commented May 15, 2024 via email

@spond
Copy link
Member

spond commented May 15, 2024

Dear @NicMAlexandre,

aBSREL already does the within-gene correction for you, so that's not something you need to do after the fact. The number of test branches for BUSTED is immaterial for the purposes of per-gene correction (one gene = one test), only inasmuch as you would expect very low power to reject given a single foreground branch. In other words, you would expect the actual Type I error rate to be much lower than the nominal one (p-value cutoff). Doing a multiple test correction here is probably going to dilute everything out.

Would you happen to have a list of p-values (for the 11k genes) that BUSTED produced that you could share?

Best,
Sergei

@NicMAlexandre
Copy link
Author

Thank you, that makes complete sense. I just direct messaged the P-values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants