-
Notifications
You must be signed in to change notification settings - Fork 6
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
KeyError: 'Bacteria' #38
Comments
I will look into this error. Would be great if you could send me the problematic bin fastas for that if possible, though ( I can provide an upload link for that soon, as soon as a current problem on our fileserver has been solved). Until then a temporary workaround may be to use the --fast_run argument here als, as already suggested for #37 (preferrably only for the problematic bins though). |
I re-ran MDMcleaner for this bin set omitting the bin that seemed to have caused the error in the previous run. However, I received the same error message for the last bin to be run. Maybe the error message is related to a step in the program that is run after the individual processing of the bins? The bin_name_filtered_*.gz files are written for all bins and the error list file is empty. However, despite the potential reference DB contamination that was detected during the run (according the log file) no new_blacklist_additions.tsv is being produced. I am now re-running the complete bin set with the --fast_run option. That worked without a problem. I find it curious, though, that I only received the |
for some reeason i could not reproduce this particular error for the test bins provided. But i added a temporary fix for the related "silva_conflict" problem. please Contact me if this keyerror still persists with the new mdmcleaner version and database... |
Hi @jvollme , I am very sorry that it took me so long to get back to you. I updated MDMcleaner to the latest version and all my previous issues were resolved. Thank you so much. Everything seems to have worked fine. However, I get the following error message at the end of the run:
I assume that this is just related to post-run cleaning steps and not affecting the results for the individual bins? Thanks! Cheers, |
Hi,
I have been running MDMcleaner on 2 different bin sets. In one run, not all bins were processed without error (see #37). Using the same reference data, I am now getting the following error for the last bin to be processed:
Any advice would be appreciated. Thanks!
The text was updated successfully, but these errors were encountered: