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

Date : 2025-03-01
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/6vw1/wctemp_0cyc/6vw1_0cyc.pdb     ====
=========================================
 
# 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                                                        6VW1
ATOM  *****  O1  EDO A 706     114.170  24.238 144.883  1.00105.99       O1  O
ATOM  *****  C2  EDO A 706     115.625  25.543 146.302  1.00111.19       C2  C
ATOM  *****  O2  EDO A 706     114.708  26.639 146.211  1.00113.46       O2  O
ATOM  *****  O   HOH A 802      81.353 -24.927 150.954  1.00106.85       802 O
ATOM  *****  O   HOH A 803     110.400 -11.340 159.535  1.00 86.65       803 O
ATOM  *****  O   HOH A 804      97.605   1.792 167.866  1.00 78.41       804 O
ATOM  *****  O   HOH A 805     119.772   6.468 156.170  1.00 63.49       805 O
ATOM  *****  O   HOH A 806     122.860  -7.322 159.340  1.00 66.57       806 O
ATOM  *****  O   HOH A 807     116.554  -1.451 154.961  1.00 67.03       807 O
ATOM  *****  O   HOH A 808     105.267   1.508 162.436  1.00 75.84       808 O
ATOM  *****  O   HOH A 809     116.870   0.043 171.206  1.00 79.93       809 O
ATOM  *****  O   HOH A 810      85.080 -21.078 151.975  1.00 93.74       810 O
ATOM  *****  O   HOH A 811     119.552  15.127 158.296  1.00 76.86       811 O
ATOM  *****  O   HOH A 812     107.967   0.073 167.292  1.00 82.02       812 O
ATOM  *****  O   HOH A 813      87.305  -7.228 171.600  1.00 92.17       813 O
ATOM  *****  O   HOH E 702      72.786 -10.992 177.172  1.00 67.33       702 O
ATOM  *****  O   HOH E 703      71.585 -11.847 186.262  1.00 60.44       703 O
ATOM  *****  O   HOH E 704      56.660  13.568 197.024  1.00106.07       704 O
ATOM  *****  O1  EDO B 705      55.529  32.759 134.997  1.00 92.09       O1  O
ATOM  *****  C2  EDO B 705      54.158  31.524 133.434  1.00 93.89       C2  C
ATOM  *****  O2  EDO B 705      52.826  31.047 133.205  1.00 90.23       O2  O
ATOM  *****  O1  EDO B 706      92.981  27.317 119.303  1.00108.71       O1  O
ATOM  *****  C2  EDO B 706      92.649  29.277 117.933  1.00108.66       C2  C
ATOM  *****  O2  EDO B 706      93.249  30.539 117.620  1.00108.62       O2  O
ATOM  *****  O1  EDO B 707      58.279  19.437 143.233  1.00 81.97       O1  O
ATOM  *****  C2  EDO B 707      58.906  18.169 145.191  1.00 94.25       C2  C
ATOM  *****  O2  EDO B 707      59.468  16.925 145.627  1.00 99.61       O2  O
ATOM  *****  O   HOH B 802      72.855  28.139 112.336  1.00102.40       802 O
ATOM  *****  O   HOH B 803      83.130  25.334 109.352  1.00 75.56       803 O
ATOM  *****  O   HOH B 804      66.053  57.020 123.955  1.00116.90       804 O
ATOM  *****  O   HOH B 805      77.505  49.017 137.011  1.00 77.87       805 O
ATOM  *****  O   HOH B 806      71.964  26.131 128.510  1.00 73.09       806 O
ATOM  *****  O   HOH B 807      71.450  27.256 134.953  1.00 80.05       807 O
ATOM  *****  O   HOH B 808      81.184  37.895 104.815  1.00 79.14       808 O
ATOM  *****  C2  BMA C   3      65.513 -10.187 164.205  1.00164.51       C2  C
ATOM  *****  C3  BMA C   3      64.912  -8.784 164.326  1.00164.84       C3  C
ATOM  *****  C4  BMA C   3      65.353  -8.085 165.626  1.00165.75       C4  C
ATOM  *****  C5  BMA C   3      66.886  -8.117 165.760  1.00164.34       C5  C
ATOM  *****  C6  BMA C   3      67.377  -7.517 167.067  1.00159.95       C6  C
ATOM  *****  O2  BMA C   3      64.864 -10.998 165.174  1.00162.15       O2  O
ATOM  *****  O3  BMA C   3      63.491  -8.819 164.251  1.00162.71       O3  O
ATOM  *****  O4  BMA C   3      64.902  -6.737 165.632  1.00164.99       O4  O
ATOM  *****  O5  BMA C   3      67.321  -9.489 165.704  1.00164.63       O5  O
ATOM  *****  O6  BMA C   3      66.718  -6.271 167.265  1.00154.88       O6  O
ATOM  *****  C2  BMA D   3      84.285  32.236 170.024  1.00171.72       C2  C
ATOM  *****  C3  BMA D   3      84.288  33.779 170.118  1.00172.94       C3  C
ATOM  *****  C4  BMA D   3      85.431  34.413 169.304  1.00172.72       C4  C
ATOM  *****  C5  BMA D   3      85.375  33.893 167.870  1.00169.55       C5  C
ATOM  *****  C6  BMA D   3      86.436  34.506 166.966  1.00162.14       C6  C
ATOM  *****  O2  BMA D   3      85.307  31.767 170.892  1.00170.11       O2  O
ATOM  *****  O3  BMA D   3      84.353  34.222 171.470  1.00171.79       O3  O
ATOM  *****  O4  BMA D   3      85.313  35.829 169.305  1.00172.07       O4  O
ATOM  *****  O5  BMA D   3      85.583  32.479 167.928  1.00171.13       O5  O
ATOM  *****  O6  BMA D   3      87.669  34.543 167.675  1.00158.17       O6  O
ATOM  *****  C2  BMA J   3      91.340  32.004 145.596  1.00133.56       C2  C
ATOM  *****  C3  BMA J   3      91.018  32.682 146.941  1.00138.67       C3  C
ATOM  *****  C4  BMA J   3      91.480  34.164 147.020  1.00139.95       C4  C
ATOM  *****  C5  BMA J   3      91.200  34.929 145.712  1.00142.09       C5  C
ATOM  *****  C6  BMA J   3      91.803  36.330 145.714  1.00143.19       C6  C
ATOM  *****  O2  BMA J   3      92.684  31.548 145.680  1.00130.38       O2  O
ATOM  *****  O3  BMA J   3      91.616  31.938 148.012  1.00140.46       O3  O
ATOM  *****  O4  BMA J   3      90.814  34.820 148.092  1.00135.76       O4  O
ATOM  *****  O5  BMA J   3      91.777  34.199 144.626  1.00138.87       O5  O
ATOM  *****  O6  BMA J   3      91.507  36.959 144.472  1.00141.93       O6  O
ATOM  *****  C2  BMA L   3      61.595  14.745 199.791  1.00153.50       C2  C
ATOM  *****  C3  BMA L   3      60.856  16.075 199.669  1.00151.85       C3  C
ATOM  *****  C4  BMA L   3      59.319  15.855 199.611  1.00151.34       C4  C
ATOM  *****  C5  BMA L   3      58.842  14.998 200.808  1.00148.59       C5  C
ATOM  *****  C6  BMA L   3      57.355  14.695 200.774  1.00144.55       C6  C
ATOM  *****  O2  BMA L   3      61.360  14.084 198.559  1.00151.37       O2  O
ATOM  *****  O3  BMA L   3      61.285  16.818 198.532  1.00148.34       O3  O
ATOM  *****  O4  BMA L   3      58.641  17.102 199.621  1.00152.28       O4  O
ATOM  *****  O5  BMA L   3      59.575  13.754 200.804  1.00151.52       O5  O
ATOM  *****  O6  BMA L   3      56.650  15.931 200.795  1.00142.83       O6  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:
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                                                        6VW1
 
# 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.012432  0.000000  0.000678
  0.000000  0.008472  0.000000
  0.000000  0.000000  0.008936
 
# 5 # Note: Non crystallographic symmetry RMS plot
The plot shows the RMS differences between two similar chains on a residue-
by-residue basis. Individual "spikes" can be indicative of interesting or
wrong residues. If all residues show a high RMS value, the structure could
be incorrectly refined.
 
In the TeX file, a plot has been inserted here
 
Chain identifiers of the two chains: A and B
 
 All-atom RMS fit for the two chains : 1.343
 CA-only RMS fit for the two chains : 1.254
 
# 6 # Note: Non crystallographic symmetry backbone difference plot
The plot shows the differences in backbone torsion angles between two
similar chains on a residue-by-residue basis. Individual "spikes" can be
indicative of interesting or wrong residues. If all residues show high
differences, the structure could be incorrectly refined.
 
In the TeX file, a plot has been inserted here
 
Chain identifiers of the two chains: A and B
 
# 7 # Note: Non crystallographic symmetry RMS plot
The plot shows the RMS differences between two similar chains on a residue-
by-residue basis. Individual "spikes" can be indicative of interesting or
wrong residues. If all residues show a high RMS value, the structure could
be incorrectly refined.
 
In the TeX file, a plot has been inserted here
 
Chain identifiers of the two chains: E and F
 
 All-atom RMS fit for the two chains : 0.976
 CA-only RMS fit for the two chains : 0.567
 
# 8 # Note: Non crystallographic symmetry backbone difference plot
The plot shows the differences in backbone torsion angles between two
similar chains on a residue-by-residue basis. Individual "spikes" can be
indicative of interesting or wrong residues. If all residues show high
differences, the structure could be incorrectly refined.
 
In the TeX file, a plot has been inserted here
 
Chain identifiers of the two chains: E and F
 
# 9 # 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 1 21 1
 Number of matrices in space group: 2
 Highest polymer chain multiplicity in structure: 2
 Highest polymer chain multiplicity according to SEQRES: 2
 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
 
# 10 # 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: 181480.281
 Volume of the Unit Cell V= 1062470.1
 Space group multiplicity: 2
 No NCS symmetry matrices (MTRIX records) found in PDB file
 Matthews coefficient for observed atoms and Z is high: Vm= 11.709
 A few residues have missing atoms that did not enter the Vm calculation
 No Matthews coefficient given in REMARK 280
 Or should we use the previously suggested Z = 4
 which would result in Vm= 2.927
 And remember, a matrix counting problem has been reported earlier already
 
# 11 # Note: Z missing on CRYST1 card
The messages above seem likely caused by the fact that Z is missing from the
CRYST1 card.
 
# 12 # 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.
 
# 13 # 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.
 
# 14 # 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.
 
 1610 BMA  (   3-) C  -
 1611 BMA  (   3-) D  -
 1612 BMA  (   3-) J  -
 1613 BMA  (   3-) L  -
 
# 15 # Warning: Covalently bound ligands
The ligands in this table are covalently bound to something else. It is
already difficult to automatically generate topologies for ligands,
but when they are covalently bound to something it becomes even more
complicated to do everything right. So, if you get weird error messages
that seem related to this covalent bond, then please feel free to
ignore those, or even better, make a topology entry by hand.
 
The comment `Other ligand` indicates that the covalent bond is to another
ligand. In that case you might want to convert the two ligands into one
bigger ligand.
 
 1610 BMA  (   3-) C  -
 1611 BMA  (   3-) D  -
 1612 BMA  (   3-) J  -
 1613 BMA  (   3-) L  -
 
# 16 # Note: No strange inter-chain connections detected
No covalent bonds have been detected between molecules with non-identical
chain identifiers.
 
# 17 # Note: No duplicate atom names in ligands
All atom names in ligands (if any) seem adequately unique.
 
# 18 # 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).
 
# 19 # 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).
 
# 20 # Warning: Groups attached to potentially hydrogen-bonding atoms
Residues were observed with groups attached to (or very near to) atoms that
potentially can form hydrogen bonds. WHAT CHECK is not very good at dealing
with such exceptional cases (Mainly because it's author is not...). So be
warned that the hydrogen-bonding related analyses of these residues
might be in error.
 
For example, an aspartic acid can be protonated on one of its delta
oxygens. This is possible because the one delta oxygen 'helps' the
other one holding that proton. However, if a delta oxygen has a group
bound to it, then it can no longer 'help' the other delta oxygen
bind the proton. However, both delta oxygens, in principle, can still
be hydrogen bond acceptors. Such problems can occur in the amino acids
Asp, Glu, and His. I have opted, for now to simply allow no hydrogen
bonds at all for any atom in any side chain that somewhere has a 'funny'
group attached to it. I know this is wrong, but there are only 12 hours
in a day.
 
 1584 NAG  (   2-) C  -    O4  bound to  1610 BMA  (   3-) C  -    C1
 1586 NAG  (   2-) D  -    O4  bound to  1611 BMA  (   3-) D  -    C1
 1594 NAG  (   2-) J  -    O4  bound to  1612 BMA  (   3-) J  -    C1
 1599 NAG  (   2-) L  -    O4  bound to  1613 BMA  (   3-) L  -    C1
 
# 21 # 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.
 
# 22 # 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.
 
# 23 # Note: All residues have a complete backbone.
No residues have missing backbone atoms.
 
# 24 # Note: No C-alpha only residues
There are no residues that consist of only an alpha carbon atom.
 
# 25 # 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 (   19)   596 (  614) A Protein             /zata/tempdir/6vw...
     2   597 (  714)   597 (  714) A Sugar               /zata/tempdir/6vw...
     3   598 (  334)   785 (  521) E Protein             /zata/tempdir/6vw...
     4   786 (  523)   790 (  527) E Protein             /zata/tempdir/6vw...
     5   791 (   19)  1386 (  614) B Protein             /zata/tempdir/6vw...
     6  1387 (  714)  1387 (  714) B Sugar               /zata/tempdir/6vw...
     7  1388 (  715)  1388 (  715) B Sugar               /zata/tempdir/6vw...
     8  1389 (  331)  1574 (  516) F Protein             /zata/tempdir/6vw...
     9  1575 (  520)  1582 (  527) F Protein             /zata/tempdir/6vw...
    10  1583 (    1)  1583 (    1) C Sugar               /zata/tempdir/6vw...
    11  1584 (    2)  1584 (    2) C Sugar<-             /zata/tempdir/6vw...
    12  1585 (    1)  1585 (    1) D Sugar               /zata/tempdir/6vw...
    13  1586 (    2)  1586 (    2) D Sugar<-             /zata/tempdir/6vw...
    14  1587 (    1)  1587 (    1) G Sugar               /zata/tempdir/6vw...
    15  1588 (    2)  1588 (    2) G Sugar               /zata/tempdir/6vw...
And so on for a total of    44 lines.
MODELs skipped upon reading PDB file: 0
X-ray structure. No MODELs found
The total number of amino acids found is 1579
of which 1062 have poor or (essentially) missing atoms
No nucleic acids observed in input file
Number of (recognized) sugars: 22
of which 22 have poor or (essentially) missing atoms
Number of water molecules: 4
Residue numbers increase monotonously OK
 
# 26 # Note: Chain identifiers seem OK
All ions seem to have a logical chain identifier, or there are no ions
present in the input file.
ERROR. File not found:
TAPEOUT.DAT
ERROR. File not found:
TAPEOUT.DAT
ERROR. File not found:
TAPEOUT.DAT
ERROR. File not found:
TAPEOUT.DAT
ERROR. File not found:
TAPEOUT.DAT
 
# 27 # 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: E
 
# 28 # Note: Ramachandran plot
 
 
In the TeX file, a plot has been inserted here
 
Chain identifier: F
 
# 29 # 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 STIEEQAKTFLDKFNHEAEDLFYQSSLASWNYNTNITEENVQNMNNAGDKWSAFLKEQST
(  19)-(  78)
                     70        80        90       100       110       120
                      |         |         |         |         |         |
   61 -  120 LAQMYPLQEIQNLTVKLQLQALQQNGSSVLSEDKSKRLNTILNTMSTIYSTGKVCNPDNP
(  79)-( 138)
                    130       140       150       160       170       180
                      |         |         |         |         |         |
  121 -  180 QECLLLEPGLNEIMANSLDYNERLWAWESWRSEVGKQLRPLYEEYVVLKNEMARANHYED
( 139)-( 198)
                    190       200       210       220       230       240
                      |         |         |         |         |         |
  181 -  240 YGDYWRGDYEVNGVDGYDYSRGQLIEDVEHTFEEIKPLYEHLHAYVRAKLMNAYPSYISP
( 199)-( 258)
                    250       260       270       280       290       300
                      |         |         |         |         |         |
  241 -  300 IGCLPAHLLGDMWGRFWTNLYSLTVPFGQKPNIDVTDAMVDQAWDAQRIFKEAEKFFVSV
( 259)-( 318)
                    310       320       330       340       350       360
                      |         |         |         |         |         |
  301 -  360 GLPNMTQGFWENSMLTDPGNVQKAVCHPTAWDLGKGDFRILMCTKVTMDDFLTAHHEMGH
( 319)-( 378)
                    370       380       390       400       410       420
                      |         |         |         |         |         |
  361 -  420 IQYDMAYAAQPFLLRNGANEGFHEAVGEIMSLSAATPKHLKSIGLLSPDFQEDNETEINF
( 379)-( 438)
                    430       440       450       460       470       480
                      |         |         |         |         |         |
  421 -  480 LLKQALTIVGTLPFTYMLEKWRWMVFKGEIPKDQWMKKWWEMKREIVGVVEPVPHDETYC
( 439)-( 498)
                    490       500       510       520       530       540
                      |         |         |         |         |         |
  481 -  540 DPASLFHVSNDYSFIRYYTRTLYQFQFQEALCQAAKHEGPLHKCDISNSTEAGQKLFNML
( 499)-( 558)
                    550       560       570       580       590
                      |         |         |         |         |
  541 -  596 RLGKSEPWTLALENVVGAKNMNVRPLLNYFEPLFTWLKDQNKNSFVGWSTDWSPYA
( 559)-( 614)
             600       610       620       630       640       650
               |         |         |         |         |         |
  598 -  657 NLCPFGEVFNATKFPSVYAWERKKISNCVADYSVLYNSTFFSTFKCYGVSATKLNDLCFS
( 334)-( 393)
             660       670       680       690       700       710
               |         |         |         |         |         |
  658 -  717 NVYADSFVVKGDDVRQIAPGQTGVIADYNYKLPDDFMGCVLAWNTRNIDATSTGNYNYKY
( 394)-( 453)
             720       730       740       750       760       770
               |         |         |         |         |         |
  718 -  777 RLFRKSNLKPFERDISTEIYQAGSTPCNGVEGFNCYFPLQSYGFQPTNGVGYQPYRVVVL
( 454)-( 513)
             780
               |
  778 -  785 SFELLNAP
( 514)-( 521)
               790
                 |
  786 -  790 TVCGP
( 523)-( 527)
                    800       810       820       830       840       850
                      |         |         |         |         |         |
  791 -  850 STIEEQAKTFLDKFNHEAEDLFYQSSLASWNYNTNITEENVQNMNNAGDKWSAFLKEQST
(  19)-(  78)
                    860       870       880       890       900       910
                      |         |         |         |         |         |
  851 -  910 LAQMYPLQEIQNLTVKLQLQALQQNGSSVLSEDKSKRLNTILNTMSTIYSTGKVCNPDNP
(  79)-( 138)
                    920       930       940       950       960       970
                      |         |         |         |         |         |
  911 -  970 QECLLLEPGLNEIMANSLDYNERLWAWESWRSEVGKQLRPLYEEYVVLKNEMARANHYED
( 139)-( 198)
                    980       990      1000      1010      1020      1030
                      |         |         |         |         |         |
  971 - 1030 YGDYWRGDYEVNGVDGYDYSRGQLIEDVEHTFEEIKPLYEHLHAYVRAKLMNAYPSYISP
( 199)-( 258)
                   1040      1050      1060      1070      1080      1090
                      |         |         |         |         |         |
 1031 - 1090 IGCLPAHLLGDMWGRFWTNLYSLTVPFGQKPNIDVTDAMVDQAWDAQRIFKEAEKFFVSV
( 259)-( 318)
                   1100      1110      1120      1130      1140      1150
                      |         |         |         |         |         |
 1091 - 1150 GLPNMTQGFWENSMLTDPGNVQKAVCHPTAWDLGKGDFRILMCTKVTMDDFLTAHHEMGH
( 319)-( 378)
                   1160      1170      1180      1190      1200      1210
                      |         |         |         |         |         |
 1151 - 1210 IQYDMAYAAQPFLLRNGANEGFHEAVGEIMSLSAATPKHLKSIGLLSPDFQEDNETEINF
( 379)-( 438)
                   1220      1230      1240      1250      1260      1270
                      |         |         |         |         |         |
 1211 - 1270 LLKQALTIVGTLPFTYMLEKWRWMVFKGEIPKDQWMKKWWEMKREIVGVVEPVPHDETYC
( 439)-( 498)
                   1280      1290      1300      1310      1320      1330
                      |         |         |         |         |         |
 1271 - 1330 DPASLFHVSNDYSFIRYYTRTLYQFQFQEALCQAAKHEGPLHKCDISNSTEAGQKLFNML
( 499)-( 558)
                   1340      1350      1360      1370      1380
                      |         |         |         |         |
 1331 - 1386 RLGKSEPWTLALENVVGAKNMNVRPLLNYFEPLFTWLKDQNKNSFVGWSTDWSPYA
( 559)-( 614)
           1390      1400      1410      1420      1430      1440
              |         |         |         |         |         |
 1389 - 1448 NITNLCPFGEVFNATKFPSVYAWERKKISNCVADYSVLYNSTFFSTFKCYGVSATKLNDL
( 331)-( 390)
           1450      1460      1470      1480      1490      1500
              |         |         |         |         |         |
 1449 - 1508 CFSNVYADSFVVKGDDVRQIAPGQTGVIADYNYKLPDDFMGCVLAWNTRNIDATSTGNYN
( 391)-( 450)
           1510      1520      1530      1540      1550      1560
              |         |         |         |         |         |
 1509 - 1568 YKYRLFRKSNLKPFERDISTEIYQAGSTPCNGVEGFNCYFPLQSYGFQPTNGVGYQPYRV
( 451)-( 510)
           1570
              |
 1569 - 1574 VVLSFE
( 511)-( 516)
               1580
                  |
 1575 - 1582 APATVCGP
( 520)-( 527)
 
 
 
 
# 30 # Note: No rounded coordinates detected
No significant rounding of atom coordinates has been detected.
 
# 31 # 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.
 
# 32 # Warning: Missing atoms
The atoms listed in the table below are missing from the entry. If many atoms
are missing, the other checks can become less sensitive. Be aware that it
often happens that groups at the termini of DNA or RNA are really missing,
so that the absence of these atoms normally is neither an error nor the
result of poor electron density. Some of the atoms listed here might also be
listed by other checks, most noticeably by the options in the previous
section that list missing atoms in several categories. The plausible atoms
with zero occupancy are not listed here, as they already got assigned a
non-zero occupancy, and thus are no longer 'missing'.
 
  610 LYS  ( 346-) E  -    CG
  610 LYS  ( 346-) E  -    CD
  610 LYS  ( 346-) E  -    CE
  610 LYS  ( 346-) E  -    NZ
 1404 LYS  ( 346-) F  -    CG
 1404 LYS  ( 346-) F  -    CD
 1404 LYS  ( 346-) F  -    CE
 1404 LYS  ( 346-) F  -    NZ
 
# 33 # 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.
 
    1 SER  (  19-) A  -   High
    2 THR  (  20-) A  -   High
    3 ILE  (  21-) A  -   High
    4 GLU  (  22-) A  -   High
    5 GLU  (  23-) A  -   High
    6 GLN  (  24-) A  -   High
    7 ALA  (  25-) A  -   High
    8 LYS  (  26-) A  -   High
    9 THR  (  27-) A  -   High
   10 PHE  (  28-) A  -   High
   11 LEU  (  29-) A  -   High
   12 ASP  (  30-) A  -   High
   13 LYS  (  31-) A  -   High
   15 ASN  (  33-) A  -   High
   16 HIS  (  34-) A  -   High
And so on for a total of  1082 lines.
 
# 34 # 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.
 
  596 ALA  ( 614-) A  -        OK
  785 PRO  ( 521-) E  -        OK (1)
  790 PRO  ( 527-) E  -        OK
 1386 ALA  ( 614-) B  -        OK
 1574 GLU  ( 516-) F  -        OK (3)
 1582 PRO  ( 527-) F  -        OK
 
# 35 # Note: Weights administratively correct
All atomic occupancy factors ('weights') fall in the 0.0--1.0 range, which
makes them administratively correct.
 
# 36 # 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.
 
# 37 # Note: All occupancies seem to add up to 0.0 - 1.0.
In principle, the occupancy of all alternates of one atom should add up till
0.0 - 1.0. 0.0 is used for the missing atom (i.e. an atom not seen in the
electron density). Obviously, there is nothing terribly wrong when a few
occupancies add up to a bit more than 1.0, because the mathematics of
refinement allow for that. However, if it happens often, it seems worth
evaluating this in light of the refinement protocol used.
 
# 38 # 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
 
# 39 # 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
 
# 40 # Note: B-factor distribution normal
The distribution of B-factors within residues is within expected ranges.
A value over 1.5 here would mean that the B-factors show signs of
over-refinement.
 
RMS Z-score :  0.762 over    5163 bonds
Average difference in B over a bond :    3.23
RMS difference in B over a bond :    4.15
 
# 41 # 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: E
 
# 42 # Note: B-factor plot
 
 
In the TeX file, a plot has been inserted here
 
Chain identifier: F
 
# 43 # 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.
 
# 44 # Note: Valine nomenclature OK
No errors were detected in valine nomenclature.
 
# 45 # Note: Threonine nomenclature OK
No errors were detected in threonine nomenclature.
 
# 46 # Note: Isoleucine nomenclature OK
No errors were detected in isoleucine nomenclature.
 
# 47 # Note: Leucine nomenclature OK
No errors were detected in leucine nomenclature.
 
# 48 # Warning: Arginine nomenclature problem
The arginine residues listed in the table below have their NH1 and NH2
swapped.
 
   97 ARG  ( 115-) A  -
  151 ARG  ( 169-) A  -
  159 ARG  ( 177-) A  -
  174 ARG  ( 192-) A  -
  227 ARG  ( 245-) A  -
  255 ARG  ( 273-) A  -
  339 ARG  ( 357-) A  -
  500 ARG  ( 518-) A  -
  887 ARG  ( 115-) B  -
  941 ARG  ( 169-) B  -
  949 ARG  ( 177-) B  -
  964 ARG  ( 192-) B  -
 1017 ARG  ( 245-) B  -
 1045 ARG  ( 273-) B  -
 1129 ARG  ( 357-) B  -
 1290 ARG  ( 518-) B  -
 
# 49 # Note: Tyrosine torsion conventions OK
No errors were detected in tyrosine torsion angle conventions.
 
# 50 # Note: Phenylalanine torsion conventions OK
No errors were detected in phenylalanine torsion angle conventions.
 
# 51 # Note: Aspartic acid torsion conventions OK
No errors were detected in aspartic acid torsion angle conventions.
 
# 52 # Note: Glutamic acid torsion conventions OK
No errors were detected in glutamic acid torsion angle conventions.
 
# 53 # 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).
 
# 54 # 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.
 
# 55 # Note: No decreasing residue numbers
All residue numbers are strictly increasing within each chain.
 
# 56 # 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]).
 
# 57 # 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.214
 RMS-deviation in bond distances: 0.006
 
# 58 # 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.
 
# 59 # 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.
 
  442 ARG  ( 460-) A  -    CB   CG   CD  105.39   -4.4
 
# 60 # 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.538
 RMS-deviation in bond angles: 1.119
 
# 61 # Error: Nomenclature error(s)
Checking for a hand-check. WHAT CHECK has over the course of this session
already corrected the handedness of atoms in several residues. These were
administrative corrections. These residues are listed here.
 
   97 ARG  ( 115-) A  -
  151 ARG  ( 169-) A  -
  159 ARG  ( 177-) A  -
  174 ARG  ( 192-) A  -
  227 ARG  ( 245-) A  -
  255 ARG  ( 273-) A  -
  339 ARG  ( 357-) A  -
  500 ARG  ( 518-) A  -
  887 ARG  ( 115-) B  -
  941 ARG  ( 169-) B  -
  949 ARG  ( 177-) B  -
  964 ARG  ( 192-) B  -
 1017 ARG  ( 245-) B  -
 1045 ARG  ( 273-) B  -
 1129 ARG  ( 357-) B  -
 1290 ARG  ( 518-) B  -
 
# 62 # Note: Chirality OK
All protein atoms have proper chirality. But, look at the previous table to
see a series of administrative chirality problems that were corrected
automatically upon reading-in the PDB file.
The average deviation= 0.395
 
# 63 # 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.344
 
# 64 # Note: Tau angles OK
All of the tau angles (N-C-alpha-C) of amino acids fall within expected
RMS deviations.
 
# 65 # 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.543
 
# 66 # Note: Side chain planarity OK
All of the side chains of residues that have an intact planar group are
planar within expected RMS deviations.
 
# 67 # 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.
 
# 68 # 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.028
 
# 69 # 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.
 
# 70 # 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.
 
 1435 PHE  ( 377-) F  -   -3.5
  641 PHE  ( 377-) E  -   -3.5
 1544 PHE  ( 486-) F  -   -2.9
  128 PRO  ( 146-) A  -   -2.8
  918 PRO  ( 146-) B  -   -2.8
  679 THR  ( 415-) E  -   -2.5
 1473 THR  ( 415-) F  -   -2.5
 1430 THR  ( 372-) F  -   -2.5
 1526 ILE  ( 468-) F  -   -2.4
  636 THR  ( 372-) E  -   -2.4
 1406 PRO  ( 348-) F  -   -2.3
  646 VAL  ( 382-) E  -   -2.3
 1440 VAL  ( 382-) F  -   -2.2
 1157 TYR  ( 385-) B  -   -2.2
  125 LEU  ( 143-) A  -   -2.2
And so on for a total of    34 lines.
 
# 71 # 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.
 
   65 TYR  (  83-) A  - Omega to (next) Pro poor
   86 GLY  ( 104-) A  - Poor phi/psi
  116 ASN  ( 134-) A  - Omega to (next) Pro poor
  119 ASN  ( 137-) A  - Omega to (next) Pro poor
  127 GLU  ( 145-) A  - Omega to (next) Pro poor
  159 ARG  ( 177-) A  - Omega to (next) Pro poor
  177 HIS  ( 195-) A  - Poor phi/psi
  193 GLY  ( 211-) A  - Poor phi/psi
  196 GLY  ( 214-) A  - Poor phi/psi
  216 LYS  ( 234-) A  - Omega to (next) Pro poor
  234 TYR  ( 252-) A  - Omega to (next) Pro poor
  236 SER  ( 254-) A  - Poor phi/psi
  239 SER  ( 257-) A  - Omega to (next) Pro poor
  244 LEU  ( 262-) A  - Omega to (next) Pro poor
  250 GLY  ( 268-) A  - Poor phi/psi
And so on for a total of   149 lines.
 
# 72 # 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.
 
   55 LEU  (  73-) A  -    -1.32
   61 LEU  (  79-) A  -    -1.32
   67 LEU  (  85-) A  -    -1.32
   77 LEU  (  95-) A  -    -1.32
   79 LEU  (  97-) A  -    -1.31
   82 LEU  ( 100-) A  -    -1.31
   90 LEU  ( 108-) A  -    -1.30
  125 LEU  ( 143-) A  -    -1.32
  333 LEU  ( 351-) A  -    -1.31
  373 LEU  ( 391-) A  -    -1.32
  374 LEU  ( 392-) A  -    -1.31
  392 LEU  ( 410-) A  -    -1.32
  422 LEU  ( 440-) A  -    -1.32
  540 LEU  ( 558-) A  -    -1.32
  542 LEU  ( 560-) A  -    -1.32
And so on for a total of   704 lines.
 
# 73 # Warning: chi-1/chi-2 angle correlation Z-score low
The score expressing how well the chi-1/chi-2 angles of all residues
correspond to the populated areas in the database is
a bit low.
 
 chi-1/chi-2 correlation Z-score : -3.477
 
# 74 # 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.
 
 1497 ARG  ( 439-) F  -   0.34
  393 SER  ( 411-) A  -   0.35
 1183 SER  ( 411-) B  -   0.35
  262 SER  ( 280-) A  -   0.38
  778 SER  ( 514-) E  -   0.38
  663 SER  ( 399-) E  -   0.38
  548 TRP  ( 566-) A  -   0.38
 1396 PHE  ( 338-) F  -   0.39
  489 SER  ( 507-) A  -   0.39
 1052 SER  ( 280-) B  -   0.39
 
# 75 # 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!
 
  127 GLU  ( 145-) A  -       0
  640 THR  ( 376-) E  -       0
  641 PHE  ( 377-) E  -       0
  875 ASN  ( 103-) B  -       0
  917 GLU  ( 145-) B  -       0
 1434 THR  ( 376-) F  -       0
 1435 PHE  ( 377-) F  -       0
 1544 PHE  ( 486-) F  -       0
   85 ASN  ( 103-) A  -       1
  335 LYS  ( 353-) A  -       1
  674 ILE  ( 410-) E  -       1
  723 SER  ( 459-) E  -       1
  750 PHE  ( 486-) E  -       1
 1125 LYS  ( 353-) B  -       1
 1418 ASN  ( 360-) F  -       1
 1468 ILE  ( 410-) F  -       1
 1541 VAL  ( 483-) F  -       1
  126 LEU  ( 144-) A  -       2
  379 ASN  ( 397-) A  -       2
  494 PHE  ( 512-) A  -       2
  624 ASN  ( 360-) E  -       2
  658 ASN  ( 394-) E  -       2
  916 LEU  ( 144-) B  -       2
 1116 CYS  ( 344-) B  -       2
 1132 MET  ( 360-) B  -       2
 1284 PHE  ( 512-) B  -       2
 1421 ALA  ( 363-) F  -       2
 1422 ASP  ( 364-) F  -       2
 1452 ASN  ( 394-) F  -       2
 1488 MET  ( 430-) F  -       2
 
# 76 # 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.046
 
# 77 # 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= 179.510 4.836
 
# 78 # Note: PRO puckering amplitude OK
Puckering amplitudes for all PRO residues are within normal ranges.
 
# 79 # 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].
 
  128 PRO  ( 146-) A  -  -60.0 half-chair C-beta/C-alpha (-54 degrees)
  160 PRO  ( 178-) A  -   51.2 half-chair C-delta/C-gamma (54 degrees)
  371 PRO  ( 389-) A  - -116.3 envelop C-gamma (-108 degrees)
  482 PRO  ( 500-) A  - -121.5 half-chair C-delta/C-gamma (-126 degrees)
  785 PRO  ( 521-) E  - -114.6 envelop C-gamma (-108 degrees)
  918 PRO  ( 146-) B  -  -59.7 half-chair C-beta/C-alpha (-54 degrees)
  950 PRO  ( 178-) B  -   51.3 half-chair C-delta/C-gamma (54 degrees)
 1161 PRO  ( 389-) B  - -116.5 envelop C-gamma (-108 degrees)
 1272 PRO  ( 500-) B  - -121.8 half-chair C-delta/C-gamma (-126 degrees)
 
# 80 # 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!
 
 1554 GLY  ( 496-) F  -  1.54   55
  760 GLY  ( 496-) E  -  1.51   38
 1505 GLY  ( 447-) F  -  1.50   12
 
# 81 # 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.
 
  177 HIS  ( 195-) A  - TT+   Highly likely
  367 TYR  ( 385-) A  - TT+   Highly likely
  641 PHE  ( 377-) E  - TT+   Highly likely
 1157 TYR  ( 385-) B  - TT+   Highly likely
 1318 ASN  ( 546-) B  - TT+   Highly likely
 1435 PHE  ( 377-) F  - TT+   Highly likely
   34 THR  (  52-) A  - TT+   Likely
   35 ASN  (  53-) A  - TT+   Likely
   69 GLU  (  87-) A  - TT+   Likely
   89 VAL  ( 107-) A  - TT+   Likely
  111 THR  ( 129-) A  - TT+   Likely
  112 GLY  ( 130-) A  - TT+   Likely
  119 ASN  ( 137-) A  - TT+   Likely
  136 ASN  ( 154-) A  - TT+   Likely
  154 VAL  ( 172-) A  - TT+   Likely
And so on for a total of   126 lines.
 
# 82 # Error: Abnormally short interatomic distances
The pairs of atoms listed in the table below have an unusually short
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.
 
The last text-item on each line represents the status of the atom pair. The
text `INTRA' means that the bump is between atoms that are explicitly listed
in the PDB file. `INTER' means it is an inter-symmetry bump. 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.
 
It seems likely that at least some of the reported bumps are caused by
administrative errors in the chain names. I.e. covalently bound atoms with
different non-blank chain-names are reported as bumps. In rare cases this is
not an error.
 
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.
 
   35 ASN  (  53-) A  -    ND2  <-->   1587 NAG  (   1-) G  -    C1   1.67    1.43  INTRA BF
 1318 ASN  ( 546-) B  -    ND2  <-->   1593 NAG  (   1-) J  -    C1   1.66    1.44  INTRA BF
  304 ASN  ( 322-) A  -    ND2  <-->   1589 NAG  (   1-) H  -    C1   1.66    1.44  INTRA BF
 1204 ASN  ( 432-) B  -    ND2  <-->   1387 NAG  ( 714-) B  -    C1   1.66    1.44  INTRA BF
  862 ASN  (  90-) B  -    ND2  <-->   1591 NAG  (   1-) I  -    C1   1.66    1.44  INTRA BF
  875 ASN  ( 103-) B  -    ND2  <-->   1388 NAG  ( 715-) B  -    C1   1.66    1.44  INTRA BF
 1094 ASN  ( 322-) B  -    ND2  <-->   1596 NAG  (   1-) K  -    C1   1.66    1.44  INTRA BF
   85 ASN  ( 103-) A  -    ND2  <-->    597 NAG  ( 714-) A  -    C1   1.66    1.44  INTRA BF
   72 ASN  (  90-) A  -    ND2  <-->   1583 NAG  (   1-) C  -    C1   1.66    1.44  INTRA BF
  607 ASN  ( 343-) E  -    ND2  <-->   1598 NAG  (   1-) L  -    C1   1.66    1.44  INTRA BF
 1401 ASN  ( 343-) F  -    ND2  <-->   1600 NAG  (   1-) M  -    C1   1.65    1.45  INTRA BF
  528 ASN  ( 546-) A  -    ND2  <-->   1585 NAG  (   1-) D  -    C1   1.65    1.45  INTRA BF
 1587 NAG  (   1-) G  -    O4   <-->   1588 NAG  (   2-) G  -    C1   1.16    1.44  INTRA BL
 1596 NAG  (   1-) K  -    O4   <-->   1597 NAG  (   2-) K  -    C1   1.16    1.44  INTRA BL
 1593 NAG  (   1-) J  -    O4   <-->   1594 NAG  (   2-) J  -    C1   1.15    1.45  INTRA BL
And so on for a total of   169 lines.
 
# 83 # 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: 68.877
Total bump value per residue: 0.106
Total number of bumps: 169
Total squared bump value: 63.917
Total number of bumps in the mildest bin: 85
Total number of bumps in the second bin: 31
Total number of bumps in the middle bin: 23
Total number of bumps in the fourth bin: 9
Total number of bumps in the worst bin: 21
 
# 84 # 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.
 
# 85 # 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.026
 
# 86 # 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: E
 
# 87 # Note: Inside/Outside RMS Z-score plot
 
 
In the TeX file, a plot has been inserted here
 
Chain identifier: F
 
# 88 # 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.
 
  722 LYS  ( 458-) E  -  -6.50
  269 GLN  ( 287-) A  -  -6.47
 1059 GLN  ( 287-) B  -  -6.45
  518 GLU  ( 536-) A  -  -5.87
 1516 LYS  ( 458-) F  -  -5.86
  595 TYR  ( 613-) A  -  -5.84
 1563 TYR  ( 505-) F  -  -5.84
 1308 GLU  ( 536-) B  -  -5.81
  769 TYR  ( 505-) E  -  -5.70
 1472 GLN  ( 414-) F  -  -5.67
 1165 ARG  ( 393-) B  -  -5.67
 1385 TYR  ( 613-) B  -  -5.57
 1544 PHE  ( 486-) F  -  -5.54
  783 ASN  ( 519-) E  -  -5.52
  678 GLN  ( 414-) E  -  -5.51
   84 GLN  ( 102-) A  -  -5.40
  375 ARG  ( 393-) A  -  -5.39
  127 GLU  ( 145-) A  -  -5.35
  874 GLN  ( 102-) B  -  -5.30
  585 PHE  ( 603-) A  -  -5.24
 1539 ASN  ( 481-) F  -  -5.24
 1375 PHE  ( 603-) B  -  -5.22
  748 GLU  ( 484-) E  -  -5.10
  917 GLU  ( 145-) B  -  -5.04
 
# 89 # 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.
 
  781 LEU  ( 517-) E  -      783 --- ASN   519- (E ) -       -4.90
 
# 90 # Note: Structural average packing environment OK
The structural average packing score is within normal ranges.
 
 
Average for range     1 - 1601 :  -0.209
 
# 91 # 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: E
 
# 92 # 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: F
 
# 93 # 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.
 
  542 LEU  ( 560-) A  -  -2.53
  300 VAL  ( 318-) A  -  -2.51
 1090 VAL  ( 318-) B  -  -2.50
 
# 94 # 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
ERROR. File not found:
TAPEOUT.DAT
ERROR. File not found:
TAPEOUT.DAT
ERROR. File not found:
TAPEOUT.DAT
ERROR. File not found:
TAPEOUT.DAT
 
# 95 # 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: E
 
# 96 # Note: Second generation quality Z-score plot
 
 
In the TeX file, a plot has been inserted here
 
Chain identifier: F
 
# 97 # 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.
 
# 98 # Note: Water contacts OK
All water clusters make at least one contact with a non-water atom.
 
# 99 # Note: No waters need moving
All water molecules are sufficiently close to the asymmetric unit given in
the input file.
 
# 100 # Note: Water hydrogen bonds OK
All water molecules can form hydrogen bonds.
 
# 101 # 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.
 
   63 GLN  (  81-) A  -
  119 ASN  ( 137-) A  -
  131 ASN  ( 149-) A  -
  176 ASN  ( 194-) A  -
  320 ASN  ( 338-) A  -
  360 HIS  ( 378-) A  -
  624 ASN  ( 360-) E  -
  853 GLN  (  81-) B  -
  966 ASN  ( 194-) B  -
 1102 ASN  ( 330-) B  -
 1150 HIS  ( 378-) B  -
 1189 HIS  ( 417-) B  -
 1294 GLN  ( 522-) B  -
 1318 ASN  ( 546-) B  -
 1452 ASN  ( 394-) F  -
 1539 ASN  ( 481-) F  -
 1556 GLN  ( 498-) F  -
 
# 102 # 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.
 
   16 HIS  (  34-) A  -   HIS-H   0.04 HIS-D   0.56
  177 HIS  ( 195-) A  -   HIS-H   0.04 HIS-E   0.59
  210 HIS  ( 228-) A  -   HIS-H   0.03 HIS-E   0.59
  221 HIS  ( 239-) A  -   HIS-H   0.04 HIS-E   0.59
  223 HIS  ( 241-) A  -   HIS-H   0.06 HIS-E   0.61
  247 HIS  ( 265-) A  -   HIS-H   0.05 HIS-E   0.57
  327 HIS  ( 345-) A  -   HIS-H   0.05 HIS-E   0.57
  355 HIS  ( 373-) A  -   HIS-H   0.04 HIS-D   0.57
  356 HIS  ( 374-) A  -   HIS-H   0.05 HIS-D   0.54
  360 HIS  ( 378-) A  -   HIS-H   0.05 HIS-D   0.57
  383 HIS  ( 401-) A  -   HIS-H   0.06 HIS-E   0.57
  399 HIS  ( 417-) A  -   HIS-H   0.04 HIS-D   0.55
  475 HIS  ( 493-) A  -   HIS-H   0.04
  487 HIS  ( 505-) A  -   HIS-H   0.04 HIS-E   0.56
  517 HIS  ( 535-) A  -   HIS-H   0.05 HIS-E   0.60
And so on for a total of    32 lines.
 
# 103 # 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.
 
    3 ILE  (  21-) A  -    N
    4 GLU  (  22-) A  -    N
    5 GLU  (  23-) A  -    N
   20 ASP  (  38-) A  -    N
   59 SER  (  77-) A  -    OG
  119 ASN  ( 137-) A  -    N
  161 LEU  ( 179-) A  -    N
  176 ASN  ( 194-) A  -    ND2
  180 ASP  ( 198-) A  -    N
  204 LEU  ( 222-) A  -    N
  205 ILE  ( 223-) A  -    N
  243 CYS  ( 261-) A  -    N
  247 HIS  ( 265-) A  -    NE2
  249 LEU  ( 267-) A  -    N
  250 GLY  ( 268-) A  -    N
And so on for a total of   128 lines.
 
# 104 # 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.
 
   15 ASN  (  33-) A  -    OD1
   78 GLN  (  96-) A  -    OE1
  223 HIS  ( 241-) A  -    ND1
  337 ASP  ( 355-) A  -    OD1
  357 GLU  ( 375-) A  -    OE1
  439 GLU  ( 457-) A  -    OE1
  481 ASP  ( 499-) A  -    OD1
  506 GLN  ( 524-) A  -    OE1
  658 ASN  ( 394-) E  -    OD1
  805 ASN  (  33-) B  -    OD1
  868 GLN  (  96-) B  -    OE1
 1013 HIS  ( 241-) B  -    ND1
 1147 GLU  ( 375-) B  -    OE1
 1271 ASP  ( 499-) B  -    OD1
 1294 GLN  ( 522-) B  -    OE1
 1298 GLN  ( 526-) B  -    OE1
 1456 ASP  ( 398-) F  -    OD1
 
# 105 # 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: 2334
- of which buried: 1187
Total number of acceptors: 2624
- of which buried: 965
Total number of donor+acceptors: 337
  (e.g. the Ser Ogamma that can donate and accept)
- of which buried: 57
Buried donors: 1187
- without H-bond: 119
- essentially without H-bond: 0
- with only a very poor H-bond: 7
- with a poor H-bond: 28
- with a H-bond: 1033
Buried acceptors: 965
- without H-bond: 157
- essentially without H-bond: 0
- with only a very poor H-bond: 7
- with a poor H-bond: 13
- with a H-bond: 788
 
# 106 # 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 (   19)   596 (  614) A Protein             /zata/tempdir/6vw...
     2   597 (  714)   597 (  714) A Sugar               /zata/tempdir/6vw...
     3   598 (  334)   785 (  521) E Protein             /zata/tempdir/6vw...
     4   786 (  523)   790 (  527) E Protein             /zata/tempdir/6vw...
     5   791 (   19)  1386 (  614) B Protein             /zata/tempdir/6vw...
     6  1387 (  714)  1387 (  714) B Sugar               /zata/tempdir/6vw...
     7  1388 (  715)  1388 (  715) B Sugar               /zata/tempdir/6vw...
     8  1389 (  331)  1574 (  516) F Protein             /zata/tempdir/6vw...
     9  1575 (  520)  1582 (  527) F Protein             /zata/tempdir/6vw...
    10  1583 (    1)  1583 (    1) C Sugar               /zata/tempdir/6vw...
    11  1584 (    2)  1584 (    2) C Sugar<-             /zata/tempdir/6vw...
    12  1585 (    1)  1585 (    1) D Sugar               /zata/tempdir/6vw...
    13  1586 (    2)  1586 (    2) D Sugar<-             /zata/tempdir/6vw...
    14  1587 (    1)  1587 (    1) G Sugar               /zata/tempdir/6vw...
    15  1588 (    2)  1588 (    2) G Sugar               /zata/tempdir/6vw...
And so on for a total of    44 lines.
 
# 107 # 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.680
  1st generation packing quality :   0.729 (          (  -0.8,  2.5))
  2nd generation packing quality :  -1.124 (          (  -1.6,  1.2))
  Ramachandran plot appearance   :  -3.028 (poor      (  -2.9,  1.6))
  chi-1/chi-2 rotamer normality  :  -3.477 (poor      (  -4.7,  1.8))
  Backbone conformation          :   0.046 (          (  -0.9,  3.7))
  Inside/Outside distribution    :   1.026
 
 RMS Z-scores, should be close to 1.0:
  Bond lengths                   :   0.214 (tight)
  Bond angles                    :   0.538 (tight)
  Omega angle restraints         :   0.879
  Side chain planarity           :   0.207 (tight)
  Improper dihedral distribution :   0.344
  B-factor distribution          :   0.762
 
# 108 # 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.
 
# 109 # 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.
 
# 110 # Error: Bumps in your structure
Upon analysing the bumps in your structure, WHAT CHECK got very, very
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.
 
# 111 # 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.
 
# 112 # 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.
 
 1593 NAG  (   1-) J  -     44.45
 1587 NAG  (   1-) G  -     32.08
 1596 NAG  (   1-) K  -     31.70
 1598 NAG  (   1-) L  -     31.04
 1591 NAG  (   1-) I  -     31.03
 1583 NAG  (   1-) C  -     30.75
 1585 NAG  (   1-) D  -     30.05
 1589 NAG  (   1-) H  -     29.82
 1597 NAG  (   2-) K  -     28.93
 1600 NAG  (   1-) M  -     28.88
 1594 NAG  (   2-) J  -     28.74
 1588 NAG  (   2-) G  -     28.26
 1599 NAG  (   2-) L  -     28.22
 1592 NAG  (   2-) I  -     28.21
 1584 NAG  (   2-) C  -     27.97
And so on for a total of   127 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.
