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

Confirm that use of BLAST's -max_target_seqs is intentional #6

Closed
armish opened this issue Sep 29, 2018 · 1 comment
Closed

Confirm that use of BLAST's -max_target_seqs is intentional #6

armish opened this issue Sep 29, 2018 · 1 comment

Comments

@armish
Copy link

armish commented Sep 29, 2018

Hi there,

This is a semi-automated message from a fellow bioinformatician. Through a GitHub search, I found that the following source files make use of BLAST's -max_target_seqs parameter:

Based on the recently published report, Misunderstood parameter of NCBI BLAST impacts the correctness of bioinformatics workflows, there is a strong chance that this parameter is misused in your repository.

If the use of this parameter was intentional, please feel free to ignore and close this issue but I would highly recommend to add a comment to your source code to notify others about this use case. If this is a duplicate issue, please accept my apologies for the redundancy as this simple automation is not smart enough to identify such issues.

Thank you!
-- Arman (armish/blast-patrol)

@dnasko
Copy link
Owner

dnasko commented Oct 1, 2018

The following text has been added to each script's help menu:

NOTE the default max_target_seqs is set to 50. Users should update                                               
this value to >= the number of sequences in the subject database if they want to guarentee                                                     
they get the best hit.

@dnasko dnasko closed this as completed Oct 1, 2018
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