-
Notifications
You must be signed in to change notification settings - Fork 1
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
[Known problem with BLAST module]500+ results gives no output in blast #199
Comments
Also, if there are 500 + results, why not just skim the top 20 and return those? |
Sequences are below to troubleshoot. Meg has verified setting a reasonable e value should not give 500+ results.
we're talking about the bottom sequence, |
Created an issue in the module to resolve tripal/tripal_blast#25 I think the ideal behavior is obvious: display the first 500 results. (realistically the first 50 results...) |
Secondary issue with #203 Setting the max number of hits to 250 instead of 50 puts you somewhere between. at 500, the module cuts users off. at 50, theres no problem. at 250, the module allows the request to run, and i believe the server runs out of memory, ie, we experience the problem that Lacey put in the failsafe to prevent in tripal/tripal_blast#12. Solutionstemporary
Long term
|
hard coded solution: default:
options: remove 250, 500 + Done on dev, testing |
changes made live as well. What I should do is change the admin form to accept an array of choices... |
The user experienced an error that there were 500 + results. Even tightening the evalue gave this error: i suspect that it is not a blast issue but a bug in the module.
The text was updated successfully, but these errors were encountered: