-
Notifications
You must be signed in to change notification settings - Fork 12
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
Help~ Python bug #24
Comments
For this error, it seems like your system lacks that shared library. You need to ask the administrator where it is and add it into his $PATH. You can try: 1. Reinstall blca, make sure all packages and dependencies are installed correctly. 2. Ask administrator to install or provide access to libargtable2.so.0. Then add its path to $PATH (or copy it to $PATH). |
@qunfengdong Thank your for your reply. I have fixed this bug after adding the lib PATH. |
We are not sure what you meant by "wrong label type in taxonomy files". Could you please give us an example? Thanks! |
d: domain - domain bacteria |
d:domain, p: phylum, c: class, o:order, f: family, g: genus, Did you use NCBI 16S database? |
If you can send us your query sequence and describe the database you used, we'd like to reproduce your error msg. Please send it to qunfengd@gmail.com. Thanks! |
@qunfengdong Oh really? thank you for your paying attention. It's my own 16S database. According to your instruction, Trainning your own database, I have to modify my tag to a rigid format. So, I suggest that multiple symbols can be used in the label setting. You only need to specify clear symbols that represent the segmentation information. In addition, other symbols can be used in the label to facilitate the expansion of database functions. I will send a part of my query sequence and describe files to your Email. Thanks again. |
I see. You were using your own 16S database. Unfortunately, you will have to stick to those format (we built BLCA using NCBI taxonomic database format). |
Thanks for all those reports. If you can email me (qunfengd@gmail.com) your query sequence as well as your own 16S database, we'd like to use them to test our procedure. |
The text was updated successfully, but these errors were encountered: