RNAseq high padj value from validated samples?
2
0
Entering edit mode
DJ_Han • 0
@1521af40
Last seen 13 months ago
United States

I ran DESeq2 with KO and WT samples(triplicated from each) and found high padj value for KO gene. The target gene KO was validated in many different ways i.e. gPCR, RT-qPCR, and even WB. The p-value for the KO gene is 0.003, but the p.adj value is > 0.05 (0.123). In this case, how can I set up the threshold? I wonder its really a reliable result or not.

DESeq2 • 660 views
ADD COMMENT
1
Entering edit mode
@mikelove
Last seen 5 hours ago
United States

Sounds like the RNA-seq counts didn't support the gene-focused validation. This can happen with low sample size or low counts.

ADD COMMENT
0
Entering edit mode

Thank you for the answer, Michael. Do you think the significantly low KO gene count number can affect the weight during normalization? If so, can I expect better contrast if I remove the target gene's raw count number from both WT and KO samples before running DESeq? Many thank you in advance!

ADD REPLY
0
Entering edit mode

No you wouldn't remove the target gene ever.

What is the sequencing depth per sample (roughly) and what are the counts for this gene?

ADD REPLY
0
Entering edit mode

Thank you for the reply. Here is the raw count numbers. WT(971, 899, 713) vs KO(493, 655, 567). Actually, We expected complete zero count number in KO samples. Exon 2-4 region was targeted (bi-allelic) in KO cell line. Prob. the numbers from different isotype. I have no idea. If I remember correctly, it was 30x.

ADD REPLY
1
Entering edit mode
swbarnes2 ★ 1.3k
@swbarnes2-14086
Last seen 1 day ago
San Diego

This doesn't sound like a DESeq2 problem. It sounds like the RNA-seq is not showing what you expect. Why did you not show the raw counts for this gene as assessed by RSEM or FeatureCounts or whatever?

ADD COMMENT

Login before adding your answer.

Traffic: 453 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6