What to use as Close-species for miRDeep2
0
0
Entering edit mode
7.1 years ago
GBC_Zonatos ▴ 10

I'm currently trying to run miRDeep2 in order to find, extract and count miRNAs from a miRNA sequencing experiment, but I'm having trouble determining which species to use as 'close/related species'.

My main question is: how many species should I use as 'close/related species'? Would using a big number of close species be better for the final output, or worse? And how closely related should the species be to my reference?

I'm working with sequences from Bos indicus, using the genome and miRNA from Bos taurus as reference, and when asking other people in the lab, I've got completely opposite directions and pipelines, which ended up being very misleading.

  1. Use only one species as 'close species', using Homo sapiens, as it's a "very well studied species".
  2. Use more species, in order to have more sequences and find more miRNAs, using Equus caballus, Mus musculus, Homo sapiens, Sus scrofa and the sequences from Bos taurus itself as close species (5 species).
  3. Use more closely related species, in this case, Ovis aries and Capra hircus, both ruminants.

The first two came from people who already worked (or are working on) similar analysis as my own, although I'm pretty sure using the same species as both reference AND close species would be wrong, even if the data we have is from Bos indicus, not Bos taurus.

The idea of using either Ovis aries or Capra hircus as reference seems appealing to me, as they are more closely related to Bos taurus than the other mentioned ones.

At the moment, I'm considering running it with Ovis aries, Capra hircus and Homo sapiens, but I'm still unsure about how closely related species should be, and how many I should use.

miRDeep2 close species miRNA related species • 1.7k views
ADD COMMENT
1
Entering edit mode

I have the same problem...any ideas?

ADD REPLY

Login before adding your answer.

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