BLAST Search main parameters
- Display a histogram of scores for each search; default
is yes. (See parameter H in the BLAST Manual).
- Restricts the number of short descriptions of matching
sequences reported to the number specified; default
limit is 100 descriptions. (See parameter V in the
manual page). See also EXPECT and CUTOFF.
- Restricts database sequences to the number specified for
which high-scoring segment pairs (HSPs) are reported;
the default limit is 50. If more database sequences
than this happen to satisfy the statistical
significance threshold for reporting (see EXPECT and
CUTOFF below), only the matches ascribed the greatest
statistical significance are reported.
(See parameter B in the BLAST Manual).
The statistical significance threshold for reporting
matches against database sequences; the default value
is 10, such that 10 matches are expected to be found
merely by chance, according to the stochastic model
of Karlin and Altschul (1990). If the statistical
significance ascribed to a match is greater than the
EXPECT threshold, the match will not be reported.
Lower EXPECT thresholds are more stringent, leading
to fewer chance matches being reported. Fractional
values are acceptable. (See parameter E in the BLAST
Cutoff score for reporting high-scoring segment pairs.
The default value is calculated from the EXPECT value
(see above). HSPs are reported for a database sequence
only if the statistical significance ascribed to them
is at least as high as would be ascribed to a lone
HSP having a score equal to the CUTOFF value. Higher
CUTOFF values are more stringent, leading to fewer
chance matches being reported. (See parameter S in
the BLAST Manual). Typically, significance thresholds
can be more intuitively managed using EXPECT.
Specify an alternate scoring matrix for BLASTP, BLASTX,
TBLASTN and TBLASTX. The default matrix is BLOSUM62
(Henikoff & Henikoff, 1992). The valid alternative
choices include: PAM40, PAM120, PAM250 and IDENTITY.
No alternate scoring matrices are available for BLASTN;
specifying the MATRIX directive in BLASTN requests
returns an error response.
Restrict a TBLASTN search to just the top or bottom
strand of the database sequences; or restrict a BLASTN,
BLASTX or TBLASTX search to just reading frames on the
top or bottom strand of the query sequence.
Mask off segments of the query sequence that have
low compositional complexity, as determined by the
SEG program of Wootton & Federhen (Computers and
Chemistry, 1993), or segments consisting of
short-periodicity internal repeats, as determined
by the XNU program of Claverie & States (Computers
and Chemistry, 1993), or, for BLASTN, by the DUST
program of Tatusov and Lipman (in preparation).
Filtering can eliminate statistically significant but
biologically uninteresting reports from the blast
output (e.g., hits against common acidic-, basic- or
proline-rich regions), leaving the more biologically
interesting regions of the query sequence available
for specific matching against database sequences.
Filtering is only applied to the query sequence (or
its translation products), not to database sequences.
Default filtering is DUST for BLASTN, SEG for other
It is not unusual for nothing at all to be masked
by SEG, XNU, or both, when applied to sequences
in SWISS-PROT, so filtering should not be expected to
always yield an effect. Furthermore, in some cases,
sequences are masked in their entirety, indicating that
the statistical significance of any matches reported
against the unfiltered query sequence should be suspect.
Causes NCBI gi identifiers to be shown in the output,
in addition to the accession and/or locus name.
- parsed HTML output
The parsed html output provides us various HTML tags to facilitate the navigation within the BLAST output and to easily retrieve more informations about the sequences in the hit table. The retrieval will be, dependently on the database where the sequences come from, taken out by using SRS 4.0, SRS 5.0 at EMBL, or Entrez of NCBI. Finally, there is a graphical overview about the matched regions of the query sequence in regards to locally-aligned HSPs from database sequences. Here is an example for the parsed BLAST output.