Is removing rRNAs, tRNAs, etc really a necessary step in the miRNA analysis?
2
0
Entering edit mode
3.6 years ago
tianshenbio ▴ 180

I have some small RNA seq data to analyze miRNAs. I trimmed the adaptors, selected reads of 18-25 nt, mapped the reads to the genome, detected novel and conserved miRNAs using mirdeep2. I’ve already done DE analysis and target predictions. However, I realized that I did not remove rRBAs, tRNAs, mRNAs, and other types of ncRNAs. I know I can filter them out using the Rfam and NCBI database. But is it really a necessary step to filter them out? It will take me a long time to do these analysis.

mirdeep2 miRNA RNA-seq • 1.9k views
ADD COMMENT
0
Entering edit mode

Dear sir, I also would like to remove rRNAs, tRNAs, mRNAs, and other types of ncRNAs using Rfam. I have no idea about it. can you please share some links related to this?.

Thanks KAMALAKKANNAN R

ADD REPLY
1
Entering edit mode

Do you want to remove these by using a standard identifier (e.g. from Pfam) or based on sequence?

ADD REPLY
0
Entering edit mode

Thanks for your reply sir, I want to go with sequence based one

ADD REPLY
1
Entering edit mode
22 months ago
GenoMax 147k

Rfam sequence files: https://docs.rfam.org/en/latest/ftp-help.html

You could also download the sequences you need for a species from: https://rnacentral.org/

Then it would be a matter of creating indexes and aligning your data.

ADD COMMENT
0
Entering edit mode

Thank you sir

ADD REPLY
1
Entering edit mode
22 months ago
noodle ▴ 590

One approach is to make sure all the 'unwanted' RNAs exist in your reference genome and then exclude these from any downstream analysis. If you're aligning to human you might want to try the T2T genome as you might have better luck discovering novel miRNAs in this genome.

ADD COMMENT
0
Entering edit mode

Thank you sir

ADD REPLY

Login before adding your answer.

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