Skip to content

exporting large numbers of hit sequences creates too long a command-line #751

@yannickwurm

Description

@yannickwurm

Using -entry when you have tens of thousands of hits can lead the export process to crash.

We should refactor

command = "blastdbcmd -outfmt '%g %i %a %t %s'" \
by writing identifiers to a file and using -entry_batch instead.

*** Retrieval options
 -entry <String>
   Comma-delimited search string(s) of sequence identifiers:
   	e.g.: 555, AC147927, 'gnl|dbname|tag', or 'all' to select all
   	sequences in the database
    * Incompatible with:  entry_batch, ipg, ipg_batch, info, metadata,
   tax_info, taxids, taxidlist, no_taxid_expansion, list, recursive,
   remove_redundant_dbs, list_outfmt, show_blastdb_search_path
 -entry_batch <File_In>
   Input file for batch processing (Format: one entry per line, seq id 
   followed by optional space-delimited specifier(s)
   [range|strand|mask_algo_id]
    * Incompatible with:  entry, range, strand, mask_sequence_with, ipg,
   ipg_batch, info, metadata, tax_info, taxids, taxidlist, no_taxid_expansion,
   list, recursive, remove_redundant_dbs, list_outfmt,
   show_blastdb_search_path

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions