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

Date : 2024-12-15
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/4kqz/wctemf/4kqz_final.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                                                        4KQZ
ATOM  *****  O   HOH A 802      16.841 -22.187 -12.247  1.00 38.36       802 O
ATOM  *****  O   HOH A 803      26.327 -24.711  -9.091  1.00 36.14       803 O
ATOM  *****  O   HOH A 804      27.751 -20.995  -5.181  1.00 42.80       804 O
ATOM  *****  O   HOH A 805      21.561 -24.021 -17.221  1.00 43.78       805 O
ATOM  *****  O   HOH A 806      33.549 -41.700  -2.216  1.00 36.71       806 O
ATOM  *****  O   HOH A 807      26.253 -24.909   0.509  1.00 44.34       807 O
ATOM  *****  O   HOH A 808      19.921 -13.540 -20.430  1.00 56.13       808 O
ATOM  *****  O   HOH A 809      12.024 -10.674   1.647  1.00 44.73       809 O
ATOM  *****  O   HOH A 810      31.398 -25.806  -4.699  1.00 39.40       810 O
ATOM  *****  O   HOH A 811       7.163 -18.538  -9.416  1.00 39.94       811 O
ATOM  *****  O   HOH A 812      14.875 -16.384   1.343  1.00 50.15       812 O
ATOM  *****  O   HOH A 813       9.442 -20.015  -1.327  1.00 35.53       813 O
ATOM  *****  O   HOH A 814       5.707 -22.702 -12.188  1.00 40.31       814 O
ATOM  *****  O   HOH A 815       6.117 -21.541  -3.248  1.00 44.49       815 O
ATOM  *****  O   HOH A 816      18.240 -21.901 -19.057  1.00 44.92       816 O
ATOM  *****  O   HOH A 818      30.518 -30.871   1.057  1.00 37.05       818 O
ATOM  *****  O   HOH A 819       7.492 -25.461 -18.130  1.00 42.76       819 O
ATOM  *****  O   HOH A 820      14.070 -18.370   3.890  1.00 46.17       820 O
ATOM  *****  O   HOH A 821      20.796 -18.389   5.976  1.00 58.79       821 O
ATOM  *****  O   HOH A 822      31.571   4.303  -1.040  1.00 47.36       822 O
ATOM  *****  O   HOH A 824      29.096 -40.356 -15.600  1.00 43.81       824 O
ATOM  *****  O   HOH A 825      33.341  -8.947  -5.303  1.00 57.94       825 O
ATOM  *****  O   HOH A 828      20.651 -18.157 -24.729  1.00 69.10       828 O
ATOM  *****  O   HOH A 829      24.049 -27.998   4.605  1.00 55.51       829 O
ATOM  *****  O   HOH A 831      23.034  -7.090   7.067  1.00 44.63       831 O
ATOM  *****  O   HOH A 832       7.513 -28.149 -17.111  1.00 50.61       832 O
ATOM  *****  O   HOH A 833      32.456 -27.971  -9.381  1.00 49.66       833 O
ATOM  *****  O   HOH A 834      36.003 -46.543  -6.865  1.00 49.07       834 O
ATOM  *****  O   HOH A 835      15.621 -25.563 -17.203  1.00 41.15       835 O
ATOM  *****  O   HOH A 836      22.289 -14.070 -20.769  1.00 49.13       836 O
ATOM  *****  O   HOH A 837      21.941 -17.601   3.679  1.00 47.77       837 O
ATOM  *****  O   HOH A 838      32.838 -31.777   0.257  1.00 46.89       838 O
ATOM  *****  O   HOH A 841      26.049   0.343 -15.611  1.00 53.22       841 O
ATOM  *****  O   HOH A 843      12.311 -31.273 -22.068  1.00 59.95       843 O
ATOM  *****  O   HOH B 802      16.497 -54.166 -32.292  1.00 59.50       802 O
ATOM  *****  O   HOH B 803      17.586 -40.784 -14.693  1.00 38.83       803 O
ATOM  *****  O   HOH B 804      10.624 -57.446   0.620  1.00 50.18       804 O
ATOM  *****  O   HOH B 805      16.180 -39.774 -20.878  1.00 42.53       805 O
ATOM  *****  O   HOH B 806      14.434 -50.792 -11.733  1.00 45.38       806 O
ATOM  *****  O   HOH B 807      -0.006 -58.331  -2.805  1.00 56.44       807 O
ATOM  *****  O   HOH B 808      23.287 -58.361 -19.310  1.00 56.29       808 O
ATOM  *****  O   HOH B 809      30.201 -52.068 -16.545  1.00 55.27       809 O
ATOM  *****  O   HOH B 810       4.935 -68.662 -20.881  1.00 83.61       810 O
ATOM  *****  O   HOH B 811      13.616 -48.461  -3.505  1.00 43.99       811 O
ATOM  *****  O   HOH B 812      18.460 -58.117 -32.059  1.00 54.85       812 O
ATOM  *****  O   HOH B 813      32.190 -57.295 -26.201  1.00 57.73       813 O
ATOM  *****  O   HOH B 814      -1.832 -56.647  -3.912  1.00 52.18       814 O
ATOM  *****  O   HOH B 816      22.946 -55.378 -32.799  1.00 61.34       816 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:
 
# 2 # Note: Header records from PDB file
Header records from PDB file.
 
HEADER                                                        4KQZ
 
# 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.021287  0.000000  0.000000
  0.000000  0.009219  0.000000
  0.000000  0.000000  0.007941
 
# 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.181
 CA-only RMS fit for the two chains : 0.901
 
# 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 # Warning: Problem detected upon counting molecules and matrices
The parameter Z as given on the CRYST card represents the molecular
multiplicity in the crystallographic cell. Normally, Z equals the number of
matrices of the space group multiplied by the number of NCS relations. The
value of Z is multiplied by the integrated molecular weight of the molecules
in the file to determine the Matthews coefficient. This relation is being
validated in this option. Be aware that the validation can get confused if
both multiple copies of the molecule are present in the ATOM records and
MTRIX records are present in the header of the PDB file.
 
 Space group as read from CRYST card: P 21 21 21
 Number of matrices in space group: 4
 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: 8
 
# 8 # 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: 45764.301
 Volume of the Unit Cell V= 641680.625
 Space group multiplicity: 4
 No NCS symmetry matrices (MTRIX records) found in PDB file
 Matthews coefficient for observed atoms and Z is high: Vm= 28.043
 No Matthews coefficient given in REMARK 280
 Or should we use the previously suggested Z = 8
 which would result in Vm= 3.505
 And remember, a matrix counting problem has been reported earlier already
 
# 9 # 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.
 
# 10 # 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.
 
# 11 # Note: No strange inter-chain connections detected
No covalent bonds have been detected between molecules with non-identical
chain identifiers.
 
# 12 # Note: No duplicate atom names in ligands
All atom names in ligands (if any) seem adequately unique.
 
# 13 # 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).
 
# 14 # 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).
 
# 15 # Note: No attached groups interfere with hydrogen bond calculations
It seems there are no sugars, lipids, etc., bound (or very close) to atoms
that otherwise could form hydrogen bonds.
 
# 16 # 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.
 
# 17 # 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.
 
# 18 # Note: All residues have a complete backbone.
No residues have missing backbone atoms.
 
# 19 # Note: No C-alpha only residues
There are no residues that consist of only an alpha carbon atom.
 
# 20 # 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 (  381)   208 (  588) A Protein             To check
     2   209 (  381)   416 (  588) B Protein             To check
     3   417 (  701)   417 (  701) A Sugar               To check
     4   418 (  701)   418 (  701) B Sugar               To check
     5   419 ( HOH )   419 ( HOH ) A water   (    1)     To check
     6   420 ( HOH )   420 ( HOH ) B water   (    1)     To check
MODELs skipped upon reading PDB file: 0
X-ray structure. No MODELs found
The total number of amino acids found is 416
of which 14 have poor or (essentially) missing atoms
No nucleic acids observed in input file
Number of (recognized) sugars: 2
of which 2 have poor or (essentially) missing atoms
Number of water molecules: 2
Residue numbers increase monotonously OK
ERROR. File not found:
TAPEOUT.DAT
ERROR. File not found:
TAPEOUT.DAT
 
# 21 # Note: Ramachandran plot
In this Ramachandran plot x-signs represent glycines, squares represent
prolines, and plus-signs represent the other residues. If too many
plus-signs fall outside the contoured areas then the molecule is poorly
refined (or worse). Proline can only occur in the narrow region around
phi=-60 that also falls within the other contour islands.
 
In a colour picture, the residues that are part of a helix are shown in blue,
strand residues in red. Preferred regions for helical residues are drawn in
blue, for strand residues in red, and for all other residues in green. A full
explanation of the Ramachandran plot together with a series of examples can
be found at the WHAT CHECK website [REF].
 
In the TeX file, a plot has been inserted here
 
Chain identifier: A
 
# 22 # Note: Ramachandran plot
 
 
In the TeX file, a plot has been inserted here
 
Chain identifier: B
 
# 23 # Note: Secondary structure
This is the secondary structure according to DSSP. Only helix (H), overwound
or 3/10-helix (3), strand (S), turn (T) and coil (blank) are shown [REF].
All DSSP related information can be found at swift.cmbi.ru.nl/gv/dssp/
This is not really a structure validation option, but a very scattered
secondary structure (i.e. many strands of only a few residues length, many
Ts inside helices, etc) tends to indicate a poor structure. A full
explanation of the DSSP secondary structure determination program together
with a series of examples can be found at the WHAT CHECK website [REF].
 
Secondary structure assignment
                     10        20        30        40        50        60
                      |         |         |         |         |         |
    1 -   60 VECDFSPLLSGTPPQVYNFKRLVFTNCNYNLTKLLSLFSVNDFTCSQISPAAIASNCYSS
( 381)-( 440)
                     70        80        90       100       110       120
                      |         |         |         |         |         |
   61 -  120 LILDYFSYPLSMKSDLSVSSAGPISQFNYKQSFSNPTCLILATVPHNLTTITKPLKYSYI
( 441)-( 500)
                    130       140       150       160       170       180
                      |         |         |         |         |         |
  121 -  180 NKCSRLLSDDRTEVPQLVNANQYSPCVSIVPSTVWEDGDYYRKQLSPLEGGGWLVASGST
( 501)-( 560)
                    190       200
                      |         |
  181 -  208 VAMTEQLQMGFGITVQYGTDTNSVCPKL
( 561)-( 588)
            210       220       230       240       250       260
              |         |         |         |         |         |
  209 -  268 VECDFSPLLSGTPPQVYNFKRLVFTNCNYNLTKLLSLFSVNDFTCSQISPAAIASNCYSS
( 381)-( 440)
            270       280       290       300       310       320
              |         |         |         |         |         |
  269 -  328 LILDYFSYPLSMKSDLSVSSAGPISQFNYKQSFSNPTCLILATVPHNLTTITKPLKYSYI
( 441)-( 500)
            330       340       350       360       370       380
              |         |         |         |         |         |
  329 -  388 NKCSRLLSDDRTEVPQLVNANQYSPCVSIVPSTVWEDGDYYRKQLSPLEGGGWLVASGST
( 501)-( 560)
            390       400       410
              |         |         |
  389 -  416 VAMTEQLQMGFGITVQYGTDTNSVCPKL
( 561)-( 588)
 
 
 
 
# 24 # Note: No rounded coordinates detected
No significant rounding of atom coordinates has been detected.
 
# 25 # Note: No artificial side chains detected
No artificial side-chain positions characterized by chi-1=0.0 or chi-1=180.0
have been detected.
 
# 26 # Note: No missing atoms detected in residues
All expected atoms are present in residues. This validation option has not
looked at 'things' that can or should be attached to the elementary building
blocks (amino acids, nucleotides). Even the C-terminal oxygens are treated
separately.
 
# 27 # Warning: B-factors outside the range 0.0 - 100.0
In principle, B-factors can have a very wide range of values, but in
practice, B-factors should not be zero while B-factors above 100.0
are a good indicator that the location of that atom is meaningless. Be
aware that the cutoff at 100.0 is arbitrary. 'High' indicates that atoms
with a B-factor > 100.0 were observed; 'Zero' indicates that atoms with
a B-factor of zero were observed.
 
   20 LYS  ( 400-) A  -   High
   80 SER  ( 460-) A  -   High
   81 ALA  ( 461-) A  -   High
   93 PHE  ( 473-) A  -   High
  106 HIS  ( 486-) A  -   High
  131 ARG  ( 511-) A  -   High
  185 GLU  ( 565-) A  -   High
  301 PHE  ( 473-) B  -   High
  338 ASP  ( 510-) B  -   High
  339 ARG  ( 511-) B  -   High
  368 TYR  ( 540-) B  -   High
  376 LEU  ( 548-) B  -   High
  377 GLU  ( 549-) B  -   High
  379 GLY  ( 551-) B  -   High
  417 NAG  ( 701-) A  -   High
  418 NAG  ( 701-) B  -   High
 
# 28 # Note: C-terminus capping
The residues listed in the table below are either C-terminal or pseudo
C-terminal (i.e. last residue before a missing residue).
In X-ray the coordinates must be located in density. Mobility or disorder
sometimes cause this density to be so poor that the positions of the atoms
cannot be determined. Crystallographers tend to leave out the atoms in such
cases. In many cases the N- or C-terminal residues are too disordered to see.
In case of the N-terminus, you can often see from the residue numbers if
there are missing residues; at the C-terminus this is impossible. Therefore,
often the position of the backbone nitrogen of the first residue missing
at the C-terminal end is calculated and added to indicate that there
are missing residues. As a single N causes validation trouble, we remove
these single-N-residues before doing the validation. If this happened,
the label -N is added to the pseudo C-terminus. Other labels can be +X
in case something weird is bound to the backbone C, or +OXT if a spurious
OXT atom is found. -OXT indicates that an expected OXT is missing. 'Swap'
means that the O' and O'' (O and OXT in PDB files) have been swapped in
terms of nomenclature. 'Bad' means that something bad happened that WHAT IF
does not understand. In such cases you might get three residue numbers in
square brackets; one of those might be what WHAT IF had expected to find,
but then it also might not). In case of chain breaks the number of missing
residues is listen in round brackets. OK means what it suggests...
 
Be aware that we cannot easily see the difference between these errors and
errors in the chain and residue numbering schemes. So do not blindly trust
the table below. If you get weird errors at, or near, the left-over
incomplete C-terminal residue, please check by hand if a missing Oxt or
a removed single N is the cause. Also, many peptidic ligands get the same
chain identifier as the larger protein they are bound to. In such cases there
are more than one C-termini and OXTs with the same ID. WHAT IF gives some
random warnings about these cases. So, don't take everything at face value,
but think for yourself.
 
  208 LEU  ( 588-) A  -        OK
  416 LEU  ( 588-) B  -        OK
 
# 29 # Note: Weights administratively correct
All atomic occupancy factors ('weights') fall in the 0.0--1.0 range, which
makes them administratively correct.
 
# 30 # Note: Normal distribution of occupancy values
 
The distribution of the occupancy values in this file seems 'normal'.
 
Be aware that this evaluation is merely the result of comparing this file
with about 500 well-refined high-resolution files in the PDB. If this file
has much higher or much lower resolution than the PDB files used
in WHAT CHECK's training set, non-normal values might very well be perfectly
fine, or normal values might actually be not so normal. So, this check is
actually more an indicator and certainly not a check in which I have great
confidence.
 
# 31 # 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.
 
# 32 # Warning: What type of B-factor?
WHAT CHECK does not yet know well how to cope with B-factors in case TLS has
been used. It simply assumes that the B-factor listed on the ATOM and HETATM
cards are the total B-factors. When TLS refinement is used that assumption
sometimes is not correct. The header of the PDB file states that TLS groups
were used. So, if WHAT CHECK complains about your  B-factors, while you think
that they are OK, then check for TLS related B-factor problems first.
 
Number of TLS groups mentione in PDB file header: 2
 
Temperature not mentioned in PDB file. This most likely means
that the temperature record is absent.
Room temperature assumed
 
# 33 # Note: Number of buried atoms with low B-factor is OK
For protein structures determined at room temperature, no more than about 1
percent of the B factors of buried atoms is below 5.0. In liquid
nitrogen this percentage is allowed to be higher, of course.
 
Percentage of buried atoms with B less than 5 :   0.00
 
# 34 # Warning: Analysis of bonded atoms indicate B-factor problems
For each of the bond types in a protein a distribution was derived for the
difference between the square roots of the B-factors of the two atoms. All
bonds in the current protein were scored against these distributions. The
number given below is the RMS Z-score over the structure. For a structure
with completely restrained B-factors, this value will be around 0.35, for
extremely high resolution structures refined with free isotropic B-factors
this number is expected to be near 1.0. A value over 1.5 is a sign of
under-contraining of the B-factors during refinement.
 
RMS Z-score :  2.006 over    2835 bonds
Average difference in B over a bond :    5.97
RMS difference in B over a bond :    8.24
 
# 35 # Note: B-factor plot
The average atomic B-factor per residue is plotted as function of the residue
number.
 
In the TeX file, a plot has been inserted here
 
Chain identifier: A
 
# 36 # Note: B-factor plot
 
 
In the TeX file, a plot has been inserted here
 
Chain identifier: B
 
# 37 # 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.
 
# 38 # Note: Valine nomenclature OK
No errors were detected in valine nomenclature.
 
# 39 # Note: Threonine nomenclature OK
No errors were detected in threonine nomenclature.
 
# 40 # Note: Isoleucine nomenclature OK
No errors were detected in isoleucine nomenclature.
 
# 41 # Note: Leucine nomenclature OK
No errors were detected in leucine nomenclature.
 
# 42 # Note: Arginine nomenclature OK
No errors were detected in arginine nomenclature.
 
# 43 # Note: Tyrosine torsion conventions OK
No errors were detected in tyrosine torsion angle conventions.
 
# 44 # Note: Phenylalanine torsion conventions OK
No errors were detected in phenylalanine torsion angle conventions.
 
# 45 # Note: Aspartic acid torsion conventions OK
No errors were detected in aspartic acid torsion angle conventions.
 
# 46 # Note: Glutamic acid torsion conventions OK
No errors were detected in glutamic acid torsion angle conventions.
 
# 47 # 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).
 
# 48 # 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.
 
# 49 # Note: No decreasing residue numbers
All residue numbers are strictly increasing within each chain.
 
# 50 # 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]).
 
# 51 # Note: Normal bond length variability
Bond lengths were found to deviate normally from the standard bond lengths
(values for Protein residues were taken from Engh and Huber [REF], for
DNA/RNA from Parkinson et al [REF]).
 
 RMS Z-score for bond lengths: 0.479
 RMS-deviation in bond distances: 0.012
 
# 52 # 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.
 
# 53 # 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.
 
  129 ASP  ( 509-) A  -    CA   CB   CG  116.71    4.1
  301 PHE  ( 473-) B  -    CA   CB   CG  120.54    6.7
  315 ASN  ( 487-) B  -    CA   CB   CG  118.24    5.6
  337 ASP  ( 509-) B  -    CA   CB   CG  117.14    4.5
 
# 54 # Note: Normal bond angle variability
Bond angles were found to deviate normally from the mean 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, and this is indeed
observed for very high resolution X-ray structures.
 
 RMS Z-score for bond angles: 0.732
 RMS-deviation in bond angles: 1.399
 
# 55 # Note: Residue hand check OK
No atoms are observed that have the wrong handedness. Be aware, though, that
WHAT CHECK might have corrected the handedness of some atoms already. The
handedness has not been corrected for any case where the problem is worse
than just an administrative discomfort.
 
# 56 # Note: Chirality OK
All protein atoms have proper chirality, or there is no intact protein
present in the PDB file.
The average deviation= 0.831
 
# 57 # 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.658
 
# 58 # Note: Tau angles OK
All of the tau angles (N-C-alpha-C) of amino acids fall within expected
RMS deviations.
 
# 59 # 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.886
 
# 60 # Note: Side chain planarity OK
All of the side chains of residues that have an intact planar group are
planar within expected RMS deviations.
 
# 61 # 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.
 
# 62 # Note: Ramachandran Z-score OK
The score expressing how well the backbone conformations of all residues
correspond to the known allowed areas in the Ramachandran plot is within
expected ranges for well-refined structures.
 
 Ramachandran Z-score : -2.771
 
# 63 # 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.
 
# 64 # 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.
 
  409 THR  ( 581-) B  -   -2.5
   43 PHE  ( 423-) A  -   -2.5
  251 PHE  ( 423-) B  -   -2.5
  201 THR  ( 581-) A  -   -2.4
  407 THR  ( 579-) B  -   -2.3
  287 SER  ( 459-) B  -   -2.2
  316 LEU  ( 488-) B  -   -2.2
   48 ILE  ( 428-) A  -   -2.2
    2 GLU  ( 382-) A  -   -2.1
  349 ASN  ( 521-) B  -   -2.1
  217 LEU  ( 389-) B  -   -2.0
  301 PHE  ( 473-) B  -   -2.0
 
# 65 # 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.
 
    2 GLU  ( 382-) A  - Poor phi/psi
    6 SER  ( 386-) A  - Omega to (next) Pro poor
   11 GLY  ( 391-) A  - Poor phi/psi
   12 THR  ( 392-) A  - Omega to (next) Pro poor
   13 PRO  ( 393-) A  - Omega to (next) Pro poor
   26 ASN  ( 406-) A  - Poor phi/psi
   38 PHE  ( 418-) A  - omega poor
   47 GLN  ( 427-) A  - Poor phi/psi
   49 SER  ( 429-) A  - Omega to (next) Pro poor
   68 TYR  ( 448-) A  - Omega to (next) Pro poor
   78 VAL  ( 458-) A  - omega poor
   79 SER  ( 459-) A  - omega poor
   80 SER  ( 460-) A  - Poor phi/psi
   82 GLY  ( 462-) A  - Poor phi/psi, omega to (next)
   95 ASN  ( 475-) A  - Omega to (next) Pro poor
And so on for a total of    63 lines.
 
# 66 # 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.
 
    8 LEU  ( 388-) A  -    -1.31
   70 LEU  ( 450-) A  -    -1.32
  108 LEU  ( 488-) A  -    -1.30
  168 LEU  ( 548-) A  -    -1.32
  208 LEU  ( 588-) A  -    -1.32
  216 LEU  ( 388-) B  -    -1.32
  217 LEU  ( 389-) B  -    -1.32
  278 LEU  ( 450-) B  -    -1.32
  316 LEU  ( 488-) B  -    -1.32
  376 LEU  ( 548-) B  -    -1.32
   61 LEU  ( 441-) A  -    -1.30
   75 ASP  ( 455-) A  -    -1.24
   99 LEU  ( 479-) A  -    -1.26
  269 LEU  ( 441-) B  -    -1.29
  270 ILE  ( 442-) B  -    -1.24
And so on for a total of   185 lines.
 
# 67 # 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.612
 
# 68 # 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.
 
  314 HIS  ( 486-) B  -   0.38
   44 THR  ( 424-) A  -   0.39
  252 THR  ( 424-) B  -   0.39
 
# 69 # 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!
 
   79 SER  ( 459-) A  -       0
   80 SER  ( 460-) A  -       0
   81 ALA  ( 461-) A  -       0
  287 SER  ( 459-) B  -       0
  335 LEU  ( 507-) B  -       0
  377 GLU  ( 549-) B  -       0
   47 GLN  ( 427-) A  -       1
   88 ASN  ( 468-) A  -       1
  130 ASP  ( 510-) A  -       1
  296 ASN  ( 468-) B  -       1
  338 ASP  ( 510-) B  -       1
  407 THR  ( 579-) B  -       1
   10 SER  ( 390-) A  -       2
  155 TRP  ( 535-) A  -       2
  199 THR  ( 579-) A  -       2
  218 SER  ( 390-) B  -       2
  255 GLN  ( 427-) B  -       2
  408 ASP  ( 580-) B  -       2
 
# 70 # 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.975
 
# 71 # Note: Omega angle restraint OK
The omega angles for trans-peptide bonds in a structure is expected to give a
gaussian distribution with the average around +178 degrees, and a standard
deviation around 5.5. In the current structure the standard deviation agrees
with this expectation.
 
Omega average and std. deviation= 178.650 6.644
 
# 72 # Note: PRO puckering amplitude OK
Puckering amplitudes for all PRO residues are within normal ranges.
 
# 73 # Note: PRO puckering phases OK
Puckering phases for all PRO residues are normal
 
# 74 # 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!
 
  379 GLY  ( 551-) B  -  3.12   25
   48 ILE  ( 428-) A  -  1.56   11
  256 ILE  ( 428-) B  -  1.52   15
 
# 75 # 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.
 
   80 SER  ( 460-) A  - TT+   Likely
  408 ASP  ( 580-) B  - TT+   Likely
 
# 76 # Error: Abnormally short interatomic distances
The pairs of atoms listed in the table below have an unusually short
interactomic distance; each bump is listed in only one direction.
 
The contact distances of all atom pairs have been checked. Two atoms are
said to `bump' if they are closer than the sum of their Van der Waals radii
minus 0.40 Angstrom. For hydrogen bonded pairs a tolerance of 0.55 Angstrom
is used. The first number in the table tells you how much shorter that
specific contact is than the acceptable limit. The second distance is the
distance between the centres of the two atoms. Although we believe that two
water atoms at 2.4 A distance are too close, we only report water pairs that
are closer than this rather short distance.
 
INTRA and INTER indicate whether the clashes are between atoms in the same
asymmetric unit, or atoms in symmetry related asymmetric units, respectively.
The last text-item on each line represents the status of the atom pair. If
the final column contains the text 'HB', the bump criterion was relaxed
because there could be a hydrogen bond. Similarly relaxed criteria are used
for 1--3 and 1--4 interactions (listed as 'B2' and 'B3', respectively).
If the last column is 'BF', the sum of the B-factors of the atoms is higher
than 80, which makes the appearance of the bump somewhat less severe because
the atoms probably are not there anyway. BL, on the other hand, indicates
that the bumping atoms both have a low B-factor, and that makes the bumps
more worrisome.
 
Bumps between atoms for which the sum of their occupancies is lower than one
are not reported. If the MODEL number does not exist (as is the case in most
X-ray files), a minus sign is printed instead.
 
   30 ASN  ( 410-) A  -    ND2 <-->   417 NAG  ( 701-) A  -    C1     1.67    1.43  INTRA BF
  238 ASN  ( 410-) B  -    ND2 <-->   418 NAG  ( 701-) B  -    C1     1.66    1.44  INTRA BF
   30 ASN  ( 410-) A  -    CG  <-->   417 NAG  ( 701-) A  -    C1     0.74    2.46  INTRA BF
  238 ASN  ( 410-) B  -    CG  <-->   418 NAG  ( 701-) B  -    C1     0.72    2.48  INTRA BF
   30 ASN  ( 410-) A  -    ND2 <-->   417 NAG  ( 701-) A  -    C2     0.63    2.47  INTRA BF
  238 ASN  ( 410-) B  -    ND2 <-->   418 NAG  ( 701-) B  -    C2     0.60    2.50  INTRA BF
   30 ASN  ( 410-) A  -    ND2 <-->   417 NAG  ( 701-) A  -    O5     0.37    2.33  INTRA BF
  238 ASN  ( 410-) B  -    ND2 <-->   418 NAG  ( 701-) B  -    O5     0.35    2.35  INTRA BF
  214 SER  ( 386-) B  -    N   <-->   215 PRO  ( 387-) B  -    CD     0.19    2.81  INTRA
    6 SER  ( 386-) A  -    N   <-->     7 PRO  ( 387-) A  -    CD     0.18    2.82  INTRA BF
  209 VAL  ( 381-) B  -    O   <-->   236 ASN  ( 408-) B  -    N      0.15    2.55  INTRA BF
  125 ARG  ( 505-) A  -    NH2 <-->   169 GLU  ( 549-) A  -    O      0.11    2.59  INTRA BL
   80 SER  ( 460-) A  -    C   <-->    81 ALA  ( 461-) A  -    C      0.09    2.71  INTRA BF
  166 SER  ( 546-) A  -    N   <-->   169 GLU  ( 549-) A  -    OE1    0.08    2.62  INTRA BF
  374 SER  ( 546-) B  -    N   <-->   377 GLU  ( 549-) B  -    OE1    0.07    2.63  INTRA BF
  374 SER  ( 546-) B  -    OG  <-->   376 LEU  ( 548-) B  -    CD1    0.06    2.74  INTRA BF
   30 ASN  ( 410-) A  -    ND2 <-->   417 NAG  ( 701-) A  -    N2     0.06    2.94  INTRA BF
  298 LYS  ( 470-) B  -    O   <-->   349 ASN  ( 521-) B  -    N      0.05    2.65  INTRA BL
  238 ASN  ( 410-) B  -    ND2 <-->   418 NAG  ( 701-) B  -    N2     0.04    2.96  INTRA BF
  310 ALA  ( 482-) B  -    O   <-->   397 MET  ( 569-) B  -    N      0.03    2.67  INTRA BL
  102 ALA  ( 482-) A  -    O   <-->   189 MET  ( 569-) A  -    N      0.02    2.68  INTRA BL
  159 ASP  ( 539-) A  -    OD1 <-->   298 LYS  ( 470-) B  -    NZ     0.01    2.69  INTRA BL
 
# 77 # 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: 7.858
Total bump value per residue: 0.053
Total number of bumps: 22
Total squared bump value: 7.741
Total number of bumps in the mildest bin: 14
Total number of bumps in the second bin: 2
Total number of bumps in the middle bin: 4
Total number of bumps in the fourth bin: 0
Total number of bumps in the worst bin: 2
 
# 78 # 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.
 
# 79 # 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.039
 
# 80 # Note: Inside/Outside RMS Z-score plot
The Inside/Outside distribution normality RMS Z-score over a 15 residue
window is plotted as function of the residue number. High areas in the plot
(above 1.5) indicate unusual inside/outside patterns.
 
In the TeX file, a plot has been inserted here
 
Chain identifier: A
 
# 81 # Note: Inside/Outside RMS Z-score plot
 
 
In the TeX file, a plot has been inserted here
 
Chain identifier: B
 
# 82 # 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.
 
  255 GLN  ( 427-) B  -  -6.67
  115 LEU  ( 495-) A  -  -6.51
  168 LEU  ( 548-) A  -  -6.35
  323 LEU  ( 495-) B  -  -6.19
   93 PHE  ( 473-) A  -  -6.17
   47 GLN  ( 427-) A  -  -6.03
  415 LYS  ( 587-) B  -  -5.90
  376 LEU  ( 548-) B  -  -5.84
  207 LYS  ( 587-) A  -  -5.79
  351 TYR  ( 523-) B  -  -5.31
  131 ARG  ( 511-) A  -  -5.26
 
# 83 # Note: No series of residues with bad packing environment
There are no stretches of three or more residues each having a packing score
worse than -4.0.
 
# 84 # Note: Structural average packing environment OK
The structural average packing score is within normal ranges.
 
 
Average for range     1 -  418 :  -0.581
 
# 85 # Note: Quality value plot
The quality value smoothed over a 10 residue window is plotted as function
of the residue number. Low areas in the plot (below -2.0) indicate unusual
packing.
 
In the TeX file, a plot has been inserted here
 
Chain identifier: A
 
# 86 # 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: B
 
# 87 # Note: Second generation packing environment OK
None of the individual amino acid residues has a bad packing environment.
 
# 88 # 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
 
# 89 # Note: Second generation quality Z-score plot
The second generation quality Z-score smoothed over a 10 residue window
is plotted as function of the residue number. Low areas in the plot (below
-1.3) indicate unusual packing.
 
In the TeX file, a plot has been inserted here
 
Chain identifier: A
 
# 90 # Note: Second generation quality Z-score plot
 
 
In the TeX file, a plot has been inserted here
 
Chain identifier: B
 
# 91 # 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.
 
# 92 # Note: Water contacts OK
All water clusters make at least one contact with a non-water atom.
 
# 93 # Note: No waters need moving
All water molecules are sufficiently close to the asymmetric unit given in
the input file.
 
# 94 # Note: Water hydrogen bonds OK
All water molecules can form hydrogen bonds.
 
# 95 # 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.
 
  106 HIS  ( 486-) A  -
 
# 96 # 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.
 
  106 HIS  ( 486-) A  -   HIS-E   0.58
  314 HIS  ( 486-) B  -   HIS-E   0.68 HIS-D   1.18
 
# 97 # 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.
 
    2 GLU  ( 382-) A  -    N
   16 VAL  ( 396-) A  -    N
   17 TYR  ( 397-) A  -    N
   28 ASN  ( 408-) A  -    N
   41 ASN  ( 421-) A  -    ND2
   91 GLN  ( 471-) A  -    NE2
   92 SER  ( 472-) A  -    N
  111 ILE  ( 491-) A  -    N
  116 LYS  ( 496-) A  -    N
  118 SER  ( 498-) A  -    N
  118 SER  ( 498-) A  -    OG
  123 CYS  ( 503-) A  -    N
  124 SER  ( 504-) A  -    OG
  144 SER  ( 524-) A  -    N
  168 LEU  ( 548-) A  -    N
And so on for a total of    37 lines.
 
# 98 # Note: Buried hydrogen bond acceptors OK
All buried polar side-chain hydrogen bond acceptors are involved in a
hydrogen bond in the optimized hydrogen bond network.
 
# 99 # 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: 603
- of which buried: 280
Total number of acceptors: 665
- of which buried: 225
Total number of donor+acceptors: 120
  (e.g. the Ser Ogamma that can donate and accept)
- of which buried: 24
Buried donors: 280
- without H-bond: 32
- essentially without H-bond: 0
- with only a very poor H-bond: 0
- with a poor H-bond: 2
- with a H-bond: 246
Buried acceptors: 225
- without H-bond: 47
- essentially without H-bond: 0
- with only a very poor H-bond: 1
- with a poor H-bond: 10
- with a H-bond: 167
 
# 100 # 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 (  381)   208 (  588) A Protein             To check
     2   209 (  381)   416 (  588) B Protein             To check
     3   417 (  701)   417 (  701) A Sugar               To check
     4   418 (  701)   418 (  701) B Sugar               To check
     5   419 ( HOH )   419 ( HOH ) A water   (    1)     To check
     6   420 ( HOH )   420 ( HOH ) B water   (    1)     To check
 
# 101 # 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.510
  1st generation packing quality :  -0.202 (          (  -0.5,  2.5))
  2nd generation packing quality :  -1.758 (          (  -1.5,  1.2))
  Ramachandran plot appearance   :  -2.771 (          (  -2.7,  1.6))
  chi-1/chi-2 rotamer normality  :  -3.612 (poor      (  -4.5,  1.7))
  Backbone conformation          :  -0.975 (          (  -0.8,  3.7))
  Inside/Outside distribution    :   1.039
 
 RMS Z-scores, should be close to 1.0:
  Bond lengths                   :   0.479 (tight)
  Bond angles                    :   0.732
  Omega angle restraints         :   1.208
  Side chain planarity           :   0.796
  Improper dihedral distribution :   0.658
  B-factor distribution          :   2.006 (loose)
 
# 102 # 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.
 
# 103 # 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.
 
# 104 # 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.
 
# 105 # 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.
 
# 106 # 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.
 
  416 LEU  ( 588-) B  -     14.69
  208 LEU  ( 588-) A  -     14.65
  168 LEU  ( 548-) A  -     13.69
  255 GLN  ( 427-) B  -     13.38
  115 LEU  ( 495-) A  -     13.02
  323 LEU  ( 495-) B  -     12.37
   93 PHE  ( 473-) A  -     12.34
   47 GLN  ( 427-) A  -     12.11
  415 LYS  ( 587-) B  -     11.80
  376 LEU  ( 548-) B  -     11.72
  207 LYS  ( 587-) A  -     11.59
  351 TYR  ( 523-) B  -     10.62
  131 ARG  ( 511-) A  -     10.53
  301 PHE  ( 473-) B  -      5.14
  315 ASN  ( 487-) B  -      4.23
And so on for a total of    38 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.
