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

Date : 2025-04-01
This report was created by WHAT IF version WHATCHECK15.0

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

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

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

Some remarks regarding the output:

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

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

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



=========================================
==== Compound code /zata/tempdir/3snc/wctemp_0cyc/3snc_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                                                        3SNC
ATOM  *****  O   DMS A2309      23.357  35.692 -20.097  1.00 94.29       O   O
ATOM  *****  C1  DMS A2309      26.221  35.814 -19.423  1.00 94.05       C1  C
ATOM  *****  C2  DMS A2309      25.334  37.258 -21.665  1.00 94.32       C2  C
ATOM  *****  O   HOH A 308      20.271  41.044 -20.165  1.00 48.38       308 O
ATOM  *****  O   HOH A 309     -14.951  44.254 -17.634  1.00 56.95       309 O
ATOM  *****  O   HOH A 310      13.911  52.040  -9.238  1.00 39.56       310 O
ATOM  *****  O   HOH A 311     -19.059  48.503  -8.415  1.00 43.60       311 O
ATOM  *****  O   HOH A 312      21.516  38.840 -18.110  1.00 41.96       312 O
ATOM  *****  O   HOH A 313      20.087  55.478  -9.607  1.00 50.52       313 O
ATOM  *****  O   HOH A 314      -0.368  40.406 -10.882  1.00 38.11       314 O
ATOM  *****  O   HOH A 315     -19.613  55.462 -10.079  1.00 65.37       315 O
ATOM  *****  O   HOH A 316      -1.213  28.630  -4.289  1.00 55.68       316 O
ATOM  *****  O   HOH A 317      33.543  19.245  -4.211  1.00 52.24       317 O
ATOM  *****  O   HOH A 318      -1.553  44.410  -8.498  1.00 32.94       318 O
ATOM  *****  O   HOH A 319     -13.690  45.265  -4.071  1.00 42.36       319 O
ATOM  *****  O   HOH A 320      15.982  53.698  -7.685  1.00 54.69       320 O
ATOM  *****  O   HOH A 321      -6.377  42.560  -8.065  1.00 47.03       321 O
ATOM  *****  O   HOH A 322      18.219  31.276 -23.718  1.00 63.99       322 O
ATOM  *****  O   HOH A 323      26.593  14.723 -13.746  1.00 38.50       323 O
ATOM  *****  O   HOH A 324      14.007  24.439   4.128  1.00 58.74       324 O
ATOM  *****  O   HOH A 325     -14.776  71.995 -24.496  1.00 61.06       325 O
ATOM  *****  O   HOH A 326      27.908  45.001 -19.082  1.00 45.53       326 O
ATOM  *****  O   HOH A 327      17.185  50.814 -15.229  1.00 34.98       327 O
ATOM  *****  O   HOH A 328       1.910  61.028 -29.218  1.00 43.68       328 O
ATOM  *****  O   HOH A 329      37.572  37.094  -9.265  1.00 56.47       329 O
ATOM  *****  O   HOH A 330     -15.431  46.592  -5.951  1.00 45.52       330 O
ATOM  *****  O   HOH A 331      -6.481  68.436 -26.315  1.00 54.62       331 O
ATOM  *****  O   HOH A 332      13.315  34.287 -21.740  1.00 49.62       332 O
ATOM  *****  O   HOH A 333       2.637  18.405 -11.839  1.00 52.28       333 O
ATOM  *****  O   HOH A 334       9.542  21.512   0.071  1.00 54.32       334 O
ATOM  *****  O   HOH A 335       2.364  50.730 -26.708  1.00 53.98       335 O
ATOM  *****  O   HOH A 336      15.262  43.926 -20.323  1.00 51.17       336 O
ATOM  *****  O   HOH A 337     -20.215  40.284 -13.195  1.00 62.56       337 O
ATOM  *****  O   HOH A 338      21.403  60.167  -5.706  1.00 58.05       338 O
ATOM  *****  O   HOH A 339      25.313  62.149  -9.684  1.00 60.43       339 O
ATOM  *****  O   HOH A 340      24.806  65.618  -8.000  1.00 68.54       340 O
ATOM  *****  O   HOH A 341     -14.902  75.353 -16.776  1.00 36.46       341 O
ATOM  *****  O   HOH A 342      42.975  32.159 -12.282  1.00 42.50       342 O
ATOM  *****  O   HOH A 343     -10.522  74.921  -9.317  1.00 57.39       343 O
ATOM  *****  O   HOH A 344       2.845  50.441 -19.380  1.00 51.26       344 O
ATOM  *****  O   HOH A 345      -0.094  45.957 -18.957  1.00 64.10       345 O
ATOM  *****  O   HOH A 346      11.854  42.659 -21.690  1.00 53.05       346 O
ATOM  *****  O   HOH A 347      -8.911  72.408 -20.563  1.00 54.19       347 O
ATOM  *****  O   HOH A 348      -9.749  67.258 -28.429  1.00 42.84       348 O
ATOM  *****  O   HOH A 349     -12.441  69.793 -24.362  1.00 49.57       349 O
ATOM  *****  O   HOH A 350      -4.353  70.214  -1.448  1.00 67.81       350 O
ATOM  *****  O   HOH A 351      22.419  23.973   5.518  1.00 66.33       351 O
ATOM  *****  O   HOH A 352      10.520  42.783 -19.472  1.00 53.06       352 O
ATOM  *****  O   HOH A 353      -9.877  63.442 -28.650  1.00 57.90       353 O
ATOM  *****  O   HOH A 354      29.689  22.468  -1.527  1.00 52.21       354 O
ATOM  *****  O   HOH A 355      30.967  34.141 -17.418  1.00 49.92       355 O
ATOM  *****  O   HOH A 356      17.339  45.966 -21.052  1.00 45.82       356 O
ATOM  *****  O   HOH A 357      -0.262  69.409 -33.962  1.00 54.19       357 O
ATOM  *****  O   HOH A 358      -1.380  64.910  -8.445  1.00 64.72       358 O
ATOM  *****  O   HOH A 359      32.234  47.004 -17.169  1.00 50.65       359 O
ATOM  *****  O   HOH A 360      36.458  34.950  -9.392  1.00 55.72       360 O
ATOM  *****  O   HOH A 361      18.083  41.932 -20.795  1.00 52.34       361 O
ATOM  *****  O   ACE H   0      28.591  51.992  -6.948  1.00 95.62       O   O
ATOM  *****  CH3 ACE H   0      30.721  52.143  -5.834  1.00 95.41       CH3 C
ATOM  *****  N   ECC H   5      22.418  39.920  -3.035  1.00 72.66       N   N
ATOM  *****  O   ECC H   5      21.116  36.818  -1.416  1.00 68.16       O   O
ATOM  *****  CA  ECC H   5      21.706  39.135  -2.010  1.00 69.33       CA  C
ATOM  *****  CB  ECC H   5      20.333  39.716  -1.693  1.00 68.56       CB  C
ATOM  *****  CD  ECC H   5      19.177  41.800  -1.072  1.00 62.39       CD  C
ATOM  *****  CG  ECC H   5      20.496  41.076  -1.043  1.00 66.06       CG  C
ATOM  *****  OE1 ECC H   5      18.491  41.785  -2.090  1.00 60.39       OE1 O
ATOM  *****  NE2 ECC H   5      18.848  42.424   0.060  1.00 59.51       NE2 N
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF is trying to recover.
Please check your SOUP carefully after this option finished.
The line in the input file that created this problem is:
ERROR reading coordinate file. WHAT IF 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                                                        3SNC
 
# 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.009274  0.000000  0.002424
  0.000000  0.012127  0.000000
  0.000000  0.000000  0.019385
 
# 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: C 1 2 1
 Number of matrices in space group: 4
 Highest polymer chain multiplicity in structure: 1
 Highest polymer chain multiplicity according to SEQRES: 1
 No explicit MTRIX NCS matrices found in the input file
 Value of Z as found on the CRYST1 card: 0
 Z, symmetry, and molecular multiplicity disagree
 Could it be that Z must be: 4
 
# 6 # Error: Matthews Coefficient (Vm) very high
 
The Matthews coefficient [REF] is defined as the density of the protein
structure in cubic Angstroms per Dalton. Normal values are between 1.5
(tightly packed, little room for solvent) and 4.0 (loosely packed, much
space for solvent). Some very loosely packed structures can get values a bit
higher than that.
 
Numbers this high are almost always caused by giving the wrong value for Z
on the CRYST1 card (or not giving this number at all).
 
 Molecular weight of all polymer chains: 34245.492
 Volume of the Unit Cell V= 458689.781
 Space group multiplicity: 4
 No NCS symmetry matrices (MTRIX records) found in PDB file
 Matthews coefficient for observed atoms and Z is high: Vm= 13.394
 No Matthews coefficient given in REMARK 280
 Could it be that Z must be: 4
 This number is the multiplication of the spacegroup and NCS symmetry count
 Matthews coefficient for observed atoms and corrected Z: Vm= 3.349
 
# 7 # Note: Z missing on CRYST1 card
The messages above seem likely caused by the fact that Z is missing from the
CRYST1 card.
 
# 8 # Note: All atoms are sufficiently far away from symmetry axes
None of the atoms in the structure is closer than 0.77 Angstrom to a proper
symmetry axis.
 
# 9 # Note: Chain identifiers OK
WHAT CHECK has not detected any serious chain identifier problems. But be
aware that WHAT CHECK doesn't care about the chain identifiers of waters.
 
# 10 # Warning: Ligands for which a topology was generated automatically
The topology for the ligands in the table below were determined
automatically. WHAT CHECK uses a local copy of the CCP4 monomer library to
generate topology information for ligands. Be aware that automatic topology
generation is a complicated task. So, if you get messages that you fail to
understand or that you believe are wrong, and one of these ligands is
involved, then check the ligand topology entry first. This topology is either
present in the monomer library, or as a libcheck-generated file in the local
directory.
 
  312 DMS  (2309-) A  -
 
# 11 # Warning: Covalently bound ligands
The ligands in this table are covalently bound to something else. It is
already difficult to automatically generate topologies for ligands,
but when they are covalently bound to something it becomes even more
complicated to do everything right. So, if you get weird error messages
that seem related to this covalent bond, then please feel free to
ignore those, or even better, make a topology entry by hand.
 
The comment `Other ligand` indicates that the covalent bond is to another
ligand. In that case you might want to convert the two ligands into one
bigger ligand.
 
  313 ACE  (   0-) H  -
 
# 12 # Warning: Strange inter-chain connections detected
The pairs of residues listed in the table below seem covalently bound
while belonging to different chains in the PDB file.
 
Sometimes this is unavoidable (e.g. if two protein chains are covalently
connected via a Cys-Cys or other bond). But if it can be avoided (e.g.
often we observe sugars with one chain identifier connected to protein
chains with another chain identifier), it should be avoided. WHAT IF and
WHAT CHECK try to deal with all exceptions thrown at it, but if you want
these programs to work optimally (i.e. make as few false error messages as
is possible) you should help them by getting as much of the administration
correct as is humanly possible.
 
  145 CYS  ( 145-) A  -    SG    314 ECC  (   5-) H  -    C
 
# 13 # Warning: Strange inter-chain connections could NOT be corrected
Often inter-chain connections are simple administrative problems. In this
case not. The observed inter-chain connection(s) either are real, or they
are too strange for WHAT CHECK to correct. Human inspection seems required.
Id: CORCNEU
 
# 14 # Note: No duplicate atom names in ligands
All atom names in ligands (if any) seem adequately unique.
 
# 15 # 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).
 
# 16 # 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).
 
# 17 # Warning: Groups attached to potentially hydrogen-bonding atoms
Residues were observed with groups attached to (or very near to) atoms that
potentially can form hydrogen bonds. WHAT CHECK is not very good at dealing
with such exceptional cases (Mainly because it's author is not...). So be
warned that the hydrogen-bonding related analyses of these residues
might be in error.
 
For example, an aspartic acid can be protonated on one of its delta
oxygens. This is possible because the one delta oxygen 'helps' the
other one holding that proton. However, if a delta oxygen has a group
bound to it, then it can no longer 'help' the other delta oxygen
bind the proton. However, both delta oxygens, in principle, can still
be hydrogen bond acceptors. Such problems can occur in the amino acids
Asp, Glu, and His. I have opted, for now to simply allow no hydrogen
bonds at all for any atom in any side chain that somewhere has a 'funny'
group attached to it. I know this is wrong, but there are only 12 hours
in a day.
 
  307 ASN  (   1-) H  -    N   bound to   313 ACE  (   0-) H  -    C
 
# 18 # 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.
 
# 19 # 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.
 
# 20 # Note: All residues have a complete backbone.
No residues have missing backbone atoms.
 
# 21 # Note: No C-alpha only residues
There are no residues that consist of only an alpha carbon atom.
 
# 22 # 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 (    1)   306 (  306) A Protein             /zata/tempdir/3sn...
     2   307 (    1)   310 (    4) H Prote<-             /zata/tempdir/3sn...
     3   311 (  306)   311 (  306) A Q O2 <-   306       /zata/tempdir/3sn...
     4   312 ( 2309)   312 ( 2309) A DMS                 /zata/tempdir/3sn...
     5   313 (    0)   313 (    0) H ACE  <-             /zata/tempdir/3sn...
     6   314 (    5)   314 (    5) H ECC  <-             /zata/tempdir/3sn...
     7   315 ( HOH )   315 ( HOH ) A water   (    1)     /zata/tempdir/3sn...
MODELs skipped upon reading PDB file: 0
X-ray structure. No MODELs found
The total number of amino acids found is 310.
No nucleic acids observed in input file
No sugars recognized in input file
Number of water molecules: 1
Residue numbers increase monotonously OK
ERROR. File not found:
TAPEOUT.DAT
 
# 23 # 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
 
# 24 # 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 SGFRKMAFPSGKVEGCMVQVTCGTTTLNGLWLDDTVYCPRHVICTAEDMLNPNYEDLLIR
(   1)-(  60)
                     70        80        90       100       110       120
                      |         |         |         |         |         |
   61 -  120 KSNHSFLVQAGNVQLRVIGHSMQNCLLRLKVDTSNPKTPKYKFVRIQPGQTFSVLACYNG
(  61)-( 120)
                    130       140       150       160       170       180
                      |         |         |         |         |         |
  121 -  180 SPSGVYQCAMRPNHTIKGSFLNGSCGSVGFNIDYDCVSFCYMHHMELPTGVHAGTDLEGK
( 121)-( 180)
                    190       200       210       220       230       240
                      |         |         |         |         |         |
  181 -  240 FYGPFVDRQTAQAAGTDTTITLNVLAWLYAAVINGDRWFLNRFTTTLNDFNLVAMKYNYE
( 181)-( 240)
                    250       260       270       280       290       300
                      |         |         |         |         |         |
  241 -  300 PLTQDHVDILGPLSAQTGIAVLDMCAALKELLQNGMNGRTILGSTILEDEFTPFDVVRQC
( 241)-( 300)
 
 
  301 -  306 SGVTFQ
( 301)-( 306)
              310
                |
  307 -  310 NSTS
(   1)-(   4)
 
 
 
 
# 25 # Note: No rounded coordinates detected
No significant rounding of atom coordinates has been detected.
 
# 26 # 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.
 
# 27 # 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.
 
# 28 # Note: All B-factors fall in the range 0.0 - 100.0
All B-factors are larger than zero, and none are observed above 100.0.
 
# 29 # 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.
 
  306 GLN  ( 306-) A  -        OK
  310 SER  (   4-) H  -        OK
 
# 30 # Note: Weights administratively correct
All atomic occupancy factors ('weights') fall in the 0.0--1.0 range, which
makes them administratively correct.
 
# 31 # 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.
 
# 32 # Warning: Occupancy atoms do not add up to 1.0.
In principle, the occupancy of all alternates of one atom should add up till
1.0. A valid exception is the missing atom (i.e. an atom not seen in the
electron density) that is allowed to have a 0.0 occupancy. Sometimes this
even happens when there are no alternate atoms given...
 
Atoms want to move. That is the direct result of the second law of
thermodynamics, in a somewhat weird way of thinking. Any way, many atoms
seem to have more than one position where they like to sit, and they jump
between them. The population difference between those sites (which is related
to their energy differences) is seen in the occupancy factors. As also for
atoms it is 'to be or not to be', these occupancies should add up to 1.0.
Obviously, it is possible that they add up to a number less than 1.0, in
cases where there are yet more, but undetected' rotamers/positions in play,
but also in those cases a warning is in place as the information shown
in the PDB file is less certain than it could have been. The residues
listed below contain atoms that have an occupancy greater than zero, but
their alternates do not add up to one. 'Strange' is added as a comment when
we believe that the structure shows no obvious reasons why this residue
should have a reduced occupancy.
 
WARNING. Presently WHAT CHECK only deals with a maximum of two alternate
positions. A small number of atoms in the PDB has three alternates. In
those cases the warning given here should obviously be neglected!
In a next release we will try to fix this.
 
  153 ASP  ( 153-) A  -   0.50
 
# 33 # 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
 
# 34 # 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
 
# 35 # 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.411 over    2141 bonds
Average difference in B over a bond :    1.05
RMS difference in B over a bond :    1.63
 
# 36 # 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
 
# 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.
 
  222 ARG  ( 222-) A  -
 
# 43 # Note: Tyrosine torsion conventions OK
No errors were detected in tyrosine torsion angle conventions.
 
# 44 # Warning: Phenylalanine convention problem
The phenylalanine residues listed in the table below have their chi-2 not
between -90.0 and 90.0.
 
  291 PHE  ( 291-) A  -
 
# 45 # Note: Aspartic acid torsion conventions OK
No errors were detected in aspartic acid torsion angle conventions.
 
# 46 # Note: Glutamic acid torsion conventions OK
No errors were detected in glutamic acid torsion angle conventions.
 
# 47 # Note: Phosphate group names OK in DNA/RNA
No errors were detected in nucleic acid phosphate group naming conventions
(or this structure contains no nucleic acids).
 
# 48 # Note: Heavy atom naming OK
No errors were detected in the atom names for non-hydrogen atoms. Please
be aware that the PDB wants us to deliberately make some nomenclature errors;
especially in non-canonical amino acids.
 
# 49 # Note: No decreasing residue numbers
All residue numbers are strictly increasing within each chain.
 
# 50 # Note: All bond lengths OK
All bond lengths are in agreement with standard bond lengths using a
tolerance of 4 sigma (both standard values and sigma for amino acids
have been taken from Engh and Huber [REF], for DNA/RNA from Parkinson
et al [REF]).
 
# 51 # Note: Normal bond length variability
Bond lengths were found to deviate normally from the standard bond lengths
(values for Protein residues were taken from Engh and Huber [REF], for
DNA/RNA from Parkinson et al [REF]).
 
 RMS Z-score for bond lengths: 0.728
 RMS-deviation in bond distances: 0.017
 
# 52 # Warning: Possible cell scaling problem
Comparison of bond distances with Engh and Huber [REF] standard values for
protein residues and Parkinson et al [REF] values for DNA/RNA shows a
significant systematic deviation. It could be that the unit cell used in
refinement was not accurate enough. The deformation matrix given below gives
the deviations found: the three numbers on the diagonal represent the
relative corrections needed along the A, B and C cell axis. These values are
1.000 in a normal case, but have significant deviations here (significant at
the 99.99 percent confidence level)
 
There are a number of different possible causes for the discrepancy. First
the cell used in refinement can be different from the best cell calculated.
Second, the value of the wavelength used for a synchrotron data set can be
miscalibrated. Finally, the discrepancy can be caused by a dataset that has
not been corrected for significant anisotropic thermal motion.
 
Please note that the proposed scale matrix has NOT been restrained to obey
the space group symmetry. This is done on purpose. The distortions can give
you an indication of the accuracy of the determination.
 
If you intend to use the result of this check to change the cell dimension
of your crystal, please read the extensive literature on this topic first.
This check depends on the wavelength, the cell dimensions, and on the
standard bond lengths and bond angles used by your refinement software.
 
SCALE matrix obtained from PDB file
  0.009274  0.000000  0.002424
  0.000000  0.012127  0.000000
  0.000000  0.000000  0.019385
Unit Cell deformation matrix
  0.998570  0.001101 -0.000320
  0.001101  0.996172  0.000689
 -0.000320  0.000689  0.997892
Proposed new scale matrix
  0.009288 -0.000012  0.002432
 -0.000013  0.012174 -0.000008
  0.000006 -0.000013  0.019426
With corresponding cell
    A    = 107.676  B   =  82.144  C    =  53.218
    Alpha=  90.000  Beta= 104.694  Gamma=  90.000
 
The CRYST1 cell dimensions
    A    = 107.830  B   =  82.460  C    =  53.320
    Alpha=  90.000  Beta= 104.650  Gamma=  90.000
 
 Variance: 65.880
 (Under-)estimated Z-score: 5.982
 
# 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.
 
   41 HIS  (  41-) A  -    CG   ND1  CE1 109.62    4.0
  175 THR  ( 175-) A  -    C    CA   CB  100.91   -4.8
 
# 54 # Note: Normal bond angle variability
Bond angles were found to deviate normally from the mean standard bond angles
(normal values for protein residues were taken from Engh and Huber [REF], for
DNA/RNA from Parkinson et al [REF]). The RMS Z-score given below is expected
to be near 1.0 for a normally restrained data set, and this is indeed
observed for very high resolution X-ray structures.
 
 RMS Z-score for bond angles: 0.836
 RMS-deviation in bond angles: 1.751
 
# 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.
 
  222 ARG  ( 222-) A  -
 
# 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= 1.093
 
# 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.905
 
# 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 : 1.137
 
# 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 # Error: Ramachandran Z-score very low
The score expressing how well the backbone conformations of all residues
correspond to the known allowed areas in the Ramachandran plot is very low.
 
 Ramachandran Z-score : -4.856
 
# 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.
 
   45 THR  (  45-) A  -   -3.2
  282 LEU  ( 282-) A  -   -2.8
  279 ARG  ( 279-) A  -   -2.6
   43 ILE  (  43-) A  -   -2.5
  102 LYS  ( 102-) A  -   -2.5
  224 THR  ( 224-) A  -   -2.5
  305 PHE  ( 305-) A  -   -2.4
  309 THR  (   3-) H  -   -2.4
  227 LEU  ( 227-) A  -   -2.3
  154 TYR  ( 154-) A  -   -2.3
   78 ILE  (  78-) A  -   -2.2
   60 ARG  (  60-) A  -   -2.2
  225 THR  ( 225-) A  -   -2.2
  177 LEU  ( 177-) A  -   -2.2
  286 ILE  ( 286-) A  -   -2.2
  201 THR  ( 201-) A  -   -2.1
  190 THR  ( 190-) A  -   -2.1
   27 LEU  (  27-) A  -   -2.0
   30 LEU  (  30-) A  -   -2.0
   67 LEU  (  67-) 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.
 
    2 GLY  (   2-) A  - Poor phi/psi
    4 ARG  (   4-) A  - omega poor
    8 PHE  (   8-) A  - Omega to (next) Pro poor
    9 PRO  (   9-) A  - omega poor
   23 GLY  (  23-) A  - Poor phi/psi
   33 ASP  (  33-) A  - Poor phi/psi
   38 CYS  (  38-) A  - Omega to (next) Pro poor
   44 CYS  (  44-) A  - Poor phi/psi
   45 THR  (  45-) A  - Poor phi/psi
   46 ALA  (  46-) A  - Poor phi/psi
   51 ASN  (  51-) A  - Omega to (next) Pro poor
   71 GLY  (  71-) A  - Poor phi/psi
   78 ILE  (  78-) A  - Poor phi/psi
   82 MET  (  82-) A  - omega poor
   84 ASN  (  84-) A  - Poor phi/psi
And so on for a total of    48 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  (  27-) A  -    -1.32
   30 LEU  (  30-) A  -    -1.32
   50 LEU  (  50-) A  -    -1.32
   67 LEU  (  67-) A  -    -1.31
   75 LEU  (  75-) A  -    -1.32
  141 LEU  ( 141-) A  -    -1.30
  177 LEU  ( 177-) A  -    -1.32
  227 LEU  ( 227-) A  -    -1.32
  232 LEU  ( 232-) A  -    -1.32
  268 LEU  ( 268-) A  -    -1.32
  282 LEU  ( 282-) A  -    -1.32
   32 LEU  (  32-) A  -    -1.26
   43 ILE  (  43-) A  -    -1.25
   57 LEU  (  57-) A  -    -1.27
   59 ILE  (  59-) A  -    -1.25
And so on for a total of   181 lines.
 
# 67 # Error: chi-1/chi-2 angle correlation Z-score very low
The score expressing how well the chi-1/chi-2 angles of all residues
correspond to the populated areas in the database is
very low.
 
 chi-1/chi-2 correlation Z-score : -7.155
 
# 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.
 
  225 THR  ( 225-) A  -   0.35
  187 ASP  ( 187-) A  -   0.37
  102 LYS  ( 102-) A  -   0.38
 
# 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!
 
   44 CYS  (  44-) A  -       0
   46 ALA  (  46-) A  -       0
   85 CYS  (  85-) A  -       0
  154 TYR  ( 154-) A  -       0
  165 MET  ( 165-) A  -       0
  276 MET  ( 276-) A  -       0
   43 ILE  (  43-) A  -       1
  182 TYR  ( 182-) A  -       1
   47 GLU  (  47-) A  -       2
  290 GLU  ( 290-) 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.756
 
# 71 # Warning: Omega angle restraints not strong enough
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 of
this distribution is above 7.0, which indicates that the omega values have
been under-restrained.
 
Omega average and std. deviation= 178.660 7.074
 
# 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].
 
   39 PRO  (  39-) A  -  102.1 envelop C-beta (108 degrees)
  241 PRO  ( 241-) A  - -123.2 half-chair C-delta/C-gamma (-126 degrees)
 
# 74 # Note: Backbone oxygen evaluation OK
All residues for which similar local backbone conformations could be found
in the WHAT CHECK database have a backbone oxygen position that has been
observed at least a few times in that database.
 
# 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.
 
   34 ASP  (  34-) A  - TT+   Highly likely
  275 GLY  ( 275-) A  - TT+   Highly likely
   51 ASN  (  51-) A  - TT+   Likely
   64 HIS  (  64-) A  - TT+   Likely
   72 ASN  (  72-) A  - TT+   Likely
   78 ILE  (  78-) A  - TT+   Likely
   85 CYS  (  85-) A  - TT+   Likely
  109 GLY  ( 109-) A  - TT+   Likely
  155 ASP  ( 155-) A  - TT+   Likely
  170 GLY  ( 170-) A  - TT+   Likely
  189 GLN  ( 189-) A  - TT+   Likely
  219 PHE  ( 219-) A  - TT+   Likely
  277 ASN  ( 277-) A  - TT+   Likely
  279 ARG  ( 279-) A  - TT+   Likely
 
# 76 # Error: Abnormally short interatomic distances
The pairs of atoms listed in the table below have an unusually short
distance; each bump is listed in only one direction,
 
The contact distances of all atom pairs have been checked. Two atoms are
said to `bump' if they are closer than the sum of their Van der Waals radii
minus 0.40 Angstrom. For hydrogen bonded pairs a tolerance of 0.55 Angstrom
is used. The first number in the table tells you how much shorter that
specific contact is than the acceptable limit. The second distance is the
distance between the centres of the two atoms.
 
The last text-item on each line represents the status of the atom pair. The
text `INTRA' means that the bump is between atoms that are explicitly listed
in the PDB file. `INTER' means it is an inter-symmetry bump. If the final
column contains the text 'HB', the bump criterion was relaxed because there
could be a hydrogen bond. Similarly relaxed criteria are used for 1--3 and
1--4 interactions (listed as 'B2' and 'B3', respectively). If the last column
is 'BF', the sum of the B-factors of the atoms is higher than 80, which makes
the appearance of the bump somewhat less severe because the atoms probably
are not there anyway. BL, on the other hand, indicates that the bumping atoms
both have a low B-factor, and that makes the bumps more worrisome.
 
It seems likely that at least some of the reported bumps are caused by
administrative errors in the chain names. I.e. covalently bound atoms with
different non-blank chain-names are reported as bumps. In rare cases this is
not an error.
 
Bumps between atoms for which the sum of their occupancies is lower than one
are not reported. If the MODEL number does not exist (as is the case in most
X-ray files), a minus sign is printed instead.
 
   45 THR  (  45-) A  -    CG2  <-->     46 ALA  (  46-) A  -    N    0.61    2.39  INTRA BF
   22 CYS  (  22-) A  -    SG   <-->     61 LYS  (  61-) A  -    NZ   0.37    2.93  INTRA BF
  131 ARG  ( 131-) A  -    NH2  <-->    289 ASP  ( 289-) A  -    CG   0.34    2.76  INTRA BL
   47 GLU  (  47-) A  -    O    <-->     49 MET  (  49-) A  -    N    0.34    2.36  INTRA BF
   47 GLU  (  47-) A  -    C    <-->     49 MET  (  49-) A  -    N    0.32    2.58  INTRA BF
  131 ARG  ( 131-) A  -    O    <-->    134 HIS  ( 134-) A  -    N    0.32    2.38  INTRA BL
   34 ASP  (  34-) A  -    OD1  <-->     90 LYS  (  90-) A  -    NZ   0.31    2.39  INTRA BF
  242 LEU  ( 242-) A  -    CD1  <-->    246 HIS  ( 246-) A  -    CB   0.30    2.90  INTRA BL
   45 THR  (  45-) A  -    OG1  <-->     46 ALA  (  46-) A  -    N    0.30    2.30  INTRA BF
  131 ARG  ( 131-) A  -    NH2  <-->    289 ASP  ( 289-) A  -    OD1  0.28    2.42  INTRA BL
   45 THR  (  45-) A  -    CB   <-->     46 ALA  (  46-) A  -    N    0.26    2.44  INTRA BF
  221 ASN  ( 221-) A  -    ND2  <-->    270 GLU  ( 270-) A  -    OE1  0.25    2.45  INTRA BF
  107 GLN  ( 107-) A  -    N    <-->    110 GLN  ( 110-) A  -    OE1  0.24    2.46  INTRA BL
   63 ASN  (  63-) A  -    OD1  <-->     78 ILE  (  78-) A  -    C    0.23    2.57  INTRA BF
  138 GLY  ( 138-) A  -    N    <-->    172 HIS  ( 172-) A  -    CD2  0.20    2.90  INTRA BL
And so on for a total of    57 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: 7.999
Total bump value per residue: 0.184
Total number of bumps: 57
Total squared bump value: 1.941
Total number of bumps in the mildest bin: 45
Total number of bumps in the second bin: 11
Total number of bumps in the middle bin: 1
Total number of bumps in the fourth bin: 0
Total number of bumps in the worst bin: 0
 
# 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 : 0.986
 
# 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 # 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.
 
  222 ARG  ( 222-) A  -  -7.00
  154 TYR  ( 154-) A  -  -6.52
   97 LYS  (  97-) A  -  -6.02
   60 ARG  (  60-) A  -  -5.92
  305 PHE  ( 305-) A  -  -5.74
  107 GLN  ( 107-) A  -  -5.37
  279 ARG  ( 279-) A  -  -5.25
  141 LEU  ( 141-) A  -  -5.19
 
# 82 # 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.
 
# 83 # Note: Structural average packing environment OK
The structural average packing score is within normal ranges.
 
 
Average for range     1 -  310 :  -0.895
 
# 84 # 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
 
# 85 # 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.
 
  276 MET  ( 276-) A  -  -2.84
 
# 86 # 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
 
# 87 # 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
 
# 88 # 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.
 
# 89 # Note: Water contacts OK
All water clusters make at least one contact with a non-water atom.
 
# 90 # Note: No waters need moving
All water molecules are sufficiently close to the asymmetric unit given in
the input file.
 
# 91 # Note: Water hydrogen bonds OK
All water molecules can form hydrogen bonds.
 
# 92 # 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.
 
   41 HIS  (  41-) A  -
   63 ASN  (  63-) A  -
  127 GLN  ( 127-) A  -
  172 HIS  ( 172-) A  -
 
# 93 # 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.
 
   41 HIS  (  41-) A  -   HIS-H   0.23 HIS-E   0.56
   64 HIS  (  64-) A  -   HIS-H   0.24 HIS-E   0.58
   80 HIS  (  80-) A  -   HIS-H   0.14 HIS-E   0.59
  134 HIS  ( 134-) A  -   HIS-H   0.20 HIS-E   0.53
  163 HIS  ( 163-) A  -   HIS-H   0.28 HIS-E   0.64
  164 HIS  ( 164-) A  -   HIS-H   0.18
  172 HIS  ( 172-) A  -   HIS-H   0.25 HIS-E   0.54
  246 HIS  ( 246-) A  -   HIS-H   0.39 HIS-E   0.60
 
# 94 # 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.
 
   34 ASP  (  34-) A  -    N
   41 HIS  (  41-) A  -    N
   45 THR  (  45-) A  -    N
   63 ASN  (  63-) A  -    ND2
   64 HIS  (  64-) A  -    N
   68 VAL  (  68-) A  -    N
   73 VAL  (  73-) A  -    N
  126 TYR  ( 126-) A  -    OH
  145 CYS  ( 145-) A  -    N
  148 VAL  ( 148-) A  -    N
  152 ILE  ( 152-) A  -    N
  171 VAL  ( 171-) A  -    N
  185 PHE  ( 185-) A  -    N
  186 VAL  ( 186-) A  -    N
  188 ARG  ( 188-) A  -    N
  189 GLN  ( 189-) A  -    N
  190 THR  ( 190-) A  -    N
  194 ALA  ( 194-) A  -    N
  198 THR  ( 198-) A  -    N
  219 PHE  ( 219-) A  -    N
  223 PHE  ( 223-) A  -    N
  253 LEU  ( 253-) A  -    N
  263 ASP  ( 263-) A  -    N
  288 GLU  ( 288-) A  -    N
  291 PHE  ( 291-) A  -    N
 
# 95 # 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.
 
  192 GLN  ( 192-) A  -    OE1
 
# 96 # 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: 443
- of which buried: 228
Total number of acceptors: 478
- of which buried: 181
Total number of donor+acceptors: 56
  (e.g. the Ser Ogamma that can donate and accept)
- of which buried: 15
Buried donors: 228
- without H-bond: 25
- essentially without H-bond: 0
- with only a very poor H-bond: 3
- with a poor H-bond: 2
- with a H-bond: 198
Buried acceptors: 181
- without H-bond: 35
- essentially without H-bond: 0
- with only a very poor H-bond: 2
- with a poor H-bond: 7
- with a H-bond: 137
 
# 97 # 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 (    1)   306 (  306) A Protein             /zata/tempdir/3sn...
     2   307 (    1)   310 (    4) H Prote<-             /zata/tempdir/3sn...
     3   311 (  306)   311 (  306) A Q O2 <-   306       /zata/tempdir/3sn...
     4   312 ( 2309)   312 ( 2309) A DMS                 /zata/tempdir/3sn...
     5   313 (    0)   313 (    0) H ACE  <-             /zata/tempdir/3sn...
     6   314 (    5)   314 (    5) H ECC  <-             /zata/tempdir/3sn...
     7   315 ( HOH )   315 ( HOH ) A water   (    1)     /zata/tempdir/3sn...
 
# 98 # 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.580
  1st generation packing quality :  -0.988 (          (  -0.5,  2.5))
  2nd generation packing quality :  -2.039 (          (  -1.5,  1.2))
  Ramachandran plot appearance   :  -4.856 (bad       (  -2.7,  1.6))
  chi-1/chi-2 rotamer normality  :  -7.155 (bad       (  -4.5,  1.7))
  Backbone conformation          :  -0.756 (          (  -0.8,  3.7))
  Inside/Outside distribution    :   0.986
 
 RMS Z-scores, should be close to 1.0:
  Bond lengths                   :   0.728
  Bond angles                    :   0.836
  Omega angle restraints         :   1.286 (loose)
  Side chain planarity           :   0.595 (tight)
  Improper dihedral distribution :   0.905
  B-factor distribution          :   0.411
 
# 99 # 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.
 
# 100 # 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.
 
# 101 # Note: Cell parameter anomaly
WHAT CHECK has compared the observed bond lengths with the Engh and Huber
parameters, and has done this as function of the direction of the bond
relative to the cell axes. From this analysis it was concluded that the
cell dimensions are probably not entirely perfect. The problem is not very
big, so you do not need to fix this before you start dealing with the other
suggestions, but you better fix this.
 
If this problem is caused by refining with another set of target values
than the Engh and Huber values, then WHAT CHECK cannot help you because
systematic target value deviations can also cause this message to pop up.
 
# 102 # Error: Bumps in your structure
Upon analysing the bumps in your structure, WHAT CHECK got a bit
worried. Sometimes this means that you have forgotten to lower the
occupancy of overlapping ligands, residues, or water molecules. But,
whatever is the origin of this problem, you have to analyse it and
fix it.
 
# 103 # Note: Bond angle variabilty Z-score high
With a resolution of 2.5-3.0 Angstrom, you dont have enough data to warrant
the bond angle variability that we observed (almost 1.0). So, you better
tighten
the screws on the bond angle target values a bit.
 
# 104 # Note: Omega angles insufficiently restraint
Omega angles tend to fall around 178 degrees with a standard deviation of 5.5
degrees. With a resolution of 2.5-3.0 Angstrom, you dont have enough data to
warrant the omega angle variability that we observed. The variability is
larger than 7.0 degrees. So, tighten the screws on the omega angle target
values a bit.
 
# 105 # Note: His, Asn, Gln side chain flips.
His, Asn, and Gln have an asymmetry in their side chain that is hard to
detect unless you have data at much better than 1.0 Angstrom resolution.
WHAT CHECK thinks that your structure contains His, Asn, or Gln residues that
will make better hydrogen bonds when flipped around their chi-2, chi-2, or
chi-3 side chain torsion angle, respectively. You better
check these Asn, His, and Gln residues, and if you use a refinement program
that includes molecular dynamics, then you must (after the
flips were made) refine a bit further before running WHAT CHECK again.
 
# 106 # Warning: Troublesome residues
The residues listed in the table below need to be inspected
 
This table is a very rough attempt to sort the residues according to how
badly they need your attention. The idea is that when you sit in  in front
of the graphics screen and study the residues with the electron density
present that you improve the structure most by dealing with the top residues
in this list first.
 
  131 ARG  ( 131-) A  -     17.26
  107 GLN  ( 107-) A  -     14.64
  222 ARG  ( 222-) A  -     13.99
  306 GLN  ( 306-) A  -     13.32
  154 TYR  ( 154-) A  -     13.18
  289 ASP  ( 289-) A  -     12.09
   97 LYS  (  97-) A  -     12.04
   60 ARG  (  60-) A  -     11.93
  305 PHE  ( 305-) A  -     11.57
  279 ARG  ( 279-) A  -     10.69
  141 LEU  ( 141-) A  -     10.38
  172 HIS  ( 172-) A  -      6.78
   41 HIS  (  41-) A  -      6.01
  134 HIS  ( 134-) A  -      5.17
  242 LEU  ( 242-) A  -      4.88
And so on for a total of    40 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.
