If you have any questions or comments, post them on one of the trackers on BRIG’s SourceForge page: http://sourceforge.net/tracker/?group_id=328245.

Features:

• Images show similarity between a central reference sequence and other sequences as concentric rings.
• BRIG will perform all BLAST comparisons and file parsing automatically via a simple GUI.
• Contig boundaries and read coverage can be displayed for draft genomes; customized graphs and annotations can be displayed.
• Using a user-defined set of genes as input, BRIG can display gene presence, absence, truncation or sequence variation in a set of complete genomes, draft genomes or even raw, unassembled sequence data.
• BRIG also accepts SAM-formatted read-mapping files enabling genomic regions present in unassembled sequence data from multiple samples to be compared simultaneously

Address of the bookmark: http://brig.sourceforge.net/

As with most programs that run on UNIX, the text output is in some specific format. If the program is popular enough, there will be one or more parsers written for that format – these are just utilities written to help you retrieve whatever information you are interested in from the output.

Let’s conclude this tutorial by converting the BLAST output in out.txt into a spreadsheet format, using a Python script. 

First, we need to get the script. We’ll do that using the ‘git’ program:

git clone https://github.com/ngs-docs/ngs-scripts.git /root/ngs-scripts

We’ll discuss ‘git’ more later; for now, just think of it as a way to get ahold of a particular set of files. In this case, we’ve placed the files in /root/ngs-scripts/, and you’re looking to run the script blast/blast-to-csv.py using Python:

python /root/ngs-scripts/blast/blast-to-csv.py out.txt

This outputs a spread-sheet like list of names and e-values. To save this to a file, do:

python /root/ngs-scripts/blast/blast-to-csv.py out.txt > ~out.csv

If you have Excel installed, try double clicking on it.

Here is a list of what is changing:

1. All databases at the root level will be dbV5.
2. The dbV5 file naming,  “_v5” will be removed. Databases with  no “_vX” descriptor will be dbV5.
3. dbV4 tarballs will be renamed with "_v4", files included in tarball will not be renamed.
4. dbV4 databases will be moved to a v4 subdirectory.
5. As of 1/13/20 the Cloud directory will be frozen with no more new entries.
6. The will be no more updates to dbV4 databases.
7. The FASTA directory will contain nr, nt, swissprot, and pdbaa files.

If you have any questions or concerns, please contact blast-help@ncbi.nlm.nih.gov

1. ElasticBLAST can handle much LARGER queries! 

ElasticBLAST can search query sets that have hundreds to millions of sequences and against BLAST databases of all sizes.

2. ElasticBLAST is FASTER

ElasticBLAST distributes your searches across multiple cloud instances to process them simultaneously. The ability to scale resources in this way allows you to process large numbers of queries in a shorter time than you could with BLAST+.

3. ElasticBLAST is EASY to run on the cloud

ElasticBLAST is easy to set up using our step-by-step instructions (Amazon Web Services (AWS), Google Cloud Platform (GCP)) and allows you to leverage the power of the cloud. Once configured, it manages the software and database installation, handles partitioning of the BLAST workload among the various instances, and deallocates cloud resources when the searches are done.

ElasticBLAST also selects the instance (i.e., machine) type for you based on database size. Of course, you can also choose the instance type manually if you prefer. 

Address of the bookmark: https://blast.ncbi.nlm.nih.gov/doc/elastic-blast/

A fairly complete on-line guide to BLAST searching can be found at the NCBI BLAST Help Manual. For a theoretical overview of BLAST, see the NCBI BLAST Course. Additional information can be found in the BLAST 2.0 Release Notes

Supported and Suggested Values for Gap Open and Extension in BLASTP, BLASTX, TBLASTN, and TBLASTX

Address of the bookmark: https://www.arabidopsis.org/Blast/BLASToptions.jsp

More @ http://www.ncbs.res.in/sowdhamini/groups_sowdhamini.htm

1. Database Enhancements:

   • The BLAST databases have shifted fully to the version 5 (v5) format, which integrates built-in taxonomy information. This allows for more detailed and efficient sequence annotation and analysis.
   • Protein databases in v5 are now accession-based, supporting a broader range of sequences, including those from high-throughput projects and the Pathogen Detection Project. These databases also accommodate structural proteins with multi-character chain identifiers.

2. Performance Improvements:

   • Adaptive Composition-Based Statistics (CBS) is available as an experimental feature, enhancing the detection of novel results in protein-protein comparisons.
   • Updated algorithms improve the stability of search results, especially when fewer hits are requested than the default output.

3. Compatibility:

   • Support for the older v4 databases has been discontinued. The v5 format is now the default for all BLAST database updates, ensuring alignment with current standards in bioinformatics.

4. User-Friendly Changes:

   • Naming conventions for databases have been simplified to enhance clarity and ease of use. For example, database names no longer include version tags like "_v5".

5. Future-Proofing:

   • BLAST+ 5 aligns with current and upcoming data requirements, ensuring that researchers have access to the most comprehensive and modern resources for sequence alignment.

These updates reflect NCBI's commitment to maintaining BLAST as a leading tool for sequence analysis. For detailed release notes and additional guidance, refer to NCBI Insights here

tax_id:
the unique identifier provided by NCBI Taxonomy
for the species or strain/isolate

GeneID:
the unique identifier for a gene
ASN1: geneid

Symbol:
the default symbol for the gene
ASN1: gene->locus

LocusTag:
the LocusTag value
ASN1: gene->locus-tag

Synonyms:
bar-delimited set of unofficial symbols for the gene

dbXrefs:
bar-delimited set of identifiers in other databases
for this gene. The unit of the set is database:value.
Note that HGNC and MGI include 'HGNC' and 'MGI', respectively,
in the value part of their identifier. Consequently,
dbXrefs for these databases will appear like:
HGNC:HGNC:1100
This would be interpreted as database='HGNC', value='HGNC:1100'
Example for MGI:
MGI:MGI:104537
This would be interpreted as database='MGI', value='MGI:104537'

chromosome:
the chromosome on which this gene is placed.
for mitochondrial genomes, the value 'MT' is used.

map location:
the map location for this gene

description:
a descriptive name for this gene

type of gene:
the type assigned to the gene according to the list of options
provided in https://www.ncbi.nlm.nih.gov/IEB/ToolBox/CPP_DOC/lxr/source/src/objects/entrezgene/entrezgene.asn

Symbol from nomenclature authority:
when not '-', indicates that this symbol is from a
a nomenclature authority

Full name from nomenclature authority:
when not '-', indicates that this full name is from a
a nomenclature authority

Nomenclature status:
when not '-', indicates the status of the name from the
nomenclature authority (O for official, I for interim)

Other designations:
pipe-delimited set of some alternate descriptions that
have been assigned to a GeneID
'-' indicates none is being reported.

Modification date:
the last date a gene record was updated, in YYYYMMDD format

Feature type:
pipe-delimited set of annotated features and their classes or
controlled vocabularies, displayed as feature_type:feature_class
or feature_type:controlled_vocabulary, when appropriate; derived
from select feature annotations on RefSeq(s) associated with the
GeneID

Address of the bookmark: ftp://ftp.ncbi.nih.gov/gene/DATA/GENE_INFO/

More @ http://www.nature.com/news/pubmed-opens-for-comment-1.14023

News source Nature.