Wondering if DESeq2 is appropriate for PhIP-seq data?
1
0
Entering edit mode
Samantha • 0
@3e3c6676
Last seen 10 months ago
Singapore

Hi there,

I'm currently using DESeq to analyse PhIP-seq data, but I'm not sure if this approach is appropriate for my analysis.

Superficially, the data looks like what comes out of bulk RNA-seq. I'd align the reads using bowtie and then I'd get a counts table with columns of different samples and rows of different peptide epitopes. Samples usually include 8 or more negatives (no antibody) and other samples (in duplicate). We're interesting in comparing each of the other samples individually against the negative samples to find peptides enriched for in each sample, which I believe is a bit different from typical differential expression analyses that compare two groups (control vs mutant/drug). Also, we are interested only in "up-regulation" since we are looking specifically for enrichment.

We've also tried some PhIP-specific pipelines but we faced some issues with implementation and the plots weren't so convincing.

Would appreciate input and feedback if DESeq is appropriate for PhIP-seq data and if there may be conditions/drawbacks that I should take note of.

Thank you so much!

DESeq2 PhIP-seq • 472 views
ADD COMMENT
1
Entering edit mode
@mikelove
Last seen 9 hours ago
United States

Seems reasonable, if the data is paired you can use a paired design in DESeq2.

ADD COMMENT
0
Entering edit mode

Thanks a lot for the reply! But the data isn't quite paired in the sense where there are two differentially treated groups with similar sample sizes.

Instead, we have: 1) 8 x control samples (beads-only) 2) Something like 30 different experimental conditions (in duplicates)

So we would be comparing condition A vs control, condition B vs control, etcetc (30 times). Would this still be considered a paired design, and ok to analyse with DESeq2?

ADD REPLY

Login before adding your answer.

Traffic: 849 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