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

query range/culling limit #34

Open
bradfordcondon opened this issue May 1, 2018 · 0 comments
Open

query range/culling limit #34

bradfordcondon opened this issue May 1, 2018 · 0 comments
Labels
Community - Feature Request For any issues describing new functionality that users/admin would like added to the module.

Comments

@bradfordcondon
Copy link
Member

This advanced option was removed ( see PR #33), but we might want it back some day.
For example:



  /*eksc: remove this as it is either the same as max_target_seqs, or miss-implemented
         as culling_limit, which is something else entirely
    $form['ALG']['GParam']['qRange'] = array(
      '#type' => 'textfield',
      '#title' => t('Max matches in a query range'),
      '#default_value' => $defaults['qRange'],
      '#size' => 12,
      '#maxlength' => 20,
      '#description' => t('Limit the number of matches to a query range. This option is useful if many strong matches to one part of a query may prevent BLAST from presenting weaker matches to another part of the query.'),
    );
  */

Its available as an advanced option on ncbi's blast instance as follows:

screen shot 2018-05-01 at 1 36 19 pm

@laceysanderson laceysanderson added the Community - Feature Request For any issues describing new functionality that users/admin would like added to the module. label Nov 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Community - Feature Request For any issues describing new functionality that users/admin would like added to the module.
Projects
None yet
Development

No branches or pull requests

2 participants