How to make a RNA-seq pipeline universal?
0
0
Entering edit mode
8.0 years ago
Sinji ★ 3.2k

So i've been working on an RNA-seq pipeline that makes it easier for my lab members to run their own analysis even though they aren't very tech savvy. While the pipeline works great for our lab since we only work on human samples, it doesn't transfer over very well to other labs using different models such as mouse, rat, or drosophila.

My question is ... how do you write the DGE portion of an RNA-seq script and make it applicable to any organism?

Currently, my pipeline will take in a GTF and create a TxDb object from that, which seems to solve ... some of my problems and just opens up new ones (how to convert from differently annotated gene names into more conventional names .. eg. ensembl to symbols). It also makes automated gene ontology analysis extremely difficult because I can never predict what kind of data is being fed into the script.

Any suggestions?

RNA-Seq • 1.5k views
ADD COMMENT
0
Entering edit mode

For our premade pipelines, we dictate the genomes that are available. Then we can ensure that things like GO annotation have a chance at working. Adding more genomes just means a few lines in a config file, so it's not exactly difficult.

ADD REPLY
0
Entering edit mode

This was my original plan, but this brings up another issue. Do you also dictate the annotations that can be used? Ensembl vs UCSC vs Gencode etc.

ADD REPLY
1
Entering edit mode

Yes, we/I dictate the annotations that are available. I manage the available packages/indices/annotations for the institute, so I get to play benevolent dictator :) This ends up cutting down on people doing silly things like mixing/matching chromosome naming conventions and organisms.

ADD REPLY
0
Entering edit mode

I may just have to start leaning towards doing something similar.

Thanks Devon!

ADD REPLY

Login before adding your answer.

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