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

Support for -culling_limit #95

Open
nathanweeks opened this issue Sep 18, 2017 · 3 comments
Open

Support for -culling_limit #95

nathanweeks opened this issue Sep 18, 2017 · 3 comments

Comments

@nathanweeks
Copy link

nathanweeks commented Sep 18, 2017

The -culling_limit option is occasionally useful for filtering, and can reduce run time as well. It would be helpful if this were supported by Galaxy BLAST+.

@peterjc
Copy link
Owner

peterjc commented Sep 18, 2017

If you want to work on a pull request, that'd be great.

It looks like it can't be combined with -best_hit_overhang or -best_hit_score_edge, which would complicate trying to offer those as well and enforcing this in the Galaxy GUI. But if you think the culling limit is more useful, we could prioritise adding that?

@nathanweeks
Copy link
Author

I can look into submitting a pull request---hopefully before someone wants -best_hit_overhang or -best_hit_score_edge! I'll hold off on starting this until galaxy_blast incorporates BLAST 2.7.1+, which fixes a -culling_limit bug I had reported to NCBI.

@peterjc
Copy link
Owner

peterjc commented Oct 27, 2017

Cross reference #93

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