-
Notifications
You must be signed in to change notification settings - Fork 5
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
Missing information for --diamond-path
#8
Comments
The 'classification' feature of ViPER generates a Krona chart that's based on a diamond blastx alignment with a database that contains sequences with an accession number from NCBI. Krona will, based on the accessions of the best 25 hits, get the lowest common ancestor and display this in a pie chart. In our lab we currently use NCBI's nr database formatted for I hope this answers your questions? I will update the documentation to make this more clear for other users. However, if you are looking to reliably identify (novel) viruses, particularly phages, I recommend using the contig output from ViPER and running it through genomad. |
I see. Thanks a lot for your answer. It's very clear now. |
The ViPER pipeline seems to offer a classification feature, which is essential in making sense of any viral data. However it is not clear how to use this feature.
The documentation says that one should add the path to a diamond database after
--diamond-path
. Yes, but which database or what kind? Are we supposed to come up with our own collection of taxonomically annotated sequences? What did you use in your research? Any suggestions? Ideally, a default should be provided and should auto-download on the first run to create a smoother user experience.Currently, I'm not sure how you intend for users to use "ViPER" with no classification database bundled?
The text was updated successfully, but these errors were encountered: