-
Notifications
You must be signed in to change notification settings - Fork 80
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
IndexError: list index out of range #104
Comments
I'm still running into this error for QUAST v5.0.2. I did some troubleshooting, and the problem was the *.bed file that was being parsed by the
Upon re-running metaquast, the same .bed file was always re-used instead of re-created, so the IndexError kept happening. I don't see any option to force overwrite the .bed file. It would be helpful to either include an option for force-overwrite of the .bed file, or to include an exception in the
|
Hello Nick @nick-youngblut! Just a few things to discuss before we implement the final fix:
|
The user could always manually delete existing output, if it exists. That is what I have now implemented in my pipeline. I think that it would just be helpful to have an error message that tells the user that pre-existing output might be the cause of the error.
Sounds great! I better error message could also work: something that just says how pre-existing output files might be the cause of the error. |
Hi there! I got the "IndexError: list index out of range" error when running metaQUAST with my assembled contigs, scaffolds, and a sorted, indexed BAM file. I tried running with the same parameters while excluding the BAM file, and I didn't have any errors. Any idea why this is? I can attach the logs if necessary! |
Hi @hlfreund ! |
Hi, thanks for getting back to me! Here is the log files for one of the assembled metagenomes I checked with metaQUAST. Thank you for your help! |
Hi @hlfreund, |
The error
The entire log is attached: metaquast.log
My conda env
The text was updated successfully, but these errors were encountered: