For each input sequence the following is shown (see the example below):
- Header line, quoting the name and length of the sequence.
- Sequence, in one-letter code, as it was interpreted by the server.
- Annotation overview, showing the predictions residue by residue,
as follows:
| . (dot) |
neutral place-holder |
| _ (underscore) |
predicted signal peptide |
| S,T |
predicted O-glycosylation sites |
- Prediction score table, quoting the scores for each S and
T residue in the sequence.
The G-score is the score from the best general predictor; the I-score
is the score from the best isolated site predictor.
If the G-score is >0.5 the residue is predicted as glycosylated;
the higher the score the more confident the prediction.
For threonines an additional score is used: if the G-score
is <0.5 but the I-score >0.5 and there are no predicted
neighbouring sites (distance <10 residues) the residue is also
predicted as glycosylated.
If a residue in a predicted signal peptide is predicted as glycosylated
there is a warning in the comment field.
- Graphs, in GIF and PostScript, illustrating the
predictions.
For each S and T the prediction score is plotted against
the position in the sequence.
The example below shows the output for
rhamnogalacturonan
acetylesterase precursor (EC 3.1.1.-), taken from the
Swiss-Prot
entry
RHA1_ASPAC.
The signal peptide prediction is consistent with the database annotation.
Two O-glycosylation sites are predicted, both threonine. One (pos. 3) is
within the signal peptide and should be ignored.
If the signal peptide check is enabled and no signal peptide is predicted
a warning is printed at the top of the output for that sequence (not shown
here).