Cufflinks input- reference information
1
0
Entering edit mode
8.3 years ago
Lindsay44 ▴ 20

I am looking for novel genes in two different experimental groups ( differential expression analysis).

When do I include the following information in my command?

Cufflinks- reference annotation (GTF)

Cuffmerge- reference annotation (GTF) and reference sequence (Fasta)

Cuffdiff- reference GTF

Thanks for the help.

RNA-Seq cufflinks • 2.1k views
ADD COMMENT
0
Entering edit mode
8.3 years ago
Satyajeet Khare ★ 1.6k

Reference GTF in tophat, cufflinks, cuffmerge and merged.gtf in cuffdiff will differentiate novel genes from known and therefore need to be included if you want known as well as novel genes. But if you want only novel genes, then you can align reads to Genome outside of the reference GTF file and then perform cufflinks and cuffmerge without reference GTF and cuffdiff with merged.gtf.

ADD COMMENT
0
Entering edit mode

Is it necessary to include the gene annotation in Hisat2 (I am not using Tophat) in addition to the indexed reference genome? What are the pros of doing this?

ADD REPLY
0
Entering edit mode

In tophat, it helped me avoid generation of multiple XLOC ids for single gene id. So I use GTF for tophat. But this happens rarely and only a handful of genes get multiple XLOC ids. I dont see any disadvantage. Dont know about HISAT2. But if HISAT2 allows reference GTF, I will use it.

ADD REPLY
0
Entering edit mode

Okay, thank you. What is the benefit of including the reference GTF in Cuffdiff as well?

ADD REPLY
0
Entering edit mode

GTF file is essential for cuffdiff as it will act as a template to quantitate transcripts in GTF file using aligned reads from bam file.

ADD REPLY
0
Entering edit mode

can it be the merged gtf created from cuffmerge or does the reference have to be included as well?

ADD REPLY
0
Entering edit mode

Use either merged.gtf or reference GTF, not both.

ADD REPLY

Login before adding your answer.

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