Using Trinity for DGE - how to input study design
0
1
Entering edit mode
4.3 years ago

I'm using trinity to perform a denovo transcriptome assembly to identify deferentially expressed genes between different treatment AND cut types (different sites of injury). I was wondering if there was a way to input the design so the expression levels are compared to the respective controls

Alternatively, I've been trying to export the gene count matrix produced by trinity so I could conduct the analysis in R instead of command line but have been unsuccessful. I'm not sure if there is a way to do this maybe?

Thanks in advance!

trinityrnaseq trinity denovo assembly • 1.3k views
ADD COMMENT
4
Entering edit mode

Trinity provides wrapper scripts to automate DGE analysis, see Differential Expression Analysis Using a Trinity Assembly. The wrapper scripts will create the R code on the fly, you can then open this code and modify the DGE analysis scripts to suit your needs.

ADD REPLY
0
Entering edit mode

Trinity does de novo RNAseq assembly. I don't think you can do DE analysis with Trinity. How are you getting the gene expression results from Trinity-assembled data? Are there de novo DE tools out there?

ADD REPLY
0
Entering edit mode

I guess that your controls will be a non-injured specimens from different treatments. This question doesn't seem very relevant to the Trinity de-novo assembler, instead this inform the strategy of downstream analysis and potentially the construction of a combined reference which is built from the libraries of all (or a subset) of samples. Do you have multiple phenotypes involved or are all specimens clonal?

Once you reach the step of performing DE analyses (after assembly/filtering/mapping/expr_estimates) you can perform a multivariate DE analysis. This is an option for DESeq2 and likely other packages.

ADD REPLY

Login before adding your answer.

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