Skip to content
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

--global-ranking, impact and when to set lower? #814

Open
fpusan opened this issue Jun 17, 2024 · 1 comment
Open

--global-ranking, impact and when to set lower? #814

fpusan opened this issue Jun 17, 2024 · 1 comment
Labels

Comments

@fpusan
Copy link

fpusan commented Jun 17, 2024

Hi and thanks for the continued development and maintenance of DIAMOND.

I'm interested in speeding up searches against NCBI nr. Ideally I would like to get only the top 10-20 hits, even if they are not very good.

I've seen here that I can use the --fast mode, which afaik is optimized for hits with >90% identity. I have also seen you mention that -g100 can speed things up if you only need the best hits for each query. I didn't fully undertood what it did exactly, or whether it came with a lower sensitivity against low identity hits.

Could you elaborate a bit on when to set -g lower than the default and the expected consecuences of doing so?

Thanks in advance

@bbuchfink
Copy link
Owner

-g N enables global ranking which means only the best N targets will be extended for each query, ranked on their ungapped extension score. This can be much faster than the default behaviour for large databases, but it is also greedy and relevant hits can easily be missed. For your application is certainly seems to make sense using it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants