Help with STAR & stringTie pipeline
1
0
Entering edit mode
4 months ago
Mike ▴ 10

Hey all, I'm new to this :)

I have about 8 SRR reads of some organism.

It will be great if you could help me determining the best course of action for me.

I took 2 reads as an example, cleaned them with Trim Galore, then ran STAR for indexing and aligning the reads to a reference genome. Then used samtools for sorting and more indexing. After that I used stringTie on the sorted bam file for the assembly and got a GTF file.

My question is what is the best way to approach this in regards to multiple reads? If I have 8 reads (or more), should I use STAR on each pair and then merge the bam's with samtools merge and use stringTie once or should I create an GTF file for each pair and merge them with stringTie --merge?

Also, is there anything i should do or add between the steps I mentioned?

The goal is to to create a gene annotation pipeline.

If you have any information regarding this I'll be happy to hear it!

stringTie samtools GTF bam • 425 views
ADD COMMENT
0
Entering edit mode

Hey Mike, I followed the same pipeline as you. Trimgalore to trim and filter, STAR to map. How did you implement StringTie on the Aligned.sortedByCoord.out.bam? I'm looking for some exact code...

Best,

Todd

ADD REPLY
0
Entering edit mode

Hi Todd, first I sorted using samtools:

samtools sort bam_input -o output_sorted.bam

Then:

if you don't have a reference file-

stringtie input -o output.gtf

if you have a reference file-

stringtie input -o -G reference.gtf output.gtf

then I merged all outputs with-

stringtie --merge -o merged.gtf gtfs

ADD REPLY
2
Entering edit mode
4 months ago

I recommend assembling each one separately with stringTie and then running stringTie merge on the result. This way you won't assemble things containing junctions that never appear in the same sample together.

ADD COMMENT

Login before adding your answer.

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