SEQanswers

Go Back   SEQanswers > General



Similar Threads
Thread Thread Starter Forum Replies Last Post
DEXSeq with experimental variables adumitri Bioinformatics 2 06-27-2013 06:37 AM

Reply
 
Thread Tools
Old 07-06-2017, 06:57 PM   #1
SuzuBell
Member
 
Location: Iowa

Join Date: Nov 2013
Posts: 12
Default Examining possible extraneous variables in RNA-sequencing data

I have an RNA-sequencing dataset with 48 samples. I have a list of several possible extraneous variable values for each of the 48 samples. Some of these extraneous variables are categorical (lane1 versus lane2, performed on day 1 versus performed on day 2, performed in room 1 versus performed in room 2) and some are quantitative (ng/UL of RNA submitted for RNA-seq, RIN, % values, etc).

The dataset contains two factors (one with 4 levels and one with 2 levels). Hence, there are 8 treatment groups, and there are 6 samples per treatment group. I did all 28 pairwise DEG analyses between the 8 treatment groups using edgeR, DESeq2, and limmaVoom, and all three methods revealed similar and disappointing results. Some treatment pairs had thousands of DEGs, and others had zero DEGs (even if that particular pair should have many in theory).

I am trying to determine if these possible extraneous variables (both categorical and quantitative) may be causing issues. The MDS plots are not too good. Is there a recommended/reliable method for testing and/or accounting for extraneous variables (both categorical and quantitative) in RNA-sequencing DEG analysis? I am most familiar with edgeR, DESeq2, and limmaVoom, but am open to other software.

Thank you for any advice!
SuzuBell is offline   Reply With Quote
Reply

Tags
correlation, deseq2, edger, limma voom

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off




All times are GMT -8. The time now is 02:31 PM.


Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2017, vBulletin Solutions, Inc.
Single Sign On provided by vBSSO