************************************************************************
********** REPORT OF PROTEIN ANALYSIS  by the WHAT IF program **********
************************************************************************

Date : 2024-11-03
This report was created by WHAT IF version WHATCHECK15.0

This document is a WHAT_CHECK 14.0 report for a PDB-file. Each reported
fact has an assigned severity, one of:

error  : Items marked as errors are considered severe problems requiring
         immediate attention.
warning: Either less severe problems or uncommon structural features. These
         still need special attention.
note   : Statistical values, plots, or other verbose results of tests and
         analyses that have been performed.

If alternate conformations are present, only the first is evaluated. Hydrogen
atoms are only included if explicitly requested, and even then they are not
used in all checks. The software functions less well for non-canonical amino
acids and exotic ligands than for the 20 canonical residues and canonical
nucleic acids.

Some remarks regarding the output:

Residues/atoms in tables are normally given in a few parts:

A number. This is the internal sequence number of the residue used by WHAT IF.
    The first residues in the file get number 1, 2, etc.
The residue type. Normally this is a three letter amino acid type.
The sequence number, between brackets. This is the residue number as it was
    given in the input file. It can be followed by the insertion code.
The chain identifier. A single character. If no chain identifier was given in
    the input file, this will be a minus sign or a blank.
A model number. If no model number exists, like in most X-ray files, this will
    be a blank or occasionally a minus sign.
In case an atom is part of the output, the atom will be listed using the PDB
    nomenclature for type and identifier.

To indicate the normality of a score, the score may be expressed as a Z-value
   or Z-score. This is just the number of standard deviations that the score
   deviates from the expected value. A property of Z-values is that the
   root-mean-square of a group of Z-values (the RMS Z-value) is expected to be
   1.0. Z-values above 4.0 and below -4.0 are very uncommon. If a Z-score is
   used in WHAT IF, the accompanying text will explain how the expected value
   and standard deviation were obtained.
The names of nucleic acids are DGUA, DTHY, OCYT, OADE, etc. The first character
   is a D or O for DNA or RNA respectively. This circumvents ambiguities in the
   many old PDB files in which DNA and RNA were both called A, C, G, and T.



=========================================
==== Compound code /zata/tempdir/3d62/wctemp_besttls/3d62_besttls.pd====
=========================================
 
# 1 # Note: Introduction
WHAT CHECK needs to read a PDB file before it can check it. It does a
series of checks upon reading the file. The results of these checks are
reported in this section (section 2.1). The rest of the report will be more
systematic in that section 2.2 reports on administrative problems. Section
2.3 gives descriptive output that is not directly validating things but
more telling you how WHAT CHECK interpreted the input file. Section 2.4
looks at B-factors, occupancies, and the presence/absence of (spurious)
atoms. Section 2.5 deals with nomenclature problems. Section 2.6 deals with
geometric problems like bond lengths and bond angles. Section 2.7 deals with
torsion angle issues. Section 2.8 looks at atomic clashes. Section 2.9 deals
with packing, accessibility, etc, issues. Section 2.10 deals with hydrogen
bonds, ion packing, and other things that can be summarized under the common
name charge-charge interactions. Section 2.11 gives a summary of whole report
and tells you (if applicable) which symmetry matrices were used. Section 2.12
tells the crystallographer which are the things most in need of manual
correction. And the last section, section 2.13, lists all residues sorted
by their need for visual inspection in light of the electron density.
WARNING. Date error on HEADER card:
HEADER                                                        3D62
ATOM  *****  C13 959 A 350      64.342  41.449  42.420  1.00 78.25       C13 C
ATOM  *****  C16 959 A 350      64.548  40.139  41.759  1.00 69.85       C16 C
ATOM  *****  C12 959 A 350      65.559  42.332  42.652  1.00 92.13       C12 C
ATOM  *****  N10 959 A 350      66.461  42.398  41.525  1.00111.98       N10 N
ATOM  *****  C9  959 A 350      66.019  42.627  40.269  1.00 89.67       C9  C
ATOM  *****  O11 959 A 350      64.851  42.655  39.950  1.00 97.89       O11 O
ATOM  *****  O8  959 A 350      67.017  42.925  39.414  1.00 68.82       O8  O
ATOM  *****  C7  959 A 350      68.281  43.415  39.943  1.00 73.50       C7  C
ATOM  *****  C5  959 A 350      69.439  42.881  39.150  1.00 61.65       C5  C
ATOM  *****  C6  959 A 350      69.809  43.473  37.954  1.00 73.67       C6  C
ATOM  *****  C1  959 A 350      70.889  42.986  37.234  1.00 75.67       C1  C
ATOM  *****  C2  959 A 350      71.608  41.912  37.706  1.00 61.78       C2  C
ATOM  *****  C3  959 A 350      71.253  41.319  38.894  1.00 64.86       C3  C
ATOM  *****  C4  959 A 350      70.176  41.806  39.619  1.00 66.36       C4  C
ATOM  *****  O   HOH A 352      64.069  38.174  37.680  1.00 33.95       352 O
ATOM  *****  O   HOH A 353      52.337  19.924  31.209  1.00 32.50       353 O
ATOM  *****  O   HOH A 354      66.254  45.996  42.403  1.00 32.24       354 O
ATOM  *****  O   HOH A 355      45.986   4.734  20.577  1.00 43.92       355 O
ATOM  *****  O   HOH A 356      75.248  24.105  35.338  1.00 53.28       356 O
ATOM  *****  O   HOH A 357      62.119  13.326  39.980  1.00 64.31       357 O
ATOM  *****  O   HOH A 358      74.317  22.694  55.215  1.00 50.03       358 O
ATOM  *****  O   HOH A 359      57.584  35.872  54.624  1.00 44.85       359 O
ATOM  *****  O   HOH A 360      66.801  15.536  46.084  1.00 58.03       360 O
ATOM  *****  O   HOH A 361      70.337  10.026   7.684  1.00 55.09       361 O
ATOM  *****  O   HOH A 362      68.481   8.680  56.427  1.00 59.24       362 O
ATOM  *****  O   HOH A 363      61.219  15.645   5.525  1.00 45.62       363 O
ATOM  *****  O   HOH A 364      72.650  39.029  43.452  1.00 38.40       364 O
ATOM  *****  O   HOH A 365      71.787   7.963  32.318  1.00 41.83       365 O
ATOM  *****  O   HOH A 366      65.655  18.967   7.029  1.00 44.40       366 O
ATOM  *****  O   HOH A 367      76.606  28.443  24.596  1.00 64.33       367 O
ATOM  *****  O   HOH A 368      54.624  12.733   8.378  1.00 45.66       368 O
ATOM  *****  O   HOH A 369      62.192  41.092  51.097  1.00 66.70       369 O
ATOM  *****  O   HOH A 370      76.606  33.731  23.671  1.00 46.73       370 O
ATOM  *****  O   HOH A 371      76.493  32.231  35.702  1.00 65.91       371 O
ATOM  *****  O   HOH A 372      68.255  45.665  43.627  1.00 45.98       372 O
ATOM  *****  O   HOH A 373      58.274  17.915  35.493  1.00 55.51       373 O
ATOM  *****  O   HOH A 374      82.016  36.619  54.288  1.00 46.97       374 O
ATOM  *****  O   HOH A 375      57.053  31.347  56.648  1.00 29.35       375 O
ATOM  *****  O   HOH A 376      55.614  30.894  53.724  1.00 52.11       376 O
ATOM  *****  O   HOH A 377      69.679  49.117  51.905  1.00 42.01       377 O
ATOM  *****  O   HOH A 378      77.334  26.741  19.306  1.00 49.52       378 O
ATOM  *****  O   HOH A 379      58.582  41.195  33.840  1.00 64.22       379 O
ATOM  *****  O   HOH A 380      77.252  17.895  17.957  1.00 41.60       380 O
ATOM  *****  O   HOH A 381      65.459  13.833  44.450  1.00 56.63       381 O
ATOM  *****  O   HOH A 382      55.227  22.777  36.218  1.00 42.78       382 O
ATOM  *****  O   HOH A 383      56.736  15.941  41.377  1.00 72.71       383 O
ATOM  *****  O   HOH A 384      66.987  16.939  38.044  1.00 46.22       384 O
ATOM  *****  O   HOH A 385      64.305  26.264  31.460  1.00 60.93       385 O
ATOM  *****  O   HOH A 386      75.544  30.730  28.527  1.00 34.81       386 O
ATOM  *****  O   HOH A 387      82.846  35.037  49.055  1.00 44.82       387 O
ATOM  *****  O   HOH A 388      53.546  24.235  53.933  1.00 72.17       388 O
ATOM  *****  O   HOH A 389      78.377  37.037  32.080  1.00 49.82       389 O
ATOM  *****  O   HOH A 390      68.831  32.160  67.511  1.00 54.66       390 O
ATOM  *****  O   HOH A 391      58.739  44.423  46.868  1.00 60.73       391 O
ATOM  *****  O   HOH A 392      55.435  43.413  46.210  1.00 38.79       392 O
ATOM  *****  O   HOH A 393      63.851  27.303  41.430  1.00124.34       393 O
ATOM  *****  O   HOH A 394      75.620  48.981  33.304  1.00 48.30       394 O
ATOM  *****  O   HOH A 395      63.356  11.004  39.684  1.00 44.25       395 O
ATOM  *****  O   HOH A 396      56.941  20.648  15.873  1.00 42.60       396 O
ATOM  *****  O   HOH A 397      71.568  15.979   5.009  1.00 59.34       397 O
ATOM  *****  O   HOH A 398      79.574  22.736  36.740  1.00 49.77       398 O
ATOM  *****  O   HOH A 399      75.879  21.260  12.466  1.00 64.59       399 O
ATOM  *****  O   HOH A 400      59.828  30.383  30.131  1.00 30.08       400 O
ATOM  *****  O   HOH A 401      79.179   6.374  35.139  1.00 53.96       401 O
ATOM  *****  O   HOH A 402      54.160  -4.972  12.357  1.00 42.48       402 O
ATOM  *****  O   HOH A 403      74.890  39.946  67.514  1.00 46.70       403 O
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
 
# 2 # Note: Header records from PDB file
Header records from PDB file.
 
HEADER                                                        3D62
 
# 3 # Error: Missing unit cell information
No SCALE matrix is given in the PDB file.
 
# 4 # Note: Proposal for corrected SCALE matrix
A corrected SCALE matrix has been derived.
 
Proposed scale matrix
  0.009375  0.000000  0.000000
  0.000000  0.022143  0.000000
  0.000000  0.000000  0.018530
 
# 5 # Warning: Problem detected upon counting molecules and matrices
The parameter Z as given on the CRYST card represents the molecular
multiplicity in the crystallographic cell. Normally, Z equals the number of
matrices of the space group multiplied by the number of NCS relations. The
value of Z is multiplied by the integrated molecular weight of the molecules
in the file to determine the Matthews coefficient. This relation is being
validated in this option. Be aware that the validation can get confused if
both multiple copies of the molecule are present in the ATOM records and
MTRIX records are present in the header of the PDB file.
 
 Space group as read from CRYST card: P 21 21 2
 Number of matrices in space group: 4
 Highest polymer chain multiplicity in structure: 1
 Highest polymer chain multiplicity according to SEQRES: 1
 No explicit MTRIX NCS matrices found in the input file
 Value of Z as found on the CRYST1 card: 0
 Z, symmetry, and molecular multiplicity disagree
 Could it be that Z must be: 4
 
# 6 # Error: Matthews Coefficient (Vm) very high
 
The Matthews coefficient [REF] is defined as the density of the protein
structure in cubic Angstroms per Dalton. Normal values are between 1.5
(tightly packed, little room for solvent) and 4.0 (loosely packed, much
space for solvent). Some very loosely packed structures can get values a bit
higher than that.
 
Numbers this high are almost always caused by giving the wrong value for Z
on the CRYST1 card (or not giving this number at all).
 
 Molecular weight of all polymer chains: 33167.383
 Volume of the Unit Cell V= 259965.875
 Space group multiplicity: 4
 No NCS symmetry matrices (MTRIX records) found in PDB file
 Matthews coefficient for observed atoms and Z is high: Vm= 7.838
 No Matthews coefficient given in REMARK 280
 Could it be that Z must be: 4
 This number is the multiplication of the spacegroup and NCS symmetry count
 Matthews coefficient for observed atoms and corrected Z: Vm= 1.959
 
# 7 # Note: Z missing on CRYST1 card
The messages above seem likely caused by the fact that Z is missing from the
CRYST1 card.
 
# 8 # Note: All atoms are sufficiently far away from symmetry axes
None of the atoms in the structure is closer than 0.77 Angstrom to a proper
symmetry axis.
 
# 9 # Note: Chain identifiers OK
WHAT CHECK has not detected any serious chain identifier problems. But be
aware that WHAT CHECK doesn't care about the chain identifiers of waters.
 
# 10 # Warning: Ligands for which a topology was generated automatically
The topology for the ligands in the table below were determined
automatically. WHAT CHECK uses a local copy of the CCP4 monomer library to
generate topology information for ligands. Be aware that automatic topology
generation is a complicated task. So, if you get messages that you fail to
understand or that you believe are wrong, and one of these ligands is
involved, then check the ligand topology entry first. This topology is either
present in the monomer library, or as a libcheck-generated file in the local
directory.
 
  301 959  ( 350-) A  -
 
# 11 # Note: Covalently bound ligands
No problems were detected that seem related to covalently bound ligands.
 
# 12 # Note: No strange inter-chain connections detected
No covalent bonds have been detected between molecules with non-identical
chain identifiers.
 
# 13 # Note: No duplicate atom names in ligands
All atom names in ligands (if any) seem adequately unique.
 
# 14 # Note: In all cases the primary alternate atom was used
WHAT CHECK saw no need to make any alternate atom corrections (which means
they either are all correct, or there are none).
 
# 15 # Note: No residues detected inside ligands
Either this structure does not contain ligands with amino acid groups inside
it, or their naming is proper (enough).
 
# 16 # Note: No attached groups interfere with hydrogen bond calculations
It seems there are no sugars, lipids, etc., bound (or very close) to atoms
that otherwise could form hydrogen bonds.
 
# 17 # Note: No probable side chain atoms with zero occupancy detected.
Either there are no side chain atoms with zero occupancy, or the side chain
atoms with zero occupancy were not present in the input PDB file (in which
case they are listed as missing atoms), or their positions are sufficiently
improbable to warrant a zero occupancy.
 
# 18 # Note: No probable backbone atoms with zero occupancy detected.
Either there are no backbone atoms with zero occupancy, or the backbone
atoms with zero occupancy were left out of the input PDB file (in
which case they are listed as missing atoms), or their positions are
sufficiently improbable to warrant a zero occupancy.
 
# 19 # Note: All residues have a complete backbone.
No residues have missing backbone atoms.
 
# 20 # Note: No C-alpha only residues
There are no residues that consist of only an alpha carbon atom.
 
# 21 # Note: Content of the PDB file as interpreted by WHAT CHECK
Content of the PDB file as interpreted by WHAT CHECK.
WHAT CHECK has read your PDB file, and stored it internally in what is called
'the soup'. The content of this soup is listed here. An extensive explanation
of all frequently used WHAT CHECK output formats can be found at
swift.cmbi.ru.nl. Look under output formats. A course on reading this
'Molecules' table is part of the WHAT CHECK website.
 
     1     1 (    3)   299 (  301) A Protein             /zata/tempdir/3d6...
     2   300 (  301)   300 (  301) A S O2 <-   299       /zata/tempdir/3d6...
     3   301 (  350)   301 (  350) A 959                 /zata/tempdir/3d6...
     4   302 ( HOH )   302 ( HOH ) A water   (    1)     /zata/tempdir/3d6...
MODELs skipped upon reading PDB file: 0
X-ray structure. No MODELs found
The total number of amino acids found is 299
of which 4 have poor or (essentially) missing atoms
No nucleic acids observed in input file
No sugars recognized in input file
Number of water molecules: 1
Residue numbers increase monotonously OK
ERROR. File not found:
TAPEOUT.DAT
 
# 22 # Note: Ramachandran plot
In this Ramachandran plot x-signs represent glycines, squares represent
prolines, and plus-signs represent the other residues. If too many
plus-signs fall outside the contoured areas then the molecule is poorly
refined (or worse). Proline can only occur in the narrow region around
phi=-60 that also falls within the other contour islands.
 
In a colour picture, the residues that are part of a helix are shown in blue,
strand residues in red. Preferred regions for helical residues are drawn in
blue, for strand residues in red, and for all other residues in green. A full
explanation of the Ramachandran plot together with a series of examples can
be found at the WHAT CHECK website [REF].
 
In the TeX file, a plot has been inserted here
 
Chain identifier: A
 
# 23 # Note: Secondary structure
This is the secondary structure according to DSSP. Only helix (H), overwound
or 3/10-helix (3), strand (S), turn (T) and coil (blank) are shown [REF].
All DSSP related information can be found at swift.cmbi.ru.nl/gv/dssp/
This is not really a structure validation option, but a very scattered
secondary structure (i.e. many strands of only a few residues length, many
Ts inside helices, etc) tends to indicate a poor structure. A full
explanation of the DSSP secondary structure determination program together
with a series of examples can be found at the WHAT CHECK website [REF].
 
Secondary structure assignment
                     10        20        30        40        50        60
                      |         |         |         |         |         |
    1 -   60 FRKMAFPSGKVEGCMVQVTCGTTTLNGLWLDDTVYCPRHVICTAEDMLNPNYEDLLIRKS
(   3)-(  62)
                     70        80        90       100       110       120
                      |         |         |         |         |         |
   61 -  120 NHSFLVQAGNVQLRVIGHSMQNCLLRLKVDTSNPKTPKYKFVRIQPGQTFSVLACYNGSP
(  63)-( 122)
                    130       140       150       160       170       180
                      |         |         |         |         |         |
  121 -  180 SGVYQCAMRPNHTIKGSFLNGSCGSVGFNIDYDCVSFCYMHHMELPTGVHAGTDLEGKFY
( 123)-( 182)
                    190       200       210       220       230       240
                      |         |         |         |         |         |
  181 -  240 GPFVDRQTAQAAGTDTTITLNVLAWLYAAVINGDRWFLNRFTTTLNDFNLVAMKYNYEPL
( 183)-( 242)
                    250       260       270       280       290
                      |         |         |         |         |
  241 -  299 TQDHVDILGPLSAQTGIAVLDMCAALKELLQNGMNGRTILGSTILEDEFTPFDVVRQCS
( 243)-( 301)
 
 
 
 
# 24 # Note: No rounded coordinates detected
No significant rounding of atom coordinates has been detected.
 
# 25 # Note: No artificial side chains detected
No artificial side-chain positions characterized by chi-1=0.0 or chi-1=180.0
have been detected.
 
# 26 # Note: No missing atoms detected in residues
All expected atoms are present in residues. This validation option has not
looked at 'things' that can or should be attached to the elementary building
blocks (amino acids, nucleotides). Even the C-terminal oxygens are treated
separately.
 
# 27 # Warning: B-factors outside the range 0.0 - 100.0
In principle, B-factors can have a very wide range of values, but in
practice, B-factors should not be zero while B-factors above 100.0
are a good indicator that the location of that atom is meaningless. Be
aware that the cutoff at 100.0 is arbitrary. 'High' indicates that atoms
with a B-factor > 100.0 were observed; 'Zero' indicates that atoms with
a B-factor of zero were observed.
 
  135 LYS  ( 137-) A  -   High
  152 TYR  ( 154-) A  -   High
  247 ILE  ( 249-) A  -   High
  277 ARG  ( 279-) A  -   High
 
# 28 # Note: C-terminus capping
The residues listed in the table below are either C-terminal or pseudo
C-terminal (i.e. last residue before a missing residue).
In X-ray the coordinates must be located in density. Mobility or disorder
sometimes cause this density to be so poor that the positions of the atoms
cannot be determined. Crystallographers tend to leave out the atoms in such
cases. In many cases the N- or C-terminal residues are too disordered to see.
In case of the N-terminus, you can often see from the residue numbers if
there are missing residues; at the C-terminus this is impossible. Therefore,
often the position of the backbone nitrogen of the first residue missing
at the C-terminal end is calculated and added to indicate that there
are missing residues. As a single N causes validation trouble, we remove
these single-N-residues before doing the validation. If this happened,
the label -N is added to the pseudo C-terminus. Other labels can be +X
in case something weird is bound to the backbone C, or +OXT if a spurious
OXT atom is found. -OXT indicates that an expected OXT is missing. 'Swap'
means that the O' and O'' (O and OXT in PDB files) have been swapped in
terms of nomenclature. 'Bad' means that something bad happened that WHAT IF
does not understand. In such cases you might get three residue numbers in
square brackets; one of those might be what WHAT IF had expected to find,
but then it also might not). In case of chain breaks the number of missing
residues is listen in round brackets. OK means what it suggests...
 
Be aware that we cannot easily see the difference between these errors and
errors in the chain and residue numbering schemes. So do not blindly trust
the table below. If you get weird errors at, or near, the left-over
incomplete C-terminal residue, please check by hand if a missing Oxt or
a removed single N is the cause. Also, many peptidic ligands get the same
chain identifier as the larger protein they are bound to. In such cases there
are more than one C-termini and OXTs with the same ID. WHAT IF gives some
random warnings about these cases. So, don't take everything at face value,
but think for yourself.
 
  299 SER  ( 301-) A  -        +OXT [ 299 ; 299 ; 301]
 
# 29 # Note: Weights administratively correct
All atomic occupancy factors ('weights') fall in the 0.0--1.0 range, which
makes them administratively correct.
 
# 30 # Note: Normal distribution of occupancy values
 
The distribution of the occupancy values in this file seems 'normal'.
 
Be aware that this evaluation is merely the result of comparing this file
with about 500 well-refined high-resolution files in the PDB. If this file
has much higher or much lower resolution than the PDB files used
in WHAT CHECK's training set, non-normal values might very well be perfectly
fine, or normal values might actually be not so normal. So, this check is
actually more an indicator and certainly not a check in which I have great
confidence.
 
# 31 # Warning: Occupancy atoms do not add up to 1.0.
In principle, the occupancy of all alternates of one atom should add up till
1.0. A valid exception is the missing atom (i.e. an atom not seen in the
electron density) that is allowed to have a 0.0 occupancy. Sometimes this
even happens when there are no alternate atoms given...
 
Atoms want to move. That is the direct result of the second law of
thermodynamics, in a somewhat weird way of thinking. Any way, many atoms
seem to have more than one position where they like to sit, and they jump
between them. The population difference between those sites (which is related
to their energy differences) is seen in the occupancy factors. As also for
atoms it is 'to be or not to be', these occupancies should add up to 1.0.
Obviously, it is possible that they add up to a number less than 1.0, in
cases where there are yet more, but undetected' rotamers/positions in play,
but also in those cases a warning is in place as the information shown
in the PDB file is less certain than it could have been. The residues
listed below contain atoms that have an occupancy greater than zero, but
their alternates do not add up to one. 'Strange' is added as a comment when
we believe that the structure shows no obvious reasons why this residue
should have a reduced occupancy.
 
WARNING. Presently WHAT CHECK only deals with a maximum of two alternate
positions. A small number of atoms in the PDB has three alternates. In
those cases the warning given here should obviously be neglected!
In a next release we will try to fix this.
 
  102 VAL  ( 104-) A  -   0.50
  163 MET  ( 165-) A  -   0.50
  223 THR  ( 225-) A  -   0.60
  252 SER  ( 254-) A  -   0.50
 
# 32 # Warning: What type of B-factor?
WHAT CHECK does not yet know well how to cope with B-factors in case TLS has
been used. It simply assumes that the B-factor listed on the ATOM and HETATM
cards are the total B-factors. When TLS refinement is used that assumption
sometimes is not correct. The header of the PDB file states that TLS groups
were used. So, if WHAT CHECK complains about your  B-factors, while you think
that they are OK, then check for TLS related B-factor problems first.
 
Number of TLS groups mentione in PDB file header: 0
 
Temperature not mentioned in PDB file. This most likely means
that the temperature record is absent.
Room temperature assumed
 
# 33 # Note: Number of buried atoms with low B-factor is OK
For protein structures determined at room temperature, no more than about 1
percent of the B factors of buried atoms is below 5.0. In liquid
nitrogen this percentage is allowed to be higher, of course.
 
Percentage of buried atoms with B less than 5 :   0.00
 
# 34 # Warning: Analysis of bonded atoms indicate B-factor problems
For each of the bond types in a protein a distribution was derived for the
difference between the square roots of the B-factors of the two atoms. All
bonds in the current protein were scored against these distributions. The
number given below is the RMS Z-score over the structure. For a structure
with completely restrained B-factors, this value will be around 0.35, for
extremely high resolution structures refined with free isotropic B-factors
this number is expected to be near 1.0. A value over 1.5 is a sign of
under-contraining of the B-factors during refinement.
 
RMS Z-score :  1.591 over    2065 bonds
Average difference in B over a bond :    4.56
RMS difference in B over a bond :    6.13
 
# 35 # Note: B-factor plot
The average atomic B-factor per residue is plotted as function of the residue
number.
 
In the TeX file, a plot has been inserted here
 
Chain identifier: A
 
# 36 # Note: Introduction to the nomenclature section.
Nomenclature problems seem, at first, rather unimportant. After all who
cares if we call the delta atoms in leucine delta2 and delta1 rather than
the other way around. Chemically speaking that is correct. But structures
have not been solved and deposited just for chemists to look at them. Most
times a structure is used, it is by software in a bioinformatics lab. And
if they compare structures in which the one used C delta1 and delta2 and the
other uses C delta2 and delta1, then that comparison will fail. Also, we
recalculate all structures every so many years to make sure that everybody
always can get access to the best coordinates that can be obtained from
the (your?) experimental data. These recalculations will be troublesome if
there are nomenclature problems.
 
Several nomenclature problems actually are worse than that. At the
WHAT CHECK website [REF] you can get an overview of the importance of all
nomenclature problems that we list.
 
# 37 # Note: Valine nomenclature OK
No errors were detected in valine nomenclature.
 
# 38 # Note: Threonine nomenclature OK
No errors were detected in threonine nomenclature.
 
# 39 # Note: Isoleucine nomenclature OK
No errors were detected in isoleucine nomenclature.
 
# 40 # Note: Leucine nomenclature OK
No errors were detected in leucine nomenclature.
 
# 41 # Note: Arginine nomenclature OK
No errors were detected in arginine nomenclature.
 
# 42 # Note: Tyrosine torsion conventions OK
No errors were detected in tyrosine torsion angle conventions.
 
# 43 # Note: Phenylalanine torsion conventions OK
No errors were detected in phenylalanine torsion angle conventions.
 
# 44 # Note: Aspartic acid torsion conventions OK
No errors were detected in aspartic acid torsion angle conventions.
 
# 45 # Note: Glutamic acid torsion conventions OK
No errors were detected in glutamic acid torsion angle conventions.
 
# 46 # Note: Phosphate group names OK in DNA/RNA
No errors were detected in nucleic acid phosphate group naming conventions
(or this structure contains no nucleic acids).
 
# 47 # Note: Heavy atom naming OK
No errors were detected in the atom names for non-hydrogen atoms. Please
be aware that the PDB wants us to deliberately make some nomenclature errors;
especially in non-canonical amino acids.
 
# 48 # Note: No decreasing residue numbers
All residue numbers are strictly increasing within each chain.
 
# 49 # Note: All bond lengths OK
All bond lengths are in agreement with standard bond lengths using a
tolerance of 4 sigma (both standard values and sigma for amino acids
have been taken from Engh and Huber [REF], for DNA/RNA from Parkinson
et al [REF]).
 
# 50 # Warning: Low bond length variability
Bond lengths were found to deviate less than normal from the mean Engh and
Huber [REF] and/or Parkinson et al [REF] standard bond lengths. The RMS
Z-score given below is expected to be near 1.0 for a normally restrained
data set. The fact that it is lower than 0.667 in this structure might
indicate that too-strong restraints have been used in the refinement. This
can only be a problem  for high resolution X-ray structures.
 
 RMS Z-score for bond lengths: 0.382
 RMS-deviation in bond distances: 0.009
 
# 51 # Note: No bond length directionality
Comparison of bond distances with Engh and Huber [REF] standard values for
protein residues and Parkinson et al [REF] values for DNA/RNA does not show
significant systematic deviations.
 
# 52 # Warning: Unusual bond angles
The bond angles listed in the table below were found to deviate more than 4
sigma from standard bond angles (both standard values and sigma for protein
residues have been taken from Engh and Huber [REF], for DNA/RNA from
Parkinson et al [REF]). In the table below for each strange angle the bond
angle and the number of standard deviations it differs from the standard
values is given. Please note that disulphide bridges are neglected. Atoms
starting with "-" belong to the previous residue in the sequence.
 
    1 PHE  (   3-) A  -    CA   CB   CG  119.16    5.4
   32 ASP  (  34-) A  -    CA   CB   CG  116.63    4.0
  138 PHE  ( 140-) A  -    CA   CB   CG  118.66    4.9
  185 ASP  ( 187-) A  -    CA   CB   CG  116.91    4.3
  293 ASP  ( 295-) A  -    CA   CB   CG  117.89    5.3
 
# 53 # Warning: Low bond angle variability
Bond angles were found to deviate less than normal from the standard bond
angles (normal values for protein residues were taken from Engh and Huber
[REF], for DNA/RNA from Parkinson et al [REF]). The RMS Z-score given below
is expected to be near 1.0 for a normally restrained data set. The fact that
it is lower than 0.667 in this structure might indicate that too-strong
restraints have been used in the refinement. This can only be a problem for
high resolution X-ray structures.
 
 RMS Z-score for bond angles: 0.659
 RMS-deviation in bond angles: 1.205
 
# 54 # Note: Residue hand check OK
No atoms are observed that have the wrong handedness. Be aware, though, that
WHAT CHECK might have corrected the handedness of some atoms already. The
handedness has not been corrected for any case where the problem is worse
than just an administrative discomfort.
 
# 55 # Note: Chirality OK
All protein atoms have proper chirality, or there is no intact protein
present in the PDB file.
The average deviation= 0.562
 
# 56 # Note: Improper dihedral angle distribution OK
The RMS Z-score for all improper dihedrals in the structure is within normal
ranges.
 
 Improper dihedral RMS Z-score : 0.454
 
# 57 # Note: Tau angles OK
All of the tau angles (N-C-alpha-C) of amino acids fall within expected
RMS deviations.
 
# 58 # Note: Normal tau angle deviations
The RMS Z-score for the tau angles (N-C-alpha-C) in the structure falls
within the normal range that we guess to be 0.5 - 1.5. Be aware, we
determined the tau normal distributions from 500 high-resolution X-ray
structures, rather than from CSD data, so we cannot be 100 percent certain
about these numbers.
 
 Tau angle RMS Z-score : 0.764
 
# 59 # Note: Side chain planarity OK
All of the side chains of residues that have an intact planar group are
planar within expected RMS deviations.
 
# 60 # Note: Atoms connected to aromatic rings OK
All of the atoms that are connected to planar aromatic rings in side chains
of amino-acid residues are in the plane within expected RMS deviations.
Since there is no DNA and no protein with hydrogens, no uncalibrated
planarity check was performed.
 
# 61 # Warning: Ramachandran Z-score low
The score expressing how well the backbone conformations of all residues
correspond to the known allowed areas in the Ramachandran plot is a bit low.
 
 Ramachandran Z-score : -3.907
 
# 62 # Note: Ramachandran check
The list contains per-residue Z-scores describing how well each residue
fits into the allowed areas of the Ramachandran plot will not be printed
because WHAT CHECK found no reason to cry.
 
# 63 # Warning: Torsion angle evaluation shows unusual residues
The residues listed in the table below contain bad or abnormal
torsion angles.
 
These scores give an impression of how `normal' the torsion angles in
protein residues are. All torsion angles except omega are used for
calculating a `normality' score. Average values and standard deviations were
obtained from the residues in the WHAT CHECK database. These are used to
calculate Z-scores. A residue with a Z-score of below -2.0 is poor, and a
score of less than -3.0 is worrying. For such residues more than one torsion
angle is in a highly unlikely position.
 
  182 PRO  ( 184-) A  -   -3.0
  152 TYR  ( 154-) A  -   -2.8
   91 THR  (  93-) A  -   -2.6
  188 THR  ( 190-) A  -   -2.5
   25 LEU  (  27-) A  -   -2.3
  274 MET  ( 276-) A  -   -2.2
  247 ILE  ( 249-) A  -   -2.2
  219 ASN  ( 221-) A  -   -2.1
  284 ILE  ( 286-) A  -   -2.1
   22 THR  (  24-) A  -   -2.0
  139 LEU  ( 141-) A  -   -2.0
  175 LEU  ( 177-) A  -   -2.0
 
# 64 # Warning: Backbone evaluation reveals unusual conformations
The residues listed in the table below have abnormal backbone torsion
angles.
 
Residues with `forbidden' phi-psi combinations are listed, as well as
residues with unusual omega angles (deviating by more than 3 sigma from the
normal value). Please note that it is normal if about 5 percent of the
residues is listed here as having unusual phi-psi combinations.
 
    6 PHE  (   8-) A  - Omega to (next) Pro poor
   21 GLY  (  23-) A  - Poor phi/psi
   31 ASP  (  33-) A  - Poor phi/psi
   36 CYS  (  38-) A  - Omega to (next) Pro poor
   42 CYS  (  44-) A  - omega poor
   48 LEU  (  50-) A  - Poor phi/psi
   49 ASN  (  51-) A  - Omega to (next) Pro poor
   51 ASN  (  53-) A  - omega poor
   69 GLY  (  71-) A  - Poor phi/psi
   77 GLY  (  79-) A  - Poor phi/psi
   82 ASN  (  84-) A  - Poor phi/psi
   91 THR  (  93-) A  - Poor phi/psi
   93 ASN  (  95-) A  - Omega to (next) Pro poor
   96 THR  (  98-) A  - Omega to (next) Pro poor
   97 PRO  (  99-) A  - omega poor
And so on for a total of    48 lines.
 
# 65 # Error: Chi-1/chi-2 rotamer problems
List of residues with a poor chi-1/chi-2 combination. Be aware that for this
validation option the individual scores are far less important than the
overall score that is given below the table.
 
   25 LEU  (  27-) A  -    -1.32
   65 LEU  (  67-) A  -    -1.32
  139 LEU  ( 141-) A  -    -1.32
  175 LEU  ( 177-) A  -    -1.30
  240 LEU  ( 242-) A  -    -1.32
  251 LEU  ( 253-) A  -    -1.32
  266 LEU  ( 268-) A  -    -1.32
   48 LEU  (  50-) A  -    -1.27
   54 ASP  (  56-) A  -    -1.23
   73 LEU  (  75-) A  -    -1.26
  185 ASP  ( 187-) A  -    -1.23
  247 ILE  ( 249-) A  -    -1.21
  279 ILE  ( 281-) A  -    -1.24
  284 ILE  ( 286-) A  -    -1.24
   41 ILE  (  43-) A  -    -1.15
And so on for a total of   152 lines.
 
# 66 # Error: chi-1/chi-2 angle correlation Z-score very low
The score expressing how well the chi-1/chi-2 angles of all residues
correspond to the populated areas in the database is
very low.
 
 chi-1/chi-2 correlation Z-score : -5.396
 
# 67 # Warning: Unusual rotamers
The residues listed in the table below have a rotamer that is not seen very
often in the database of solved protein structures. This option determines
for every residue the position specific chi-1 rotamer distribution.
Thereafter it verified whether the actual residue in the molecule has the
most preferred rotamer or not. If the actual rotamer is the preferred one,
the score is 1.0. If the actual rotamer is unique, the score is 0.0. If
there are two preferred rotamers, with a population distribution of 3:2 and
your rotamer sits in the lesser populated rotamer, the score will be 0.667.
No value will be given if insufficient hits are found in the database.
 
It is not necessarily an error if a few residues have rotamer values below
0.3, but careful inspection of all residues with these low values could be
worth it.
 
  160 MET  ( 162-) A  -   0.39
 
# 68 # Warning: Unusual backbone conformations
For the residues listed in the table below, the backbone formed by itself and
two neighbouring residues on either side is in a conformation that is not
seen very often in the database of solved protein structures. The number
given in the table is the number of similar backbone conformations in the
database with the same amino acid in the centre.
 
For this check, backbone conformations are compared with database structures
using C-alpha superpositions with some restraints on the backbone oxygen
positions.
 
A residue mentioned in the table can be part of a strange loop, or there
might be something wrong with it or its directly surrounding residues. There
are a few of these in every protein, but in any case it is worth looking at,
especially if a regular DSSP secondary structure (H or S for helix or strand,
respectively) is indicated!
 
   83 CYS  (  85-) A  -       0
   91 THR  (  93-) A  -       0
  117 ASN  ( 119-) A  -       0
  152 TYR  ( 154-) A  -       0
  180 TYR  ( 182-) A  -       0
  225 LEU  ( 227-) A  -       0
   49 ASN  (  51-) A  -       1
  140 ASN  ( 142-) A  -       1
  143 CYS  ( 145-) A  -       1
  247 ILE  ( 249-) A  -       1
  274 MET  ( 276-) A  -       1
  280 LEU  ( 282-) A  -       1
   68 ALA  (  70-) A  -       2
   82 ASN  (  84-) A  -       2
  163 MET  ( 165-) A  -       2
 
# 69 # Note: Backbone conformation Z-score OK
The backbone conformation analysis gives a score that is normal for well
refined protein structures.
 
 Backbone conformation Z-score : -0.952
 
# 70 # Note: Omega angle restraint OK
The omega angles for trans-peptide bonds in a structure is expected to give a
gaussian distribution with the average around +178 degrees, and a standard
deviation around 5.5. In the current structure the standard deviation agrees
with this expectation.
 
Omega average and std. deviation= 178.820 6.814
 
# 71 # Note: PRO puckering amplitude OK
Puckering amplitudes for all PRO residues are within normal ranges.
 
# 72 # Warning: Unusual PRO puckering phases
The proline residues listed in the table below have a puckering phase that is
not expected to occur in protein structures. Puckering parameters were
calculated by the method of Cremer and Pople [REF]. Normal PRO rings
approximately show a so-called envelope conformation with the C-gamma atom
above the plane of the ring (phi=+72 degrees), or a half-chair conformation
with C-gamma below and C-beta above the plane of the ring (phi=-90 degrees).
If phi deviates strongly from these values, this is indicative of a very
strange conformation for a PRO residue, and definitely requires a manual
check of the data. Be aware that this is a warning with a low confidence
level. See: Who checks the checkers? Four validation tools applied to eight
atomic resolution structures [REF].
 
   50 PRO  (  52-) A  -  -17.2 half-chair C-alpha/N (-18 degrees)
  182 PRO  ( 184-) A  -  -38.4 envelop C-alpha (-36 degrees)
  239 PRO  ( 241-) A  -   52.2 half-chair C-delta/C-gamma (54 degrees)
 
# 73 # Warning: Backbone oxygen evaluation
The residues listed in the table below have an unusual backbone oxygen
position.
 
For each of the residues in the structure, a search was performed to find
5-residue stretches in the WHAT CHECK database with superposable C-alpha
coordinates, and some restraints on the neighbouring backbone oxygens.
 
In the following table the RMS distance between the backbone oxygen positions
of these matching structures in the database and the position of the backbone
oxygen atom in the current residue is given. If this number is larger than
1.5 a significant number of structures in the database show an alternative
position for the backbone oxygen. If the number is larger than 2.0 most
matching backbone fragments in the database have the peptide plane flipped.
A manual check needs to be performed to assess whether the experimental data
can support that alternative as well. The number in the last column is the
number of database hits (maximum 80) used in the calculation. It is "normal"
that some glycine residues show up in this list, but they are still worth
checking!
 
  293 ASP  ( 295-) A  -  1.68   28
 
# 74 # Warning: Possible peptide flips
For the residues listed in the table below, the backbone formed by the
residue mentioned and the one N-terminal of it show systematic deviations
from normality that are consistent with a peptide flip. This can either
be a 180 degree flip of the entire peptide plane or a trans to cis flip.
(Cis to trans flips cannot be detected yet). The type can be TT+, TC-,
or TC+:
TT+ indicates a 180 degree flip of the entire peptide plane.
TC- indicates a trans to cis conversion that requires a flip of the N atom.
TC+ indicates a trans to cis conversion that requires a flip of the O atom.
Note that the method will only work correctly for PDB files with full
isotropic B-factors.
 
   91 THR  (  93-) A  - TT+   Likely
  152 TYR  ( 154-) A  - TT+   Likely
 
# 75 # Error: Abnormally short interatomic distances
The pairs of atoms listed in the table below have an unusually short
interactomic distance; each bump is listed in only one direction.
 
The contact distances of all atom pairs have been checked. Two atoms are
said to `bump' if they are closer than the sum of their Van der Waals radii
minus 0.40 Angstrom. For hydrogen bonded pairs a tolerance of 0.55 Angstrom
is used. The first number in the table tells you how much shorter that
specific contact is than the acceptable limit. The second distance is the
distance between the centres of the two atoms. Although we believe that two
water atoms at 2.4 A distance are too close, we only report water pairs that
are closer than this rather short distance.
 
INTRA and INTER indicate whether the clashes are between atoms in the same
asymmetric unit, or atoms in symmetry related asymmetric units, respectively.
The last text-item on each line represents the status of the atom pair. If
the final column contains the text 'HB', the bump criterion was relaxed
because there could be a hydrogen bond. Similarly relaxed criteria are used
for 1--3 and 1--4 interactions (listed as 'B2' and 'B3', respectively).
If the last column is 'BF', the sum of the B-factors of the atoms is higher
than 80, which makes the appearance of the bump somewhat less severe because
the atoms probably are not there anyway. BL, on the other hand, indicates
that the bumping atoms both have a low B-factor, and that makes the bumps
more worrisome.
 
Bumps between atoms for which the sum of their occupancies is lower than one
are not reported. If the MODEL number does not exist (as is the case in most
X-ray files), a minus sign is printed instead.
 
  117 ASN  ( 119-) A  -    O   <-->   119 SER  ( 121-) A  -    N      0.55    2.15  INTRA
  105 GLN  ( 107-) A  -    N   <-->   108 GLN  ( 110-) A  -    OE1    0.43    2.27  INTRA BF
  103 ARG  ( 105-) A  -    NH2 <-->   179 PHE  ( 181-) A  -    O      0.17    2.53  INTRA
  263 CYS  ( 265-) A  -    O   <-->   267 LYS  ( 269-) A  -    N      0.14    2.56  INTRA BL
  107 GLY  ( 109-) A  -    N   <-->   128 MET  ( 130-) A  -    O      0.13    2.57  INTRA BF
  268 GLU  ( 270-) A  -    O   <-->   272 ASN  ( 274-) A  -    N      0.10    2.60  INTRA BF
    6 PHE  (   8-) A  -    N   <-->   111 SER  ( 113-) A  -    OG     0.10    2.60  INTRA BL
   49 ASN  (  51-) A  -    ND2 <-->   186 ARG  ( 188-) A  -    CZ     0.09    3.01  INTRA BF
  165 LEU  ( 167-) A  -    O   <-->   167 THR  ( 169-) A  -    N      0.07    2.63  INTRA BF
  201 ASN  ( 203-) A  -    ND2 <-->   287 ASP  ( 289-) A  -    O      0.06    2.64  INTRA
   14 CYS  (  16-) A  -    O   <-->    29 TRP  (  31-) A  -    N      0.05    2.65  INTRA BL
  147 GLY  ( 149-) A  -    N   <-->   159 TYR  ( 161-) A  -    O      0.04    2.66  INTRA BL
  103 ARG  ( 105-) A  -    NH1 <-->   178 LYS  ( 180-) A  -    O      0.04    2.66  INTRA BL
   90 ASP  (  92-) A  -    OD1 <-->    91 THR  (  93-) A  -    N      0.04    2.56  INTRA BF
  188 THR  ( 190-) A  -    O   <-->   190 GLN  ( 192-) A  -    N      0.03    2.67  INTRA BL
  249 GLY  ( 251-) A  -    N   <-->   250 PRO  ( 252-) A  -    CD     0.03    2.97  INTRA BL
  186 ARG  ( 188-) A  -    O   <-->   190 GLN  ( 192-) A  -    NE2    0.03    2.67  INTRA
  219 ASN  ( 221-) A  -    ND2 <-->   268 GLU  ( 270-) A  -    OE1    0.02    2.68  INTRA
  128 MET  ( 130-) A  -    CE  <-->   132 HIS  ( 134-) A  -    C      0.02    3.18  INTRA
  227 ASP  ( 229-) A  -    OD2 <-->   267 LYS  ( 269-) A  -    NZ     0.02    2.68  INTRA BF
  165 LEU  ( 167-) A  -    N   <-->   169 VAL  ( 171-) A  -    O      0.02    2.68  INTRA BL
   68 ALA  (  70-) A  -    N   <-->    71 VAL  (  73-) A  -    O      0.02    2.68  INTRA BF
  131 ASN  ( 133-) A  -    ND2 <-->   193 GLY  ( 195-) A  -    O      0.02    2.68  INTRA
  117 ASN  ( 119-) A  -    C   <-->   119 SER  ( 121-) A  -    N      0.02    2.88  INTRA BF
  248 LEU  ( 250-) A  -    N   <-->   249 GLY  ( 251-) A  -    N      0.01    2.59  INTRA BL
  252 SER  ( 254-) A  -    O   <-->   256 GLY  ( 258-) A  -    N      0.01    2.69  INTRA
   42 CYS  (  44-) A  -    SG  <-->    52 TYR  (  54-) A  -    CE1    0.01    3.39  INTRA BF
  184 VAL  ( 186-) A  -    O   <-->   186 ARG  ( 188-) A  -    N      0.01    2.69  INTRA BL
  151 ASP  ( 153-) A  -    O   <-->   154 CYS  ( 156-) A  -    N      0.01    2.69  INTRA BF
   20 CYS  (  22-) A  -    N   <-->    23 THR  (  25-) A  -    O      0.01    2.69  INTRA BF
 
# 76 # Note: Some notes regarding these bumps
The bumps have been binned in 5 categories ranging from 'please look at'
till 'must fix'. Additionally, the integrated sum of all bumps, the squared
sum of all bumps, and these latter two values normalized by the number of
contacts are listed too for comparison purposes between, for example, small
and large proteins.
 
Total bump value: 2.293
Total bump value per residue: 0.100
Total number of bumps: 30
Total squared bump value: 0.602
Total number of bumps in the mildest bin: 28
Total number of bumps in the second bin: 1
Total number of bumps in the middle bin: 1
Total number of bumps in the fourth bin: 0
Total number of bumps in the worst bin: 0
 
# 77 # Note: Inside/outside distribution check
The following list contains per-residue Z-scores describing how well the
residue's observed accessibility fits the expected one. A positive Z-score
indicates "more exposure than usual", whereas a negative Z-score means
"more buried than usual". The absolute value of the Z-score must be used to
judge the quality. Today WHAT CHECK saw no reason to complain.
 
# 78 # Note: Inside/Outside residue distribution normal
The distribution of residue types over the inside and the outside of the
protein is normal.
 
inside/outside RMS Z-score : 1.012
 
# 79 # Note: Inside/Outside RMS Z-score plot
The Inside/Outside distribution normality RMS Z-score over a 15 residue
window is plotted as function of the residue number. High areas in the plot
(above 1.5) indicate unusual inside/outside patterns.
 
In the TeX file, a plot has been inserted here
 
Chain identifier: A
 
# 80 # Warning: Abnormal packing environment for some residues
The residues listed in the table below have an unusual packing environment.
 
The packing environment of the residues is compared with the average packing
environment for all residues of the same type in good PDB files. A low
packing score can indicate one of several things: Poor packing, misthreading
of the sequence through the density, crystal contacts, contacts with a
co-factor, or the residue is part of the active site. It is not uncommon to
see a few of these, but in any case this requires further inspection of the
residue.
 
  152 TYR  ( 154-) A  -  -6.78
  187 GLN  ( 189-) A  -  -6.15
   95 LYS  (  97-) A  -  -6.10
  135 LYS  ( 137-) A  -  -6.02
  220 ARG  ( 222-) A  -  -5.71
  105 GLN  ( 107-) A  -  -5.42
  274 MET  ( 276-) A  -  -5.26
  139 LEU  ( 141-) A  -  -5.19
  254 GLN  ( 256-) A  -  -5.17
   58 ARG  (  60-) A  -  -5.05
 
# 81 # Warning: Abnormal packing environment for sequential residues
A stretch of at least three sequential residues with a questionable packing
environment was found. This could indicate that these residues are part
of a strange loop. It might also be an indication of misthreading in the
density. However, it can also indicate that one or more residues in this
stretch have other problems such as, for example, missing atoms, very
weird angles or bond lengths, etc.
 
The table below lists the first and last residue in each stretch found,
as well as the average residue score of the series.
 
    2 ARG  (   4-) A  -        4 --- MET     6- (A ) -       -4.82
 
# 82 # Note: Structural average packing environment OK
The structural average packing score is within normal ranges.
 
 
Average for range     1 -  299 :  -0.844
 
# 83 # Note: Quality value plot
The quality value smoothed over a 10 residue window is plotted as function
of the residue number. Low areas in the plot (below -2.0) indicate unusual
packing.
 
In the TeX file, a plot has been inserted here
 
Chain identifier: A
 
# 84 # Warning: Low packing Z-score for some residues
The residues listed in the table below have an unusual packing
environment according to the 2nd generation packing check. The score
listed in the table is a packing normality Z-score: positive means
better than average, negative means worse than average. Only residues
scoring less than -2.50 are listed here. These are the unusual
residues in the structure, so it will be interesting to take a
special look at them.
 
  219 ASN  ( 221-) A  -  -2.82
   41 ILE  (  43-) A  -  -2.52
 
# 85 # Note: No series of residues with abnormal new packing environment
There are no stretches of four or more residues each having a packing
Z-score worse than -1.75.
ERROR. File not found:
TAPEOUT.DAT
 
# 86 # Note: Second generation quality Z-score plot
The second generation quality Z-score smoothed over a 10 residue window
is plotted as function of the residue number. Low areas in the plot (below
-1.3) indicate unusual packing.
 
In the TeX file, a plot has been inserted here
 
Chain identifier: A
 
# 87 # Warning: No crystallisation information
No, or very inadequate, crystallisation information was observed upon
reading the PDB file header records. This information should be available
in the form of a series of REMARK 280 lines. Without this information a
few things, such as checking ions in the structure, cannot be performed
optimally.
 
# 88 # Note: Water contacts OK
All water clusters make at least one contact with a non-water atom.
 
# 89 # Note: No waters need moving
All water molecules are sufficiently close to the asymmetric unit given in
the input file.
 
# 90 # Note: Water hydrogen bonds OK
All water molecules can form hydrogen bonds.
 
# 91 # Error: His, Asn, Gln side chain flips
Listed here are Histidine, Asparagine or Glutamine residues for
which the orientation determined from hydrogen bonding analysis are
different from the assignment given in the input. Either they could
form energetically more favourable hydrogen bonds if the terminal
group was rotated by 180 degrees, or there is no assignment in the
input file (atom type 'A') but an assignment could be made. Be aware,
though, that if the topology could not be determined for one or more
ligands, then this option will make errors.
 
   26 ASN  (  28-) A  -
   61 ASN  (  63-) A  -
  108 GLN  ( 110-) A  -
  170 HIS  ( 172-) A  -
  244 HIS  ( 246-) A  -
  297 GLN  ( 299-) A  -
 
# 92 # Note: Histidine type assignments
For all complete HIS residues in the structure a tentative assignment to
HIS-D (protonated on ND1), HIS-E (protonated on NE2), or HIS-H (protonated
on both ND1 and NE2, positively charged) is made based on the hydrogen bond
network. A second assignment is made based on which of the Engh and Huber
[REF] histidine geometries fits best to the structure.
 
In the table below all normal histidine residues are listed. The assignment
based on the geometry of the residue is listed first, together with the RMS
Z-score for the fit to the Engh and Huber parameters. For all residues where
the H-bond assignment is different, the assignment is listed in the last
columns, together with its RMS Z-score to the Engh and Huber parameters.
 
As always, the RMS Z-scores should be close to 1.0 if the residues were
restrained to the Engh and Huber parameters during refinement, and if
enough (high resolution) data is available.
 
Please note that because the differences between the geometries of the
different types are small it is possible that the geometric assignment given
here does not correspond to the type used in refinement. This is especially
true if the RMS Z-scores are much higher than 1.0.
 
If the two assignments differ, or the `geometry' RMS Z-score is high, it is
advisable to verify the hydrogen bond assignment, check the HIS type used
during the refinement and possibly adjust it.
 
   39 HIS  (  41-) A  -   HIS-E   0.45
   62 HIS  (  64-) A  -   HIS-E   0.51
   78 HIS  (  80-) A  -   HIS-E   0.56
  132 HIS  ( 134-) A  -   HIS-E   0.50
  161 HIS  ( 163-) A  -   HIS-E   0.70
  162 HIS  ( 164-) A  -   HIS-E   0.44
  170 HIS  ( 172-) A  -   HIS-E   0.73
  244 HIS  ( 246-) A  -   HIS-E   0.47
 
# 93 # Warning: Buried unsatisfied hydrogen bond donors
The buried hydrogen bond donors listed in the table below have a hydrogen
atom that is not involved in a hydrogen bond in the optimized hydrogen bond
network.
 
Hydrogen bond donors that are buried inside the protein normally use all of
their hydrogens to form hydrogen bonds within the protein. If there are any
non hydrogen bonded buried hydrogen bond donors in the structure they will
be listed here. In very good structures the number of listed atoms will tend
to zero.
 
Waters are not listed by this option.
 
    4 MET  (   6-) A  -    N
   39 HIS  (  41-) A  -    N
   42 CYS  (  44-) A  -    N
   53 GLU  (  55-) A  -    N
   77 GLY  (  79-) A  -    N
   93 ASN  (  95-) A  -    ND2
  135 LYS  ( 137-) A  -    N
  146 VAL  ( 148-) A  -    N
  150 ILE  ( 152-) A  -    N
  153 ASP  ( 155-) A  -    N
  169 VAL  ( 171-) A  -    N
  175 LEU  ( 177-) A  -    N
  176 GLU  ( 178-) A  -    N
  183 PHE  ( 185-) A  -    N
  185 ASP  ( 187-) A  -    N
  212 ASN  ( 214-) A  -    ND2
  217 PHE  ( 219-) A  -    N
  221 PHE  ( 223-) A  -    N
  223 THR  ( 225-) A  -    OG1
  224 THR  ( 226-) A  -    OG1
  225 LEU  ( 227-) A  -    N
  228 PHE  ( 230-) A  -    N
  248 LEU  ( 250-) A  -    N
  261 ASP  ( 263-) A  -    N
  282 SER  ( 284-) A  -    N
  286 GLU  ( 288-) A  -    N
  288 GLU  ( 290-) A  -    N
  289 PHE  ( 291-) A  -    N
  297 GLN  ( 299-) A  -    N
 
# 94 # Warning: Buried unsatisfied hydrogen bond acceptors
The buried side-chain hydrogen bond acceptors listed in the table below are
not involved in a hydrogen bond in the optimized hydrogen bond network.
 
Side-chain hydrogen bond acceptors buried inside the protein normally form
hydrogen bonds within the protein. If there are any not hydrogen bonded in
the optimized hydrogen bond network they will be listed here.
 
Waters are not listed by this option.
 
   26 ASN  (  28-) A  -    OD1
  162 HIS  ( 164-) A  -    ND1
  219 ASN  ( 221-) A  -    OD1
 
# 95 # Note: Some notes regarding these donors and acceptors
The donors and acceptors have been counted, also as function of their
accessibility. The buried donors and acceptors have been binned in five
categories ranging from not forming any hydrogen bond till forming a poor
till perfect hydrogen bond. Obviously, the buried donors and acceptors
with no or just a poor hydrogen bond should be a topic of concern. As every
protein contains more acceptors than donors, unsatisfied donors are more in
need of attention than unsatisfied acceptors.
 
Total number of donors: 426
- of which buried: 211
Total number of acceptors: 463
- of which buried: 184
Total number of donor+acceptors: 50
  (e.g. the Ser Ogamma that can donate and accept)
- of which buried: 13
Buried donors: 211
- without H-bond: 27
- essentially without H-bond: 0
- with only a very poor H-bond: 0
- with a poor H-bond: 5
- with a H-bond: 179
Buried acceptors: 184
- without H-bond: 38
- essentially without H-bond: 0
- with only a very poor H-bond: 1
- with a poor H-bond: 17
- with a H-bond: 128
 
# 96 # Note: Content of the PDB file as interpreted by WHAT CHECK
Content of the PDB file as interpreted by WHAT CHECK.
WHAT CHECK has read your PDB file, and stored it internally in what is called
'the soup'. The content of this soup is listed here. An extensive explanation
of all frequently used WHAT CHECK output formats can be found at
swift.cmbi.ru.nl. Look under output formats. A course on reading this
'Molecules' table is part of the WHAT CHECK website.
 
     1     1 (    3)   299 (  301) A Protein             /zata/tempdir/3d6...
     2   300 (  301)   300 (  301) A S O2 <-   299       /zata/tempdir/3d6...
     3   301 (  350)   301 (  350) A 959                 /zata/tempdir/3d6...
     4   302 ( HOH )   302 ( HOH ) A water   (    1)     /zata/tempdir/3d6...
 
# 97 # Note: Summary report
This is an overall summary of the quality of the structure as compared with
current reliable structures. Numbers in brackets are the average and standard
deviation observed for a large number of files determined with a similar
resolution.
 
The second table mostly gives an impression of how well the model conforms
to common refinement restraint values. These numbers are less than 1.0 if the
spread in data is too little, and larger than 1.0 when the spread is too
large. The former does not need to be a problem, the latter always is bad.
 
 Structure Z-scores, positive is better than average:
  Resolution read from PDB file  :   2.700
  1st generation packing quality :  -0.860 (          (  -0.8,  2.5))
  2nd generation packing quality :  -1.630 (          (  -1.6,  1.2))
  Ramachandran plot appearance   :  -3.907 (poor      (  -2.9,  1.6))
  chi-1/chi-2 rotamer normality  :  -5.396 (bad       (  -4.7,  1.8))
  Backbone conformation          :  -0.952 (          (  -0.9,  3.7))
  Inside/Outside distribution    :   1.012
 
 RMS Z-scores, should be close to 1.0:
  Bond lengths                   :   0.382 (tight)
  Bond angles                    :   0.659 (tight)
  Omega angle restraints         :   1.239
  Side chain planarity           :   0.515 (tight)
  Improper dihedral distribution :   0.454
  B-factor distribution          :   1.591 (loose)
 
# 98 # Note: Introduction to refinement recommendations
First, be aware that the recommendations for crystallographers listed below
are produced by a computer program that was written by a guy who got his
PhD in NMR...
 
We have tried to convert the messages written in this report into a small
set of things you can do with your refinement software to get a better
structure. The things you should do first are listed first. And in some
cases you should first fix that problem, then refine a bit further, and
then run WHAT CHECK again before looking at other problems. If, for example,
WHAT CHECK has found a problem with the SCALE and CRYST cards, then you must
first fix that problem, refine the structure a bit further, and run WHAT
CHECK again because errors in the SCALE and or CRYST card can lead to many
problems elsewhere in the validation process.
 
It is also important to keep in mind that WHAT CHECK is software and that it
occasionally totally misunderstands what is the cause of a problem. But, if
WHAT CHECK lists a problem there normally is a problem albeit that it not
always is the actual problem that gets listed.
 
# 99 # Note: Matthews coefficient problem
WHAT CHECK detected a Matthews coefficient problem. Most times this is an
administrative problem caused by typing the wrong cell multiplicity number
on the CRYST card (or not typing it at all). Occasionally it is caused by
typing the wrong space group on the CRYST card. You better fix this problem,
but normally this problem does not cause WHAT CHECK to give any erroneous
error messages further down in the report.
 
# 100 # Error: Bumps in your structure
Upon analysing the bumps in your structure, WHAT CHECK got a bit
worried. Sometimes this means that you have forgotten to lower the
occupancy of overlapping ligands, residues, or water molecules. But,
whatever is the origin of this problem, you have to analyse it and
fix it.
 
# 101 # Note: His, Asn, Gln side chain flips.
His, Asn, and Gln have an asymmetry in their side chain that is hard to
detect unless you have data at much better than 1.0 Angstrom resolution.
WHAT CHECK thinks that your structure contains His, Asn, or Gln residues that
will make better hydrogen bonds when flipped around their chi-2, chi-2, or
chi-3 side chain torsion angle, respectively. You better
check these Asn, His, and Gln residues, and if you use a refinement program
that includes molecular dynamics, then you must (after the
flips were made) refine a bit further before running WHAT CHECK again.
 
# 102 # Warning: Troublesome residues
The residues listed in the table below need to be inspected
 
This table is a very rough attempt to sort the residues according to how
badly they need your attention. The idea is that when you sit in  in front
of the graphics screen and study the residues with the electron density
present that you improve the structure most by dealing with the top residues
in this list first.
 
    1 PHE  (   3-) A  -     15.81
  152 TYR  ( 154-) A  -     13.69
  135 LYS  ( 137-) A  -     13.05
  187 GLN  ( 189-) A  -     12.31
   95 LYS  (  97-) A  -     12.19
  220 ARG  ( 222-) A  -     11.42
  105 GLN  ( 107-) A  -     11.22
  274 MET  ( 276-) A  -     10.60
  139 LEU  ( 141-) A  -     10.47
  254 GLN  ( 256-) A  -     10.33
   58 ARG  (  60-) A  -     10.11
  185 ASP  ( 187-) A  -      4.23
  293 ASP  ( 295-) A  -      3.97
  138 PHE  ( 140-) A  -      3.64
   32 ASP  (  34-) A  -      3.02
And so on for a total of    37 lines.
==============
 
 
WHAT IF
    G.Vriend,
      WHAT IF: a molecular modelling and drug design program,
    J. Mol. Graph. 8, 52--56 (1990).
 
WHAT_CHECK (verification routines from WHAT IF)
    R.W.W.Hooft, G.Vriend, C.Sander and E.E.Abola,
      Errors in protein structures
    Nature 381, 272 (1996).
    (see also http://swift.cmbi.ru.nl/gv/whatcheck for a course and extra
    information)
 
PDB facilities
    Touw WG, Baakman C, Black J, te Beek TA, Krieger E, Joosten RP, Vriend G.
      A series of PDB-related databanks for everyday needs.
    Nucleic Acids Research D364-368 Database issue (2015).
 
Bond lengths and angles, protein residues
    R.Engh and R.Huber,
      Accurate bond and angle parameters for X-ray protein structure
      refinement,
    Acta Crystallogr. A47, 392--400 (1991) and
    R.Engh and R.Huber,
    International Tables for Crystallography (2001)
 
 
Bond lengths and angles, DNA/RNA
    G.Parkinson, J.Voitechovsky, L.Clowney, A.T.Bruenger and H.Berman,
      New parameters for the refinement of nucleic acid-containing structures
    Acta Crystallogr. D52, 57--64 (1996).
 
DSSP
    W.Kabsch and C.Sander,
      Dictionary of protein secondary structure: pattern
      recognition of hydrogen bond and geometrical features
    Biopolymers 22, 2577--2637 (1983).
 
Hydrogen bond networks
    R.W.W.Hooft, C.Sander and G.Vriend,
      Positioning hydrogen atoms by optimizing hydrogen bond networks in
      protein structures
    PROTEINS, 26, 363--376 (1996).
 
Matthews' Coefficient
    B.W.Matthews
      Solvent content of Protein Crystals
    J. Mol. Biol. 33, 491--497 (1968).
 
Peptide flips
    Touw WG, Joosten RP, Vriend G.
      Detection of trans-cis flips and peptide-plane flips in protein
      structures.
    Acta Crystallogr D Biological Crystallograhy 71, 1604-1614 (2015).
 
Protein side chain planarity
    R.W.W. Hooft, C. Sander and G. Vriend,
      Verification of protein structures: side-chain planarity
    J. Appl. Cryst. 29, 714--716 (1996).
 
Puckering parameters
    D.Cremer and J.A.Pople,
      A general definition of ring puckering coordinates
    J. Am. Chem. Soc. 97, 1354--1358 (1975).
 
Quality Control
    G.Vriend and C.Sander,
      Quality control of protein models: directional atomic
      contact analysis,
    J. Appl. Cryst. 26, 47--60 (1993).
 
Ramachandran plot
    G.N.Ramachandran, C.Ramakrishnan and V.Sasisekharan,
      Stereochemistry of Polypeptide Chain Conformations
    J. Mol. Biol. 7, 95--99 (1963).
    R.W.W. Hooft, C.Sander and G.Vriend,
      Objectively judging the quality of a protein structure from a
      Ramachandran plot
    CABIOS (1997), 13, 425--430.
 
Symmetry Checks
    R.W.W.Hooft, C.Sander and G.Vriend,
      Reconstruction of symmetry related molecules from protein
      data bank (PDB) files
    J. Appl. Cryst. 27, 1006--1009 (1994).
 
Tau angle
    W.G.Touw and G.Vriend
      On the complexity of Engh and Huber refinement restraints: the angle
      tau as example.
    Acta Crystallogr D 66, 1341--1350 (2010).
 
Ion Checks
    I.D.Brown and K.K.Wu,
      Empirical Parameters for Calculating Cation-Oxygen Bond Valences
    Acta Cryst. B32, 1957--1959 (1975).
 
    M.Nayal and E.Di Cera,
      Valence Screening of Water in Protein Crystals Reveals Potential Na+
      Binding Sites
    J.Mol.Biol. 256 228--234 (1996).
 
    P.Mueller, S.Koepke and G.M.Sheldrick,
      Is the bond-valence method able to identify metal atoms in protein
      structures?
    Acta Cryst. D 59 32--37 (2003).
 
Checking checks
    K.Wilson, C.Sander, R.W.W.Hooft, G.Vriend, et al.
      Who checks the checkers
    J.Mol.Biol. (1998) 276,417-436.
==============
 
 
WHAT IF
    G.Vriend,
      WHAT IF: a molecular modelling and drug design program,
    J. Mol. Graph. 8, 52--56 (1990).
 
WHAT_CHECK (verification routines from WHAT IF)
    R.W.W.Hooft, G.Vriend, C.Sander and E.E.Abola,
      Errors in protein structures
    Nature 381, 272 (1996).
    (see also http://swift.cmbi.ru.nl/gv/whatcheck for a course and extra
    information)
 
PDB facilities
    Touw WG, Baakman C, Black J, te Beek TA, Krieger E, Joosten RP, Vriend G.
      A series of PDB-related databanks for everyday needs.
    Nucleic Acids Research D364-368 Database issue (2015).
 
Bond lengths and angles, protein residues
    R.Engh and R.Huber,
      Accurate bond and angle parameters for X-ray protein structure
      refinement,
    Acta Crystallogr. A47, 392--400 (1991) and
    R.Engh and R.Huber,
    International Tables for Crystallography (2001)
 
 
Bond lengths and angles, DNA/RNA
    G.Parkinson, J.Voitechovsky, L.Clowney, A.T.Bruenger and H.Berman,
      New parameters for the refinement of nucleic acid-containing structures
    Acta Crystallogr. D52, 57--64 (1996).
 
DSSP
    W.Kabsch and C.Sander,
      Dictionary of protein secondary structure: pattern
      recognition of hydrogen bond and geometrical features
    Biopolymers 22, 2577--2637 (1983).
 
Hydrogen bond networks
    R.W.W.Hooft, C.Sander and G.Vriend,
      Positioning hydrogen atoms by optimizing hydrogen bond networks in
      protein structures
    PROTEINS, 26, 363--376 (1996).
 
Matthews' Coefficient
    B.W.Matthews
      Solvent content of Protein Crystals
    J. Mol. Biol. 33, 491--497 (1968).
 
Peptide flips
    Touw WG, Joosten RP, Vriend G.
      Detection of trans-cis flips and peptide-plane flips in protein
      structures.
    Acta Crystallogr D Biological Crystallograhy 71, 1604-1614 (2015).
 
Protein side chain planarity
    R.W.W. Hooft, C. Sander and G. Vriend,
      Verification of protein structures: side-chain planarity
    J. Appl. Cryst. 29, 714--716 (1996).
 
Puckering parameters
    D.Cremer and J.A.Pople,
      A general definition of ring puckering coordinates
    J. Am. Chem. Soc. 97, 1354--1358 (1975).
 
Quality Control
    G.Vriend and C.Sander,
      Quality control of protein models: directional atomic
      contact analysis,
    J. Appl. Cryst. 26, 47--60 (1993).
 
Ramachandran plot
    G.N.Ramachandran, C.Ramakrishnan and V.Sasisekharan,
      Stereochemistry of Polypeptide Chain Conformations
    J. Mol. Biol. 7, 95--99 (1963).
    R.W.W. Hooft, C.Sander and G.Vriend,
      Objectively judging the quality of a protein structure from a
      Ramachandran plot
    CABIOS (1997), 13, 425--430.
 
Symmetry Checks
    R.W.W.Hooft, C.Sander and G.Vriend,
      Reconstruction of symmetry related molecules from protein
      data bank (PDB) files
    J. Appl. Cryst. 27, 1006--1009 (1994).
 
Tau angle
    W.G.Touw and G.Vriend
      On the complexity of Engh and Huber refinement restraints: the angle
      tau as example.
    Acta Crystallogr D 66, 1341--1350 (2010).
 
Ion Checks
    I.D.Brown and K.K.Wu,
      Empirical Parameters for Calculating Cation-Oxygen Bond Valences
    Acta Cryst. B32, 1957--1959 (1975).
 
    M.Nayal and E.Di Cera,
      Valence Screening of Water in Protein Crystals Reveals Potential Na+
      Binding Sites
    J.Mol.Biol. 256 228--234 (1996).
 
    P.Mueller, S.Koepke and G.M.Sheldrick,
      Is the bond-valence method able to identify metal atoms in protein
      structures?
    Acta Cryst. D 59 32--37 (2003).
 
Checking checks
    K.Wilson, C.Sander, R.W.W.Hooft, G.Vriend, et al.
      Who checks the checkers
    J.Mol.Biol. (1998) 276,417-436.
