A list of one or more UniProt primary accession numbers. A pair of strings giving (1) the name of a predictor and (2) the status of that predictor with regard to a recently completed query. Status can be COMPLETE (finished with no errors), TIMEOUT (request to predictor timed out), WORKING (query is currently in progress, optionally followed by a string describing the progress so far), or ERROR followed by a string describing the error itself. A jobID and the email address that was used when submitting the job. Both must be supplied when requesting the status or results of a job, or cancelling a job. A 4-tuple containing the score results for a single pair of proteins. The query protein. The reference protein. A numeric score produced by running the p-values produced by the individual predictors through Fisher's Unweighted Method. A p-value representing the probability that any two randomly- chosen proteins in this proteome would be given an rs score equal to or higher than the rs for this pair, by the same process. A 4-tuple containing the score results for a single protein against the whole reference set. The query protein. A numeric score reflecting how closely related this protein is to the biological function embodied by the reference set. A p-value representing the probability that any randomly- chosen protein in this proteome would be given an rs score equal to or higher than the rs for this one, by the same process. A list of scores and p-values for a pair of proteins across a number of predictors, along with an overall score and p-value. The query protein. The reference protein. A numeric score reflecting how closely related these two protein are, according to one specific predictor. A p-value representing the probability that any randomly- chosen protein in this proteome would be given an rs score equal to or higher than the rs for this one, by the same predictor. A numeric score produced by running the p-values produced by the individual predictors through Fisher's Unweighted Method. A p-value representing the probability that any two randomly- chosen proteins in this proteome would be given an f-rs score equal to or higher than the rs for this pair, by the same process. Use SubmitTwoProteinSets to request a comparison of two sets of proteins. You must supply an email address in order to retrieve the results later. If enableEmailNotify is set to true, you will receive an email notifying you when the job has completed. Otherwise you will need to keep calling the MonitorJob operation. NB Your email address will be logged and used to contact you in case of any problems, changes to the service etc. We will not pass it on to any third parties. After submitting a job you will immediately receive a unique, randomly-generated jobID. You will need to supply this (along with your email address) in order to monitor, cancel or retrieve the results of a job. Use MonitorJob to check on the status of a job you've submitted, by supplying the jobID and your email address. The status code can be COMPLETE (job finished with no errors), WORKING (job is currently in progress, optionally followed by a string describing the progress so far), CANCELLED (cancelled by user using CancelJob), FAILURE (job failed to start, followed by a string describing the details of the error), EXPIRED (the job was cleaned off the server after a pre-defined period of time had elapsed since completion -- 24 hours?) or UNKNOWN (an unrecognized jobID was supplied). NB A COMPLETE job is not necessarily error-free; this just means that all predictors have finished executing, successfully or not. Use one of the Retrieve operations to get the individual results by predictor. Use CancelJob to completely abort a job you've submitted, by supplying the jobID and your email address. All temporary files etc. on the server will be deleted, and no results will be obtainable for this job. The status code can only be CANCELLED (if the job aborted cleanly) or ERROR followed by a string describing the error itself (if an error occurred during the cancellation process). Use RetrievePairwiseScores to retrieve the results of a job you've submitted, in the form of a list of query protein/reference protein score pairs. You must supply both the jobID and your email address. The output of RetrievePairwiseScores contains a human-readable comments field (remember to inspect this, or log it, in case it contains important information), a list of predictor status codes, and a list of scores. If this is called before the job is complete, the list of scores will be empty. Use RetrieveSetwiseScores to retrieve the results of a job you've submitted, in the form of a score for each query protein vs. the reference set. You must supply both the jobID and your email address. The output of RetrieveSetwiseScores contains a human-readable comments field (remember to inspect this, or log it, in case it contains important information), a list of predictor status codes, and a list of scores. If this is called before the job is complete, the list of scores will be empty. Use RetrieveCompleteScores to retrieve the results of a job you've submitted, in the form of a complete score profile for each query protein/reference protein pair across all the predictors, along with an overall score for each pair. The output of RetrieveCompleteScores contains a human-readable comments field (remember to inspect this, or log it, in case it contains important information), a list of predictors and status codes, and a list of score profiles. The scores in the score profile occur in the same order as the predictors in the status list. If this is called before the job is complete, or there was a problem with one or more predictors, the score profiles will be incomplete. Any missing scores (for whatever reason) will be set to null.