Protein mapping aided by the use of a separate conserved domain database. More sensitive than Blastp.

Blastp compares protein queries to protein databases.

App Creator

Roger Barthelson

Quick Start

Test Data


Test data for this app appears directly in the Discovery Environment in the Data window under Community Data -> iplantcollaborative -> example_data -> blastp.

Input File(s)

Use BAtestpep.fa (query ) and refseq_protein (database) from the directory above as test input.

Parameters Used in App

When the app is run in the Discovery Environment, use the following parameters with the above input file(s) to get the output provided in the next section below.

Use the Default parameters with the Test data.

Output File(s)

For the test case, the output file you will find in the example_data directory is named Blasttestoutput.txt

General use with the "Create BLAST Database" tool:

The Blastp app takes a folder as input for the database because there are multiple files involved. The best thing to do when you are creating a database is to give the database and the output file the same name e.g. "mygenome". Then after it has run, make a new folder inside the output directory, name it "mygenome", and drag all the database files into it, but not the logs directory. You can then drag that directory "mygenome" to one of your other directories so it will be easy to find. When you run Blastp, drag and drop the database directory you created into the database input for Blastp.

Tool Source for App

Related Tutorials

BLAST a Transcriptome (Workflow Tutorial)