allow mismatch in miRDeep2
Entering edit mode
20 months ago

I used mirDeep2 for my analysis with the following command lines:

Method 1:

  1. (without option q) trimmed_data.fq -e -h -i -j -m -p bta.fa -s reads_collapsed.fa -t reads_vs_refdb.arf -v

  2. reads_collapsed.fa bta.fa reads_vs_refdb.arf mature_ref_bta.fa mature_other.fa hairpin_ref_bta.fa -t bta 2>report.log

Later I wanted to loosen my criteria to allow mismatches. I added option q when running and used the outputs, reads_collapsed_mismatches_allowed.fa and reads_vs_refdb_mismatches_allowed.arf, as inputs for without changing any other parameters for

Method 2: 1. (with option q to allow mismatches) trimmed_data.fq -e -h -i -j -m -p bta.fa -q -s reads_collapsed_mismatches_allowed.fa -t reads_vs_refdb_mismatches_allowed.arf -v

  1. (same as the first run) reads_collapsed_mismatches_allowed.fa bta.fa reads_vs_refdb_mismatches_allowed.arf mature_ref_bta.fa mature_other.fa hairpin_ref_bta.fa -t bta 2>report.log

The number of reads mapped to reference genome bta.fa increased when option q was included. However, the results from module are EXACTLY the same. I have tried these methods for different datasets and still see the same things: output from were different but output from were the same even though the module was run differenlt. Please help me with the following questions:

  1. Why I allow mismatches with q option), but the results after were the same?
  2. What can I do to allow mismatches in the miRNAs search?


miRDeep2 mismatch • 378 views

Login before adding your answer.

Traffic: 1487 users visited in the last hour
Help About
Access RSS

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6