Skip to content
2000
Volume 17, Issue 1
  • ISSN: 0929-8665
  • E-ISSN: 1875-5305

Abstract

A series of elegant phosphorylation site prediction methods have been developed, which are playing an increasingly important role in accelerating the experimental characterization of phosphorylation sites in phosphoproteins. In this study, we selected six recently published methods (DISPHOS, NetPhosK, PPSP, KinasePhos, Scansite and PredPhospho) to evaluate their performance. First, we compiled three testing datasets containing experimentally verified phosphorylation sites for mammalian, Arabidopsis and rice proteins. Then, we present the prediction performance of the tested methods on these three independent datasets. Rather than quantitatively ranking the performance of these methods, we focused on providing an understanding of the overall performance of the predictors. Based on this evaluation, we found the following results: i) current phosphorylation site predictors are not effective for practical use and there is substantial need to improve phosphorylation site prediction; ii) current predictors perform poorly when used to predict phosphorylation sites in plant phosphoproteins, suggesting that a rice-specific predictor will be required to obtain confident computational annotation of phosphorylation sites in rice proteomics research; and iii) the tested predictors are complementary to some extent, implying that establishment of a meta-server might be a promising approach to developing an improved prediction system.

Loading

Article metrics loading...

/content/journals/ppl/10.2174/092986610789909412
2010-01-01
2025-07-09
Loading full text...

Full text loading...

/content/journals/ppl/10.2174/092986610789909412
Loading

  • Article Type:
    Research Article
Keyword(s): Evaluation; Phosphorylation site; Prediction; Protein
This is a required field
Please enter a valid email address
Approval was a Success
Invalid data
An Error Occurred
Approval was partially successful, following selected items could not be processed due to error
Please enter a valid_number test