********************************************************************************
Version 2.0.6
********************************************************************************

OEChem 2.0.6
================================================================================

New features
--------------------------------------------------------------------------------

* The performance of the SDF V3000 format file parsing has been significantly
  improved and is now approximately 50% faster.
  The speed of importing an SDF file in V3000 format is now comparable to V2000.
  See table :ref:`table_ImportPerformance_V3000` below that shows the improvements.

.. _table_ImportPerformance_V3000:

.. list-table:: **Performance improvement of importing SDF V3000 file format**

   * - .. image:: ../../releasenotes/images/2016-Feb/ImportPerformance-V3000.*
          :width: 300 pt
     - .. image:: ../../releasenotes/images/2016-Feb/ImportPerformance-V3000-PATH.*
          :width: 300 pt

.. note::

   There are some pathological cases when only a slight improvement
   has been achieved.  From the parsing viewpoint, a pathological or
   atypical SDF V3000 file contains an excessive number of non-default
   property values, redundantly specified atom or bond properties,
   and/or atom coordinates in scientific notation which requires a more
   general but slower parsing activity.  For typical SDF V3000 files,
   a significant improvement was seen, but generally the magnitude of
   the improvement is largely input data dependent.

.. oe:language:: c++ csharp

   * :oe:func:`OEChem::OEWriteMolToString` and
     :oe:func:`OEChem::OEReadMolFromString` overload functions have been
     added to allow specification of the file format using the
     :ref:`the OEFormat namespace <OEChem_OEFormat>`.

.. oe:language:: python

   * :oe:func:`OEChem::OEWriteMolToBytes` and
     :oe:func:`OEChem::OEReadMolFromBytes` overload functions have been
     added to allow specification of the file format using the
     :ref:`the OEFormat namespace <OEChem_OEFormat>`.

.. oe:language:: java

   * :oe:func:`OEChem::OEWriteMolToByteArray` and
     :oe:func:`OEChem::OEReadMolFromByteArray` overload functions have been
     added to allow specification of the file format using the
     :ref:`the OEFormat namespace <OEChem_OEFormat>`.

* :oe:meth:`OEChem::OEMolBase::Clear` performance has been
  improved whenever the molecule is already empty.

* The following flavors have been added to the
  :oe:constns:`OEChem::OEOFlavor::MOL2`
  namespace: :oe:const:`OEChem::OEOFlavor::MOL2::Forcefield`,
  :oe:const:`OEChem::OEOFlavor::MOL2::ChargePrecision`, and
  :oe:const:`OEChem::OEOFlavor::MOL2::GeneralFFFormat`.
  These flavors allow writing nonstandard variants of Tripos MOL2 files
  targeted at the general force field community.

Major bug fixes
--------------------------------------------------------------------------------

* :oe:func:`OEChem::OEMMFF94PartialCharges` function no longer crashes with
  incorrect atom types.

* :oe:func:`OEChem::OEUniMolecularRxn` function no longer crashes when 
  bonds to mapped explicit hydrogens are deleted.

Minor bug fixes
--------------------------------------------------------------------------------

* :oe:func:`OEChem::OESortConfsByTag` function can now sort conformations by
  generic data with double type.

* :oe:meth:`OEChem::OE2DRingDictionary::AddRings` method now allows the addition of ring templates
  with extremely high average bond length. These ring templates are normalized before
  inserting them into the ring dictionary.

* **OEChem TK**'s MDL V2000 and V3000 readers have been improved  
  to handle nonstandard or incorrect MDL or SDF files.

  * :oe:func:`OEChem::OEReadMolecule` now warns about invalid
    bond stereo marks on non-single bond types and will ignore them.  Additionally, a common
    error in CTfile format files is the presence of a "wedge either" bond on a double bond.
    This latter error is now automatically changed to the assumed (non-wedge) "double either"
    bond mark and a warning is generated.

  * :oe:func:`OEChem::OEReadMolecule` now attempts to read a
    variant of the SDFile format that contains blank line(s) before the start of the
    SD data appendices.  Although this is a deviation from the CTfile format,
    this format has been known to occur in the wild. This change now impacts the use of
    concatenated MOL files when the structures have blank molecule titles.
    In general, concatenated MOL files are a much less preferred strategy for multiple
    record structure input and should be avoided. It is highly recommended to always use
    SDF files for multi-record input since an explicit record delimiter is always present.

  * When :oe:func:`OEChem::OEReadMolecule` encounters a connection table
    format error for SDF format files, it now advances to the next record delimiter.
    Previously, it would have attempted to reset and reread at an arbitrary point in the
    corrupted file, possibly generating additional warnings.

  * :oe:func:`OEChem::OEReadMolecule` and low level MDL format readers are now more tolerant
    for V3000 format files that contain  arbitrary collection types.  Previously, only
    stereo collections and highlight collections were allowed. Now a message about
    unknown types generates the warning
    ``Skipping unknown collection type, XXX/YYY``, with ``XXX/YYY`` indicating
    the specific collection type that was ignored.  Unknown collection information
    is not persisted to any output format types: it is well and truly skipped!

  * A warning is now thrown when multiple rgroup label sites (e.g., R1R2)
    are encountered, indicating that this type of representation is not yet supported.

  * When reading V3000 format containing pseudo-atoms (i.e., atoms not in the internal
    **OpenEye** element list), the atom symbol information is no longer lost
    but can be retrieved from :oe:meth:`OEChem::OEAtomBase::GetName` and is now the same 
    as V2000 file format handling.

* When an :oe:const:`OEChem::OEMolBaseType::OEMiniMol` molecule
  implementation is instantiated from another :ref:`OEMolBase <OEChem_OEMolBase>` instance that
  contains one or more atoms, the dimension code is also copied so that
  :oe:meth:`OEChem::OEMolBase::GetDimension`
  matches the dimension setting from the original :ref:`OEMolBase <OEChem_OEMolBase>`
  instance.

* :oe:func:`OEChem::OEReadMolecule` is now more tolerant
  for SKC format files containing explicit string tags of 0-length.

* :oe:func:`OEChem::OEAssignHybridization` now ignores transition metals,
  lanthanides, and actinides and sets their hybridization to
  :oe:const:`OEChem::OEHybridization::Unknown`.
  As a result, these atoms are no longer inadvertently considered to be potential tetrahedral
  stereocenters.

* :ref:`OEMolDatabase <OEChem_OEMolDatabase>` cannot support file formats without explicit
  record delimiters, so files such as MOL, MDL, and RXN
  cannot be supported.
  A properly formatted SDF file is the preferred input to initialize the
  :ref:`OEMolDatabase <OEChem_OEMolDatabase>` class.

* :ref:`OEMolDatabase <OEChem_OEMolDatabase>` now fails early and refuses to
  parse the junk data when a file changes underneath an  
  :ref:`OEMolDatabase <OEChem_OEMolDatabase>`.
  This can happen when an NFS client changes a file that is already open on 
  another NFS directory, invalidating the NFS client that is using
  :ref:`OEMolDatabase <OEChem_OEMolDatabase>`.

* :oe:func:`OEChem::OESweepRotorCompressHydrogens`
  no longer returns ``false`` when the molecule passed in does not
  contain any hydrogens. However, it returns ``false`` if the
  molecule contains any deleted atoms, as it is then likely that
  the rotor compression data is already corrupted.

* :oe:func:`OEMath::OEGeom3DMatrixInvert` function has been fixed. 

* A bug that allowed the ``!DEFAULT`` value of a parameter in the configuration 
  file to be set to a value that is illegal for that parameter has been fixed.
  A warning is now thrown when an illegal value is set. 

* A bug that caused PDB Data records, such as ``REMARK`` and ``SSBON``, to be
  clipped at 72 characters instead of 80 characters has been fixed.

C++-specific changes
--------------------------------------------------------------------------------

* A const :ref:`OEGraphMol <OEChem_OEGraphMol>`,
  :ref:`OEMol <OEChem_OEMol>`, or :ref:`OEQMol <OEChem_OEQMol>` no longer
  results in a compilation error when using the following generic
  data getters that should have been previously marked ``const`` in the header file:
  :oe:meth:`GetBoolData<OESystem::OEBase::GetBoolData>`, 
  :oe:meth:`GetIntData<OESystem::OEBase::GetIntData>`, 
  :oe:meth:`GetFloatData<OESystem::OEBase::GetFloatData>`,
  :oe:meth:`GetDoubleData<OESystem::OEBase::GetDoubleData>`, and
  :oe:meth:`GetStringData<OESystem::OEBase::GetStringData>`.

* :oe:func:`OEChem::OEPRECompress` that outputs an
  :ref:`OEMol <OEChem_OEMol>` has been deprecated in favor of the
  :oe:func:`OEFastROCS::OEPrepareFastROCSMol` function. 
  This function will be removed in a future release.

  .. note::

     :oe:func:`OEChem::OEPRECompress` that alters the binary IO
     handlers on an :ref:`oemolstreambase <OEChem_oemolstreambase>` is still
     supported and is the appropriate way to turn on PRE-compressed ``OEB``.


Python-specific changes
--------------------------------------------------------------------------------

* Passing ``None`` to the :ref:`oemolistream <OEChem_oemolistream>` and :ref:`oemolostream <OEChem_oemolostream>`
  constructors no longer results in a crash.

Documentation changes
--------------------------------------------------------------------------------

* :oe:func:`OEChem::OEDeleteEverythingExceptTheFirstLargestComponent` function 
  is now documented. 
  
OEBio 2.0.6
================================================================================

New features
--------------------------------------------------------------------------------

* :oe:meth:`OEBio::OESplitMolComplexOptions::SetSplitCovalentCofactors` and
  :oe:meth:`OEBio::OESplitMolComplexOptions::GetSplitCovalentCofactors` methods have
  been added to control the splitting of covalent cofactors from a macromolecular complex.
  The new constant :oe:const:`OEBio::OESplitMolComplexSetup::CovCofactor` controls whether
  :oe:func:`OEBio::OEConfigureSplitMolComplexOptions` sets up command-line parsing
  for this option.

* :ref:`OEMolComplexCategorizer <OEBio_OEMolComplexCategorizer>` can now recognize a multi-residue
  :ref:`OEAtomBondSet <OEChem_OEAtomBondSet>` as a covalently attached ligand or cofactor.

* :oe:const:`AminoAcid<OEBio::OEResidueDatabaseCategory::AminoAcid>`,
  a new residue database category, has been introduced. 
  It consists of standard amino acids and common variants
  such as seleno-methionine. Previously, these had been listed in the category
  :oe:const:`Cofactor<OEBio::OEResidueDatabaseCategory::Cofactor>`.

* :oe:meth:`OEBio::OESplitMolComplexOptions::SetWarnNoLigand` and
  :oe:meth:`OEBio::OESplitMolComplexOptions::GetWarnNoLigand` methods have been
  added to control whether the molecular complex splitting functions generate
  a verbose message warning whenever a ligand is not identified.

* :oe:func:`OEBio::OEClearMolComplexSDData` function has been added to remove
  SD tags generated by :oe:func:`OEBio::OEGetMolComplexComponents`.

* :oe:func:`OEBio::OEGetAlignments` has been added to deal with multiple chains
  in each structure. The method returns an iterator of alignments, one for
  each pairwise chain alignment.  
  :oe:func:`OEBio::OEGetAlignment` now returns the highest scored alignment 
  from :oe:func:`OEBio::OEGetAlignments`.
  :oe:func:`OEBio::OEGetSimpleAlignment` is
  a replacement for :oe:func:`OEBio::OEGetAlignment`, which only looks at the first 
  chain in each sequence.

* :oe:func:`OEBio::OEWriteAlignment` has gained a third parameter to allow varying
  the width of the output.

* The following methods have been added to the :ref:`OESequenceAlignment <OEBio_OESequenceAlignment>` class:

  * :oe:meth:`OEBio::OESequenceAlignment::GetChainID`
  * :oe:meth:`OEBio::OESequenceAlignment::GetSequenceIdentity`
  * :oe:meth:`OEBio::OESequenceAlignment::GetSequenceSimilarity`.


Minor bug fixes
--------------------------------------------------------------------------------

* Titles generated by functions :oe:func:`OEBio::OESplitMolComplex` and
  :oe:func:`OEBio::OEGetMolComplexComponents` no longer contain single quotes or
  blank characters.

* Ongoing maintenance has been performed in the :ref:`OEResidueCategoryData <OEBio_OEResidueCategoryData>`
  database used by :ref:`OESplitMolComplexOptions <OEBio_OESplitMolComplexOptions>`. Residues have been
  removed from the :oe:const:`Polymer<OEBio::OEResidueDatabaseCategory::Polymer>` and
  :oe:const:`Misc<OEBio::OEResidueDatabaseCategory::Misc>` lists.

Documentation changes
--------------------------------------------------------------------------------

* The examples have been updated to perceive residues when this is
  not performed by the default molecule reader activity (for example, in the case of :file:`.mol2`).
  With this update, examples that had previously been transforming input
  hydrogen names from a PDB file to the new nomenclature
  (``closecontacts``, ``makealpha``, ``subsetres``, and ``swapaieres``)
  now retain the input hydrogen names.


OESystem 2.0.6
================================================================================

New features
--------------------------------------------------------------------------------

* :ref:`OEThreadedDots <OESystem_OEThreadedDots>` has been added to provide a
  thread-safe way to output progress bar dots to the terminal when the
  work is being updated from multiple threads simultaneously.

OEPlatform 2.0.6
================================================================================

* Minor internal improvements have been made.

OEGrid 1.5.3
================================================================================

Major bug fixes
--------------------------------------------------------------------------------

* :oe:func:`OESystem::OEMakeGridFromCenterAndExtents` now
  propagates errors with the grid construction.

* :oe:func:`OESystem::OEReadGrid` can now read a gzipped
  `OESystem::OEFizzGrid`.

