Closed Yuzhang0102 closed 1 year ago
IIRC, miRDeep2.pl
calls (potentially novel) miRNA(-precursor)s from reads mapped to the genome, whereas quantifier.pl
maps reads to (annotated) miRNAs (trading specificity for sensitivity). I hope this answers your first question. Regarding your second and third question, I am not sure I get what you are asking. Maybe @Drmirdeep can provide a better answer.
Please have a look at the publication and the tools help regarding the options used by quantifier.pl and mirdeep2.pl
Thanks for your replies! I have looked at the options of quantifier.pl many times, but I don't know how to avoid this condition, or it can't be avoid?
Hi, I firstly merged and collapsed my all fastq data of all samples to predict novel miRNAs by miRDeep2.pl. Then I used the output precursor and mature fasta to run quantifier.pl for each sample. But I got two reads counts of some miRNA in the results.
quantifier.pl -p novel_pres_07_04_2023_t_15_26_33_score-50_to_na.fa -m novel_mature_07_04_2023_t_15_26_33_score-50_to_na.fa -r sample1.fa -d
I checked these miRNAs found that the precursor have two locations of mature miRNA sequence, like this: But the mature miRNA structure is this: So my questions are