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

Date : 2024-10-29
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/6m0j/wctemp_0cyc/6m0j_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                                                        6M0J
ATOM  *****  O   HOH A1002     -25.963  23.857 -26.732  1.00 53.02      1002 O
ATOM  *****  O   HOH A1003     -42.305   8.602 -33.842  1.00 56.65      1003 O
ATOM  *****  O   HOH A1004     -27.829  15.936 -11.401  1.00 53.00      1004 O
ATOM  *****  O   HOH A1005     -34.901  10.598 -30.978  1.00 54.11      1005 O
ATOM  *****  O   HOH A1006     -28.745  12.173  -0.294  1.00 53.52      1006 O
ATOM  *****  O   HOH A1007      -3.961   7.815 -26.371  1.00 53.63      1007 O
ATOM  *****  O   HOH A1008     -31.196  55.095   4.137  1.00 71.37      1008 O
ATOM  *****  O   HOH A1009     -40.376  10.106 -50.865  1.00 63.78      1009 O
ATOM  *****  O   HOH A1010      -7.813  29.158 -11.880  1.00 64.89      1010 O
ATOM  *****  O   HOH A1011     -25.568   4.973 -53.610  1.00 57.39      1011 O
ATOM  *****  O   HOH A1012     -34.586  24.032 -33.242  1.00 48.29      1012 O
ATOM  *****  O   HOH A1013     -26.478  36.450 -22.246  1.00 57.25      1013 O
ATOM  *****  O   HOH A1014      -9.853  18.761 -26.358  1.00 46.93      1014 O
ATOM  *****  O   HOH A1015     -49.594  39.831 -30.107  1.00 57.16      1015 O
ATOM  *****  O   HOH A1016     -23.927   4.546 -35.359  1.00 51.05      1016 O
ATOM  *****  O   HOH A1017     -27.799  20.091  -9.531  1.00 59.31      1017 O
ATOM  *****  O   HOH A1018     -20.582  13.443 -53.091  1.00 51.80      1018 O
ATOM  *****  O   HOH A1019     -18.138  24.261 -11.830  1.00 52.33      1019 O
ATOM  *****  O   HOH A1020     -27.510  33.135 -34.943  1.00 53.19      1020 O
ATOM  *****  O   HOH A1021     -21.354  31.953 -19.065  1.00 54.40      1021 O
ATOM  *****  O   HOH A1022     -39.862  29.657 -25.756  1.00 62.29      1022 O
ATOM  *****  O   HOH A1023     -28.170   8.587 -32.462  1.00 47.95      1023 O
ATOM  *****  O   HOH A1024     -29.593  31.629  -5.502  1.00 60.83      1024 O
ATOM  *****  O   HOH A1025     -38.949  37.142 -36.247  1.00 59.69      1025 O
ATOM  *****  O   HOH A1026     -42.436  24.659 -47.957  1.00 61.77      1026 O
ATOM  *****  O   HOH A1027     -31.364   6.422 -34.931  1.00 52.05      1027 O
ATOM  *****  O   HOH A1028     -41.792  32.593 -42.267  1.00 58.56      1028 O
ATOM  *****  O   HOH A1029     -27.474   6.523 -41.589  1.00 49.77      1029 O
ATOM  *****  O   HOH A1030     -28.163  12.280 -15.537  1.00 58.79      1030 O
ATOM  *****  O   HOH A1031     -37.477  -2.432 -36.981  1.00 57.68      1031 O
ATOM  *****  O   HOH A1032     -23.873  15.039 -31.114  1.00 48.10      1032 O
ATOM  *****  O   HOH A1033     -23.693  18.873 -19.478  1.00 52.29      1033 O
ATOM  *****  O   HOH A1034     -18.064  28.487 -11.749  1.00 55.23      1034 O
ATOM  *****  O   HOH A1035     -40.777  14.886 -29.015  1.00 59.84      1035 O
ATOM  *****  O   HOH A1036      -2.150   9.396 -27.064  1.00 51.03      1036 O
ATOM  *****  O   HOH A1037     -17.478  10.422 -25.104  1.00 55.37      1037 O
ATOM  *****  O   HOH A1038     -39.568  31.579 -40.941  1.00 59.11      1038 O
ATOM  *****  O   HOH A1039     -31.441  17.572 -52.045  1.00 58.06      1039 O
ATOM  *****  O   HOH A1040     -21.202  -2.552 -35.457  1.00 53.03      1040 O
ATOM  *****  O   HOH A1041     -46.177  11.081 -27.498  1.00 60.72      1041 O
ATOM  *****  O   HOH A1042     -37.712  16.624 -53.303  1.00 60.55      1042 O
ATOM  *****  O   HOH A1043     -27.625  -3.910 -49.364  1.00 52.46      1043 O
ATOM  *****  O   HOH A1044     -18.036   1.984  -1.726  1.00 54.71      1044 O
ATOM  *****  O   HOH A1045     -31.206  -3.908 -50.935  1.00 57.76      1045 O
ATOM  *****  O   HOH A1046      -5.676  19.725 -20.599  1.00 55.03      1046 O
ATOM  *****  O   HOH A1047     -41.552  27.137 -47.586  1.00 55.34      1047 O
ATOM  *****  O   HOH A1048     -15.708  -3.625 -45.040  1.00 51.35      1048 O
ATOM  *****  O   HOH A1049      -4.597  19.788 -36.370  1.00 59.47      1049 O
ATOM  *****  O   HOH A1050     -19.740  31.213 -16.945  1.00 50.62      1050 O
ATOM  *****  O   HOH A1051     -12.426  11.522 -46.869  1.00 50.90      1051 O
ATOM  *****  O   HOH A1052     -14.859  19.514 -42.787  1.00 54.48      1052 O
ATOM  *****  O   HOH A1053     -13.762   0.422  -7.862  1.00 53.87      1053 O
ATOM  *****  O   HOH A1054     -40.775  21.420 -29.137  1.00 60.27      1054 O
ATOM  *****  O   HOH A1055     -25.998  27.443 -29.854  1.00 53.48      1055 O
ATOM  *****  O   HOH A1056     -36.967  36.085 -38.231  1.00 61.18      1056 O
ATOM  *****  O   HOH A1057     -30.183   3.844 -34.693  1.00 54.55      1057 O
ATOM  *****  O   HOH A1058      -7.642  24.607 -30.022  1.00 61.36      1058 O
ATOM  *****  O   HOH A1059     -24.775  10.710  -2.578  1.00 53.40      1059 O
ATOM  *****  O   HOH A1060      -6.245  21.990 -22.071  1.00 55.52      1060 O
ATOM  *****  O   HOH A1061     -25.359  27.394 -27.192  1.00 53.46      1061 O
ATOM  *****  O   HOH A1062     -41.150   7.555 -31.848  1.00 63.24      1062 O
ATOM  *****  O   HOH A1063     -40.464  21.569 -26.508  1.00 64.40      1063 O
ATOM  *****  O   HOH A1064      -4.110  23.358 -22.339  1.00 68.10      1064 O
ATOM  *****  O   HOH A1065     -40.205  30.861 -49.346  1.00 62.38      1065 O
ATOM  *****  O   HOH A1066     -40.132  28.261 -49.223  1.00 64.23      1066 O
ATOM  *****  O   HOH A1067     -30.690   7.025 -32.430  1.00 60.22      1067 O
ATOM  *****  O   HOH A1068     -16.111   3.276  -0.747  1.00 61.53      1068 O
ATOM  *****  O   HOH A1069     -38.928  -3.115 -35.004  1.00 66.73      1069 O
ATOM  *****  O   HOH A1070     -38.697  -3.747 -39.071  1.00 57.13      1070 O
ATOM  *****  O   HOH A1071     -37.489  33.686 -40.631  1.00 74.27      1071 O
ATOM  *****  O   HOH E 702     -35.994  34.423  19.290  1.00 64.55       702 O
ATOM  *****  O   HOH E 703     -37.707  25.648  14.678  1.00 52.96       703 O
ATOM  *****  O   HOH E 704     -47.972  39.014  11.203  1.00 57.75       704 O
ATOM  *****  O   HOH E 705     -43.606  23.520  18.207  1.00 54.61       705 O
ATOM  *****  O   HOH E 706     -42.572  28.558  21.810  1.00 54.80       706 O
ATOM  *****  O   HOH E 707     -42.600  27.029  19.519  1.00 58.30       707 O
ATOM  *****  O   HOH E 708     -45.291  30.065  18.159  1.00 51.05       708 O
ATOM  *****  O   HOH E 709     -44.956  27.364  17.955  1.00 52.40       709 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:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF 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                                                        6M0J
 
# 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.009554  0.000000  0.000000
  0.000000  0.009554  0.000000
  0.000000  0.000000  0.004372
 
# 5 # Warning: Problem detected upon counting molecules and matrices
The parameter Z as given on the CRYST card represents the molecular
multiplicity in the crystallographic cell. Normally, Z equals the number of
matrices of the space group multiplied by the number of NCS relations. The
value of Z is multiplied by the integrated molecular weight of the molecules
in the file to determine the Matthews coefficient. This relation is being
validated in this option. Be aware that the validation can get confused if
both multiple copies of the molecule are present in the ATOM records and
MTRIX records are present in the header of the PDB file.
 
 Space group as read from CRYST card: P 41 21 2
 Number of matrices in space group: 8
 Highest polymer chain multiplicity in structure: 1
 Highest polymer chain multiplicity according to SEQRES: 1
 No explicit MTRIX NCS matrices found in the input file
 Value of Z as found on the CRYST1 card: 0
 Z, symmetry, and molecular multiplicity disagree
 Could it be that Z must be: 8
 
# 6 # Error: Matthews Coefficient (Vm) very high
 
The Matthews coefficient [REF] is defined as the density of the protein
structure in cubic Angstroms per Dalton. Normal values are between 1.5
(tightly packed, little room for solvent) and 4.0 (loosely packed, much
space for solvent). Some very loosely packed structures can get values a bit
higher than that.
 
Numbers this high are almost always caused by giving the wrong value for Z
on the CRYST1 card (or not giving this number at all).
 
 Molecular weight of all polymer chains: 90881.992
 Volume of the Unit Cell V= 2505812.5
 Space group multiplicity: 8
 No NCS symmetry matrices (MTRIX records) found in PDB file
 Matthews coefficient for observed atoms and Z is high: Vm= 27.572
 No Matthews coefficient given in REMARK 280
 Could it be that Z must be: 8
 This number is the multiplication of the spacegroup and NCS symmetry count
 Matthews coefficient for observed atoms and corrected Z: Vm= 3.447
 
# 7 # Note: Z missing on CRYST1 card
The messages above seem likely caused by the fact that Z is missing from the
CRYST1 card.
 
# 8 # Note: All atoms are sufficiently far away from symmetry axes
None of the atoms in the structure is closer than 0.77 Angstrom to a proper
symmetry axis.
 
# 9 # Note: Chain identifiers OK
WHAT CHECK has not detected any serious chain identifier problems. But be
aware that WHAT CHECK doesn't care about the chain identifiers of waters.
 
# 10 # Note: No strange inter-chain connections detected
No covalent bonds have been detected between molecules with non-identical
chain identifiers.
 
# 11 # Note: No duplicate atom names in ligands
All atom names in ligands (if any) seem adequately unique.
 
# 12 # 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).
 
# 13 # 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).
 
# 14 # 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.
 
# 15 # 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.
 
# 16 # 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.
 
# 17 # Note: All residues have a complete backbone.
No residues have missing backbone atoms.
 
# 18 # Note: No C-alpha only residues
There are no residues that consist of only an alpha carbon atom.
 
# 19 # 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)   597 (  615) A Protein             /zata/tempdir/6m0...
     2   598 (  333)   791 (  526) E Protein             /zata/tempdir/6m0...
     3   792 (  903)   792 (  903) A Sugar               /zata/tempdir/6m0...
     4   793 (  904)   793 (  904) A Sugar               /zata/tempdir/6m0...
     5   794 (  905)   794 (  905) A Sugar               /zata/tempdir/6m0...
     6   795 (  906)   795 (  906) A Sugar               /zata/tempdir/6m0...
     7   796 (  601)   796 (  601) E Sugar               /zata/tempdir/6m0...
     8   797 (  901)   797 (  901) A  ZN                 /zata/tempdir/6m0...
     9   798 (  902)   798 (  902) A  CL                 /zata/tempdir/6m0...
    10   799 ( HOH )   799 ( HOH ) A water   (    1)     /zata/tempdir/6m0...
    11   800 ( HOH )   800 ( HOH ) E water   (    1)     /zata/tempdir/6m0...
MODELs skipped upon reading PDB file: 0
X-ray structure. No MODELs found
The total number of amino acids found is 791
of which 71 have poor or (essentially) missing atoms
No nucleic acids observed in input file
Number of (recognized) sugars: 5
of which 3 have poor or (essentially) missing atoms
Number of water molecules: 2
Residue numbers increase monotonously OK
 
# 20 # 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
 
# 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: E
 
# 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 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 -  597 RLGKSEPWTLALENVVGAKNMNVRPLLNYFEPLFTWLKDQNKNSFVGWSTDWSPYAD
( 559)-( 615)
             600       610       620       630       640       650
               |         |         |         |         |         |
  598 -  657 TNLCPFGEVFNATRFASVYAWNRKRISNCVADYSVLYNSASFSTFKCYGVSPTKLNDLCF
( 333)-( 392)
             660       670       680       690       700       710
               |         |         |         |         |         |
  658 -  717 TNVYADSFVIRGDEVRQIAPGQTGKIADYNYKLPDDFTGCVIAWNSNNLDSKVGGNYNYL
( 393)-( 452)
             720       730       740       750       760       770
               |         |         |         |         |         |
  718 -  777 YRLFRKSNLKPFERDISTEIYQAGSTPCNGVEGFNCYFPLQSYGFQPTNGVGYQPYRVVV
( 453)-( 512)
             780       790
               |         |
  778 -  791 LSFELLHAPATVCG
( 513)-( 526)
 
 
 
 
# 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.
 
   38 GLU  (  56-) A  -   High
   42 GLN  (  60-) A  -   High
   63 GLN  (  81-) A  -   High
   68 GLN  (  86-) A  -   High
   69 GLU  (  87-) A  -   High
   83 GLN  ( 101-) A  -   High
   84 GLN  ( 102-) A  -   High
   85 ASN  ( 103-) A  -   High
   86 GLY  ( 104-) A  -   High
   87 SER  ( 105-) A  -   High
   88 SER  ( 106-) A  -   High
  116 ASN  ( 134-) A  -   High
  117 PRO  ( 135-) A  -   High
  118 ASP  ( 136-) A  -   High
  119 ASN  ( 137-) A  -   High
And so on for a total of    74 lines.
 
# 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.
 
  597 ASP  ( 615-) A  -        OK
  791 GLY  ( 526-) E  -        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: 0
 
Temperature not mentioned in PDB file. This most likely means
that the temperature record is absent.
Room temperature assumed
 
# 33 # Note: Number of buried atoms with low B-factor is OK
For protein structures determined at room temperature, no more than about 1
percent of the B factors of buried atoms is below 5.0. In liquid
nitrogen this percentage is allowed to be higher, of course.
 
Percentage of buried atoms with B less than 5 :   0.00
 
# 34 # 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.894 over    5423 bonds
Average difference in B over a bond :    3.55
RMS difference in B over a bond :    4.66
 
# 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: E
 
# 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 # 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  -
  622 ARG  ( 357-) E  -
 
# 43 # Warning: Tyrosine convention problem
The tyrosine residues listed in the table below have their chi-2 not between
-90.0 and 90.0
 
  165 TYR  ( 183-) A  -
 
# 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 # 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.347
 RMS-deviation in bond distances: 0.009
 
# 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.
 
  442 ARG  ( 460-) A  -    CB   CG   CD  103.54   -5.3
  460 TRP  ( 478-) A  -    CA   CB   CG  105.68   -4.2
 
# 54 # 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.633
 RMS-deviation in bond angles: 1.272
 
# 55 # 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  -
  622 ARG  ( 357-) E  -
 
# 56 # 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.563
 
# 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.473
 
# 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.611
 
# 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 # 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.020
 
# 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.
 
  642 PHE  ( 377-) E  -   -2.8
  655 LEU  ( 390-) E  -   -2.6
  647 VAL  ( 382-) E  -   -2.3
  612 PHE  ( 347-) E  -   -2.2
  563 VAL  ( 581-) A  -   -2.1
  414 ASN  ( 432-) A  -   -2.1
  675 ILE  ( 410-) E  -   -2.1
   89 VAL  ( 107-) A  -   -2.1
  761 GLY  ( 496-) E  -   -2.1
  367 TYR  ( 385-) A  -   -2.1
  495 ILE  ( 513-) A  -   -2.0
  177 HIS  ( 195-) A  -   -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.
 
   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
  128 PRO  ( 146-) A  - omega poor
  159 ARG  ( 177-) A  - Omega to (next) Pro poor
  177 HIS  ( 195-) A  - Poor phi/psi, omega poor
  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
  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    82 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.
 
   27 LEU  (  45-) A  -    -1.31
   79 LEU  (  97-) A  -    -1.32
  333 LEU  ( 351-) A  -    -1.30
  341 LEU  ( 359-) A  -    -1.32
  422 LEU  ( 440-) A  -    -1.32
  566 LEU  ( 584-) A  -    -1.32
  652 LEU  ( 387-) E  -    -1.31
  655 LEU  ( 390-) E  -    -1.32
   61 LEU  (  79-) A  -    -1.25
   70 ILE  (  88-) A  -    -1.25
   82 LEU  ( 100-) A  -    -1.29
  215 ILE  ( 233-) A  -    -1.24
  438 LEU  ( 456-) A  -    -1.29
  495 ILE  ( 513-) A  -    -1.20
  502 LEU  ( 520-) A  -    -1.23
And so on for a total of   349 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.586
 
# 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.
 
   52 SER  (  70-) A  -   0.35
  664 SER  ( 399-) E  -   0.35
  682 LYS  ( 417-) E  -   0.36
  215 ILE  ( 233-) A  -   0.36
   25 SER  (  43-) A  -   0.36
  106 SER  ( 124-) A  -   0.38
  489 SER  ( 507-) A  -   0.39
  116 ASN  ( 134-) A  -   0.40
 
# 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!
 
   85 ASN  ( 103-) A  -       0
  127 GLU  ( 145-) A  -       0
  326 CYS  ( 344-) A  -       0
  544 LYS  ( 562-) A  -       0
  318 PRO  ( 336-) A  -       1
  675 ILE  ( 410-) E  -       1
  687 ASN  ( 422-) E  -       1
  751 PHE  ( 486-) E  -       1
  335 LYS  ( 353-) A  -       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.166
 
# 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= 179.350 5.729
 
# 72 # Note: PRO puckering amplitude OK
Puckering amplitudes for all PRO residues are within normal ranges.
 
# 73 # 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].
 
  482 PRO  ( 500-) A  -  108.0 envelop C-beta (108 degrees)
  649 PRO  ( 384-) E  - -116.9 envelop C-gamma (-108 degrees)
  786 PRO  ( 521-) E  - -115.5 envelop C-gamma (-108 degrees)
 
# 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!
 
  654 ASP  ( 389-) E  -  1.64   12
  761 GLY  ( 496-) E  -  1.50   34
 
# 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.
 
  177 HIS  ( 195-) A  - TT+   Highly likely
  267 PHE  ( 285-) A  - TT+   Highly likely
  544 LYS  ( 562-) A  - TT+   Highly likely
  608 ASN  ( 343-) E  - TT+   Highly likely
   35 ASN  (  53-) A  - TT+   Likely
   64 MET  (  82-) A  - TT+   Likely
   69 GLU  (  87-) A  - TT+   Likely
  112 GLY  ( 130-) A  - TT+   Likely
  119 ASN  ( 137-) A  - TT+   Likely
  121 GLN  ( 139-) A  - TT+   Likely
  155 GLY  ( 173-) A  - TT+   Likely
  176 ASN  ( 194-) A  - TT+   Likely
  202 GLY  ( 220-) A  - TT+   Likely
  234 TYR  ( 252-) A  - TT+   Likely
  236 SER  ( 254-) A  - TT+   Likely
And so on for a total of    45 lines.
 
# 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.
 
   72 ASN  (  90-) A  -    ND2 <-->   793 NAG  ( 904-) A  -    C1     1.66    1.44  INTRA BF
   35 ASN  (  53-) A  -    ND2 <-->   795 NAG  ( 906-) A  -    C1     1.66    1.44  INTRA BF
  528 ASN  ( 546-) A  -    ND2 <-->   792 NAG  ( 903-) A  -    C1     1.65    1.45  INTRA BF
  608 ASN  ( 343-) E  -    ND2 <-->   796 NAG  ( 601-) E  -    C1     1.65    1.45  INTRA BF
  304 ASN  ( 322-) A  -    ND2 <-->   794 NAG  ( 905-) A  -    C1     1.65    1.45  INTRA BF
   72 ASN  (  90-) A  -    CG  <-->   793 NAG  ( 904-) A  -    C1     0.77    2.43  INTRA BF
  304 ASN  ( 322-) A  -    CG  <-->   794 NAG  ( 905-) A  -    C1     0.77    2.43  INTRA BF
  528 ASN  ( 546-) A  -    CG  <-->   792 NAG  ( 903-) A  -    C1     0.75    2.45  INTRA BF
  608 ASN  ( 343-) E  -    CG  <-->   796 NAG  ( 601-) E  -    C1     0.72    2.48  INTRA BF
   35 ASN  (  53-) A  -    CG  <-->   795 NAG  ( 906-) A  -    C1     0.71    2.49  INTRA BF
   35 ASN  (  53-) A  -    ND2 <-->   795 NAG  ( 906-) A  -    C2     0.65    2.45  INTRA BF
  528 ASN  ( 546-) A  -    ND2 <-->   792 NAG  ( 903-) A  -    C2     0.64    2.46  INTRA BF
  304 ASN  ( 322-) A  -    ND2 <-->   794 NAG  ( 905-) A  -    C2     0.63    2.47  INTRA BF
   72 ASN  (  90-) A  -    ND2 <-->   793 NAG  ( 904-) A  -    C2     0.62    2.48  INTRA BF
  608 ASN  ( 343-) E  -    ND2 <-->   796 NAG  ( 601-) E  -    C2     0.62    2.48  INTRA BF
And so on for a total of    80 lines.
 
# 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: 22.264
Total bump value per residue: 0.101
Total number of bumps: 80
Total squared bump value: 20.004
Total number of bumps in the mildest bin: 57
Total number of bumps in the second bin: 8
Total number of bumps in the middle bin: 8
Total number of bumps in the fourth bin: 2
Total number of bumps in the worst bin: 5
 
# 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.030
 
# 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: E
 
# 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.
 
  269 GLN  ( 287-) A  -  -6.76
  784 HIS  ( 519-) E  -  -6.40
  723 LYS  ( 458-) E  -  -6.39
  518 GLU  ( 536-) A  -  -6.06
  611 ARG  ( 346-) E  -  -5.94
  679 GLN  ( 414-) E  -  -5.50
  710 VAL  ( 445-) E  -  -5.41
  770 TYR  ( 505-) E  -  -5.41
  585 PHE  ( 603-) A  -  -5.36
   84 GLN  ( 102-) A  -  -5.26
  709 LYS  ( 444-) E  -  -5.16
  375 ARG  ( 393-) A  -  -5.11
 
# 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 -  796 :  -0.085
 
# 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: E
 
# 87 # 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.91
  741 GLY  ( 476-) E  -  -2.69
  715 ASN  ( 450-) E  -  -2.50
 
# 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: E
 
# 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.
 
   16 HIS  (  34-) A  -
   84 GLN  ( 102-) A  -
  116 ASN  ( 134-) A  -
  136 ASN  ( 154-) A  -
  272 ASN  ( 290-) A  -
  362 GLN  ( 380-) A  -
  517 HIS  ( 535-) A  -
  763 GLN  ( 498-) E  -
 
# 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.
 
   16 HIS  (  34-) A  -   HIS-H   0.32 HIS-E   0.62
  177 HIS  ( 195-) A  -   HIS-H   0.07 HIS-E   0.57
  210 HIS  ( 228-) A  -   HIS-H   0.10 HIS-E   0.60
  221 HIS  ( 239-) A  -   HIS-H   0.11 HIS-E   0.60
  223 HIS  ( 241-) A  -   HIS-H   0.20 HIS-E   0.63
  247 HIS  ( 265-) A  -   HIS-H   0.23 HIS-E   0.61
  327 HIS  ( 345-) A  -   HIS-H   0.24 HIS-E   0.57
  355 HIS  ( 373-) A  -   HIS-H   0.17 HIS-D   0.60
  356 HIS  ( 374-) A  -   HIS-H   0.18 HIS-D   0.58
  360 HIS  ( 378-) A  -   HIS-H   0.13 HIS-D   0.61
  383 HIS  ( 401-) A  -   HIS-H   0.28 HIS-E   0.54
  399 HIS  ( 417-) A  -   HIS-H   0.05 HIS-D   0.56
  475 HIS  ( 493-) A  -   HIS-H   0.10 HIS-D   0.54
  487 HIS  ( 505-) A  -   HIS-H   0.19 HIS-E   0.54
  517 HIS  ( 535-) A  -   HIS-H   0.21 HIS-E   0.57
  522 HIS  ( 540-) A  -   HIS-H   0.23 HIS-E   0.58
  784 HIS  ( 519-) E  -   HIS-H   0.10 HIS-E   0.57
 
# 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.
 
  162 TYR  ( 180-) A  -    OH
  180 ASP  ( 198-) A  -    N
  186 ARG  ( 204-) A  -    NH1
  243 CYS  ( 261-) A  -    N
  247 HIS  ( 265-) A  -    NE2
  249 LEU  ( 267-) A  -    N
  250 GLY  ( 268-) A  -    N
  251 ASP  ( 269-) A  -    N
  252 MET  ( 270-) A  -    N
  255 ARG  ( 273-) A  -    NE
  259 ASN  ( 277-) A  -    N
  322 GLN  ( 340-) A  -    N
  343 CYS  ( 361-) A  -    N
  373 LEU  ( 391-) A  -    N
  379 ASN  ( 397-) A  -    N
And so on for a total of    46 lines.
 
# 98 # 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
   58 GLN  (  76-) A  -    OE1
  223 HIS  ( 241-) A  -    ND1
  362 GLN  ( 380-) A  -    OE1
  481 ASP  ( 499-) A  -    OD1
  653 ASN  ( 388-) E  -    OD1
  704 ASN  ( 439-) E  -    OD1
  758 GLN  ( 493-) E  -  A OE1
 
# 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: 1161
- of which buried: 593
Total number of acceptors: 1288
- of which buried: 493
Total number of donor+acceptors: 152
  (e.g. the Ser Ogamma that can donate and accept)
- of which buried: 31
Buried donors: 593
- without H-bond: 44
- essentially without H-bond: 0
- with only a very poor H-bond: 5
- with a poor H-bond: 8
- with a H-bond: 536
Buried acceptors: 493
- without H-bond: 76
- essentially without H-bond: 0
- with only a very poor H-bond: 5
- with a poor H-bond: 9
- with a H-bond: 403
 
# 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 (   19)   597 (  615) A Protein             /zata/tempdir/6m0...
     2   598 (  333)   791 (  526) E Protein             /zata/tempdir/6m0...
     3   792 (  903)   792 (  903) A Sugar               /zata/tempdir/6m0...
     4   793 (  904)   793 (  904) A Sugar               /zata/tempdir/6m0...
     5   794 (  905)   794 (  905) A Sugar               /zata/tempdir/6m0...
     6   795 (  906)   795 (  906) A Sugar               /zata/tempdir/6m0...
     7   796 (  601)   796 (  601) E Sugar               /zata/tempdir/6m0...
     8   797 (  901)   797 (  901) A  ZN                 /zata/tempdir/6m0...
     9   798 (  902)   798 (  902) A  CL                 /zata/tempdir/6m0...
    10   799 ( HOH )   799 ( HOH ) A water   (    1)     /zata/tempdir/6m0...
    11   800 ( HOH )   800 ( HOH ) E water   (    1)     /zata/tempdir/6m0...
 
# 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.450
  1st generation packing quality :   1.037 (          (  -0.3,  2.5))
  2nd generation packing quality :  -0.894 (          (  -1.4,  1.2))
  Ramachandran plot appearance   :  -3.020 (poor      (  -2.4,  1.5))
  chi-1/chi-2 rotamer normality  :  -3.586 (poor      (  -4.2,  1.7))
  Backbone conformation          :   0.166 (          (  -0.7,  3.6))
  Inside/Outside distribution    :   1.030
 
 RMS Z-scores, should be close to 1.0:
  Bond lengths                   :   0.347 (tight)
  Bond angles                    :   0.633 (tight)
  Omega angle restraints         :   1.042
  Side chain planarity           :   0.437 (tight)
  Improper dihedral distribution :   0.473
  B-factor distribution          :   0.894
 
# 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: Bond length variabilty Z-score low
With a resolution of 1.5-2.5 Angstrom, you might have enough data to warrant
more bond length variability that we observed (less than 0.5). If your
resolution is close to 1.5 Angstrom, you can consider allowing the refinement
software more freedom when it comes to applying the bond length target
restraints. If your resolution is close to 2.5 Angstrom, you can do this too,
but you might want to be a bit careful.
 
# 106 # 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.
 
# 107 # 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.
 
  269 GLN  ( 287-) A  -     13.52
  784 HIS  ( 519-) E  -     12.80
  723 LYS  ( 458-) E  -     12.78
   84 GLN  ( 102-) A  -     12.52
  518 GLU  ( 536-) A  -     12.11
  611 ARG  ( 346-) E  -     11.89
  679 GLN  ( 414-) E  -     11.00
  710 VAL  ( 445-) E  -     10.82
  770 TYR  ( 505-) E  -     10.81
  585 PHE  ( 603-) A  -     10.72
  709 LYS  ( 444-) E  -     10.33
  375 ARG  ( 393-) A  -     10.22
  442 ARG  ( 460-) A  -      7.96
  250 GLY  ( 268-) A  -      3.88
  259 ASN  ( 277-) A  -      3.84
And so on for a total of    70 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.
