-
Notifications
You must be signed in to change notification settings - Fork 18
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
mikdo pick throws this error and results in very few transcripts #415
Comments
Dear @aseetharam , Many thanks for your bug report. This does look like an incompatibility between Mikado and the current version of networx. To confirm this is the case, the best way would be to downgrade the library to the minimum required version ( @ljyanesm might be able to have a look at it. Kind regards |
Thanks, @lucventurini, for the quick response! I rebuild the container with the recommended
Thanks! |
Dear @aseetharam Thank you for checking. Then my other hypothesis is that you might have ORFs without an ID in your dataset. May I ask how you produced the ORFs (including the version of the program) and a snippet of the ORF file you used, please? |
Hi @lucventurini: |
Okay, just wanted to update you. I tried the gff3 file from Transdecoder (orfs) as well as new orfs generated using prodigal, but neither of them worked (same error). If you would like me to try anything, please don't hesitate! Thanks, |
Dear @aseetharam, Would it be possible for you to make a minimal example (maybe just extracting one of the failing loci) and share that with us? |
No need @ljyanesm , this happened right now on my machine using the sample data :-/ Something has broken somewhere. |
@aseetharam FYI this means we do have a confirmation on the bug, fixing it ASAP. |
@ljyanesm the problem is in This breaks Mikado downstream as that field would be used for ordering the ORFs. Setting it as a bug. |
@ljyanesm @lucventurini, thanks! Looking forward for the fix! |
Dear @aseetharam, The original issue you've posted was fixed with the commit referenced here. There are a couple of other issues we are currently working on, as soon as these are resolved I will merge and tag a new release. Thank you for reporting the issue, and your patience. Luis |
Dear @aseetharam , The new version of Mikado (2.3.1) that we just released contains the fix for this issue. It also contains many other bug fixes and general improvements that should make Mikado much faster for dense loci. The new version is already present in PyPI and should be uploaded to Conda soon. We are closing the issue for now, but please feel free to reopen it if you encounter any issue. Kind regards, |
Hello,
I've been running Mikado on a number of plant genomes and recently upgraded it to the latest version. I'm using the Singulairty image (v2.3.0, centos) and all the steps until pick (configure, prepare, serialise), completed successfully.
mikado pick
was run as follows:and the
pick.log
hasthis error is repeated numerous times, ending with:
I'm stumped. Can you please help me fix this error? I think I can rule out any installation error. Since this is happening on all 11 genomes I've been running, you can also probably rule out problematic data. Any help will be greatly appreciated!
Thanks,
I'm editing to add more info:
and the final results:
This doesn't seem right.
The text was updated successfully, but these errors were encountered: