24
Parsing BLAST output

Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

Embed Size (px)

Citation preview

Page 1: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

Parsing BLAST output

Page 2: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

Output of a local BLAST search

“less” program

Full path to the BLAST output file

Page 3: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

BLAST program used for the search

Reference

Information of the query sequence

One-line summary of the search results

Detailed information for the first 2 hsps of the first hit:Accession number, description, organism, score, E value, identities, positives, and alignment

Information of the database

Page 4: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

Sample BLAST output (continued)

Hsp information from the first hit

Page 5: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

Press “q” to quit the “less” viewing mode

Page 6: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

The size of the BLAST output is limited only by the free disk space you have in your computer. It’s virtually impossible to open a large text file. Let alone going through the file line by line.

The purpose of parsing BLAST output is to extract user-defined information from the BLAST output file for clear visualization and summarization.

Page 7: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

Search result parsing

The Bio::SearchIO system was designed for parsing sequence database searches (BLAST, sim4, waba, FASTA, HMMER, exonerate, etc.)

Page 8: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

One-line summary of the search results

Load Bio::SearchIO moduleUsage informationIt will appear if the program is invoked without arguments

Define the class

Print out the header information

Process each result

Page 9: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

Process each hit

Process each HSP

Control for the number of hits to be extracted

Indicator showing the work is done

Page 10: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

Change directory (cd) to where the perl script and the BLAST output file are stored

Confirm that the perl script and the BLAST output are in place

Page 11: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

Oops… an error message

It’s due to Windows and Unix compatibility.

Page 12: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

Find the file in Windows system and open it with Notepad++

Page 13: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

Select “convert to UNIX format” in the “Format” drop-down menu

After the conversion, save the file and exit Notepad++

Page 14: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

Another error message

This is because the perl interpreter has been installed in another location (/usr/bin/) while the script is looking for the perl interpreter in /usr/local/bin

Page 15: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

Solution:Create a symbolic link of /usr/bin/perl in /usr/local/bin

Command:ln<space>-s<space>/usr/bin/perl<space>/usr/local/bin/perl

Now it’s working !

Page 16: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

Congratulation! You’ve just parsed a BLAST output!

This is the file you’ve just generated.

Page 17: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

Let’s see how the file looks like, using “less”.

Page 18: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

Here is how it looks like.

The parsed output is tab-delimited and can be imported into Excel for better visualization.

Page 19: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file
Page 20: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

Locate the file in Windows system

Page 21: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file
Page 22: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file
Page 23: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file
Page 24: Parsing BLAST output. Output of a local BLAST search “less” program Full path to the BLAST output file

Accession numbers of the top 3 hits

Descriptions of the top 3 hits

E values of the top 3 hits

Information of each HSP of the top 3 hits

Header row

Query sequence