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

Online version and downloadable software package for offline use (source code in PERL) freely available at http://bat.ina.certh.gr/tools/circoletto/

Contact:ndarz@certh.gr

Address of the bookmark: http://tools.bat.infspire.org/circoletto/

https://github.com/IGS/twinblast

https://mra.asm.org/content/8/35/e00842-19

Address of the bookmark: https://github.com/IGS/twinblast

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

unzip blatSrc35.zip

to unpack the archive. This gives a directory blatSrc now move into that directory.

#cd blatSrc

before you begin read the README file that comes with the source code.

One thing about building blat is that you need to set the MACHTYPE variable so that the BLAT sources know what type of machine you are compiling the software on.

on most *nix machines, typing

echo $MACHTYPE

will return the machine architecture type.

On my CentOS 6 based system this gave:

x86_64-redhat-linux-gnu

However, what BLAT requires is the 'short value' (ie the first part of the MACHTYPE). To correct this, in the bash shell type (change this to the correct MACHTYPE for your system)

MACHTYPE=x86_64
export MACHTYPE

now running the command:

echo $MACHTYPE

should give the correct short form of the MACHTYPE:

x86_64

now create the directory lib/$MACHTYPE in the source tree. ie:

mkdir lib/$MACHTYPE

For my machine, lib/x86_64 already existed, so I did not have to do this, but this is not the case for all architectures.

The BLAT code assumes that you are compiling BLAT as a non-privileged (ie non-root) user. As a result, you must create the directory for the executables to go into:

mkdir ~/bin/$MACHTYPE

If you are installing as a normal user, edit your .bashrc to add the following (change the x86_64 to be your MACHTYPE):

export PATH=~/bin/x86_64::$PATH

For me, though, this was not good enough. I wanted the executables in /usr/local/bin where all my other code goes. As a result I did some hackery...

There is a master make template in the inc directory called common.mk and I edited this file with the command:

vi inc/common.mk

I replaced the line

    BINDIR=${HOME}/bin/${MACHTYPE}

with

    BINDIR=/usr/local/bin

saved and quit (as this is in my path, I do not need to do anything else)

All the preparation is now done and you can create the blat executables by going into the toplevel of the blat source tree (for me it was /usr/local/src/blat/blatSrc, but change to wherever you unpacked blat into).

Now simply run the command:

make

to compile the code.

Blat installed cleanly and the executables were all neatly placed in /usr/local/bin/x86_64, just like I wanted.

now simply running the command:

blat

on the command line gives me information on blat and sample usage.

Blat is installed and it's installed properly in my system code tree!!!

Massimiliano Orsini and Simone Carcangiu develope a new and fast fast package "BlaSTorage" to parse and store BLAST results. BlaSTorage shows comparable speed of more basic parser written in compiled languages as C++ and can be easily integrated into web applications or software pipelines.

Find more @ http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3571973/

http://biowiki.crs4.it/biowiki/MassimilianoOrsini

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/