-
Notifications
You must be signed in to change notification settings - Fork 23
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
Bug: v0.2.0 Deepbinner bin - "readclass not found" #11
Comments
This is referring to the issue reported here rrwick#11. I encountered this error myself and made this quick fix to get the program to finish. @rwick Might be good to incorporate a fix since it currently dies rather suddenly. I haven't figured out yet why the reads (I've got 587 out of 2.4 mil) are not being classified in the first place (the couple that I blasted seem like real data). If I figure it out I'll report in a separate "non classified reads" issue about this.
Any chance this pull request will be merged anytime soon? I have a large run (380GB of fast5) where I'm not done calling bases, but I want to take the (120GB) of fastq files I have base called already and debarcode them. It's throwing the |
jrherr i dont know if this is a suitable solution for you, but: In case you need a docker container, i have just added the above line to mine. Its on Docker Hub: https://hub.docker.com/r/ttubb/deepbinner/dockerfile (currently waiting on Docker Hub to build the updated version, should be done in a few hours). |
Thanks @ttubb! I needed a couple of days to implement, but this worked like a charm! I did exactly as you said, merged the hotfix, and reinstalled deepbinner using |
I am running deepbinner bin on already basecalled minion data.
The tool throws a KeyError("not found"), if an unclassified read id is encountered.
Data:
Flow-Cells: FLO-MIN106
Kit: SQK-RBK004
Classification was generated per run with:
Binning with:
For some runs the classification omits one read and this prompts the bin.py to switch into a previously untested or disabled section of code.
Maybe I just have an old version of the code.
enable_not_found_bin_patch.txt
The text was updated successfully, but these errors were encountered: