-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MIRDEEP2:MIRDEEP2_RUN failed #221
Comments
Can you share more information, e.g. logfiles of MIRDEEP2 ? |
HI @mianlee - we need more details to be able to address this issue. I cannot reproduce at the moment using the testdata. Ideally, please share the details for the failing step, e.g. |
Hi, I have run into the similar problem. 3 of my 48 samples failed on MIRDEEP2_RUN with the same message.
|
I have the same issue that part of my samples fail with |
Without a small(!) sharable dataset (and exact miRDeep2 command) that reproduces the error even @Drmirdeep will have a hard time troubleshooting this. Also please note that even though you see the same error message (i.e. 'symptoms'), the underlying cause might be different. |
I unmilestoned this as this requires further data to support finding a potential cause of the issue. Fully agree with what @mschilli87 said - if you could/can share a small dataset that can be used to track down the issue, please share :) |
I had the same problem, No precursors excised This is my code miRDeep2.pl reads_collapsed.fa Oryza_sativa.fa reads_collapsed_vs_genome.arf osa_mature.fa osa_hairpin.fa none -t osa -g -1 2>report.log How do you solve it? Thank you very much |
This comment was marked as duplicate.
This comment was marked as duplicate.
Just wanted to see if it worked out. Wanted to ask
花开再会
***@***.***
…------------------ 原始邮件 ------------------
发件人: "nf-core/smrnaseq" ***@***.***>;
发送时间: 2023年12月8日(星期五) 晚上6:06
***@***.***>;
***@***.******@***.***>;
主题: Re: [nf-core/smrnaseq] MIRDEEP2:MIRDEEP2_RUN failed (Issue #221)
@TOCEAN-ops: Did you even read the comments here before commenting yourself? Nothing changed since August: Without being able to reproduce the issue, there won't be a way to help. 🤷
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Should work in dev |
Ok. 0 reads mapped. Why is anyone surprised here that no precursors were excised? The tool cannot be more verbose. But maybe it should directly abort in this case 🤷🏼♂️ |
Description of the bug
Dear authors:
The pipeline works fine except for Mirdeep2. It shows MIRDEEP2:MIRDEEP2_RUN failed. I checked all my files and parameters, but I can't solve this issue. Do you what can cause this error? Thank you so much!
Command used and terminal output
Relevant files
No response
System information
CentOS 7 linux
HPC
The text was updated successfully, but these errors were encountered: