# MiRDeep2 identification of novel and known miRNAs

**URL:** <https://help.galaxyproject.org/t/mirdeep2-identification-of-novel-and-known-mirnas/2036>\
**Category:** usegalaxy.eu support\
**Tags:** custom-genome, mirna, tool-help, rbc\_mirdeep2\
**Created:** [September 3, 2019, 3:55pm UTC](https://help.galaxyproject.org/t/mirdeep2-identification-of-novel-and-known-mirnas/2036 "2019-09-03T15:55:44Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![jennaj](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/jennaj/32/27_2.png) [@jennaj](https://help.galaxyproject.org/u/jennaj)\
**Post date:** [September 13, 2019, 7:35pm UTC](https://help.galaxyproject.org/t/mirdeep2-identification-of-novel-and-known-mirnas/2036/17 "2019-09-13T19:35:37Z")

</div>

I’m not sure, but it certainly couldn’t hurt to remove the description line content from all fasta inputs. With any tool/workflow when working in Galaxy, and usually line command as well.

The error you are getting is from the underlying 3rd party tool, not some error trapping/format checks from the Galaxy wrapper around it. Meaning, you would hit these same format issues no matter where/how you use this tool.

---

_[View the full topic](https://help.galaxyproject.org/t/mirdeep2-identification-of-novel-and-known-mirnas/2036)._