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

[BUG] padj=nan when pvalue is not nan #355

Closed
ggg5438 opened this issue Jan 10, 2025 · 1 comment
Closed

[BUG] padj=nan when pvalue is not nan #355

ggg5438 opened this issue Jan 10, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@ggg5438
Copy link

ggg5438 commented Jan 10, 2025

Hello,
Thank you for your package. It helps me a lot. (especially I don"t want to use R)

I found that some padj values are nan when corresponding p-values are not nan.
Among 12,308 genes, 1,223 padj values are nan, even though all foldchange values are not nan and only 43 raw p-values are nan.

I have two questions:

  1. Why some raw p-values have nan values even when their fc and stat values are not nan?
  2. Why padj values have nan values when raw p-values are not nan?
@ggg5438 ggg5438 added the bug Something isn't working label Jan 10, 2025
@BorisMuzellec
Copy link
Collaborator

Hi @ggg5438, thank you for your interest in our package.

This is not a bug.

  1. Unadjusted. p-values may be set to nan when a gene contains an extreme outlier value. The adjusted p-value for this gene will be in turn set to nan. This can be controlled by setting cooks_filter to True or False in DeseqStats.
  2. A padj may be set to nan even though its unadjusted counterpart is not nan due to independent filtering (independent_filter in in DeseqStats).

See also the DESeq2 vignette on this topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants