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

Command line options #777

Open
saassli21 opened this issue Jan 9, 2024 · 1 comment
Open

Command line options #777

saassli21 opened this issue Jan 9, 2024 · 1 comment

Comments

@saassli21
Copy link

I blastp on my data and it's really much faster than I exprected.
i used some filters based on the documentation in "Wiki" section ( https://github.com/bbuchfink/diamond/wiki/3.-Command-line-options ) in order to decrease my dataset but I can't do the link between the option and header of my output file :

" ./diamond blastp --min-score 500 --evalue 0.0001 --query-cover 90 --approx-id 70 -d /lab/saassli/blast/db_swissprot/swissprot -q /lab/saassli/blast/input.fa --header -o /lab/saassli/blast/output_swissprot/matches_filter_evalue.tsv "

for example I know that for --evalue I must survey the e-value column in my output file
--min-score it's bit-score column in my output file

but for --approx-id and --query-cover I don't know which column I should survey and how they are calculated
Thanks,
Saassli,

@bbuchfink
Copy link
Owner

These columns are not reported by default, you can see them by changing the format e.g. -f 6 qcovhsp approx_pident.

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

No branches or pull requests

2 participants