On Monday 28th March 2011 the WSBlastpgp service was decommissioned and replaced by the following services:

• PSI-BLAST (REST)
• PSI-BLAST (SOAP)

The service documentation and clients below are historical and provided solely for reference purposes.

Position Specific Iterative BLAST (PSI-BLAST) performs an iterative sequence similarity search which can detect more distant evolutionary relationships.

Pattern Hit Initiated BLAST (PHI-BLAST) treats multiple occurrences of a defined pattern within the query sequence as independent sequences.

These tools are only available for database protein searches.

The iterative strategy of PSI-BLAST can be run in two ways:

1. Manual: at each iteration the list of hits found is returned and the hits used to generate the profile the next iteration are selected and submitted to perform the nest iteration.
2. Automatic: the set of hits used to construct the profile is automatically selected based on an E-value threshold. For this mode the search will stop either when the iterations converge (i.e. the same hits are used to build the profile in each iteration) or when a specified maximum number of iterations is reached.

This service provides only the automatic mode. To use the manual mode see the WSPSIBlast, PSI-BLAST (SOAP) or PSI-BLAST (REST) services.

For more information on this tool see:

• EBI Tools:
  • PSI-BLAST/PHI-BLAST
  • PSI-BLAST/PHI-BLAST Help
• NCBI:
  • NCBI BLAST Help
  • BLAST Guide
• BioCatalogue

Sample clients are provided for a number of programming languages. For details of how to use these clients, download the client and run the program without any arguments.

For further details see PSI-BLAST/PHI-BLAST Clients.

WSDL service description:

http://www.ebi.ac.uk/Tools/webservices/wsdl/WSBlastpgp.wsdl

Submits a PSI-BLAST/PHI-BLAST job to the service.

Arguments:

• params an instance of the inputParams data structure.
• content a list of data data structures describing the query sequence data.

Returns: a string containing the job ID (jobid).

Get the entry IDs of the hits in the BLAST output.

Arguments:

• jobid the job identifier specifying the job to get the IDs from.

Returns: a string array of entry IDs.

Get the status of a job.

Arguments:

• jobid the job identifier of the job to check status of.

Returns: a string indicating the status of the job. Current values are:

• DONE: job has finished, and the results can then be retrieved.
• ERROR: the job failed or no results where found
• NOT_FOUND: the job id is no longer available (job results are deleted after 24 h)
• PENDING: the job is in a queue waiting processing
• RUNNING: the job is currently being processed

Get details of the result types available.

Arguments:

• jobid the job identifier of the job to get result types for.

Returns: an array of WSFile structures describing the available result types for the job.

Wait until the job has finished and get the specified type of result data.

Arguments:

• jobid the job identifier of the job to get result from.
• type a string specifying the type of result to retrieve. See getResults(jobid) and WSFile for details of how to obtain valid values.

Returns: a base64 encoded string containing the result data. Depending on the SOAP library and programming language used the result may be returned in decoded form.

Structure containing the input data for the job

For example to specify an input sequence in Java:

Data inSeq = new Data();
inSeq.setType = "sequence";
inSeq.setContent = ">TestSequence\nASAMPLESEQ\n";

A structure containing the parameters required to run the job.

Structure describing a result type. Returned by the getResults(jobid) method.

If you have any questions or comments, or you plan to use this service as part of a course or for a high number of submissions, please contact us EBI Support.