OEMedChem TK 1.0.4
================================================================================

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

* A major overhaul of the fragmentation internals of
  :ref:`OEMCSFragDatabase <OEMedChem_OEMCSFragDatabase>` now allows an arbitrary number of
  fragmentation cuts.   Additionally, an experimental capability for
  performing limited ring bond fragmentation cuts has been provided.
  Because of the combinatorial explosion of fragments generated with
  increased fragmentation cuts, care should be used when determining
  fragmentation cut limits.  The enhanced ability to do arbitrary N-cut
  fragmentation makes the MCS results from the fragmentation approach much
  closer to an :ref:`OEMCSSearch <OEChem_OEMCSSearch>` mapping result, with better
  overall performance than a mapping approach. To specify the fragmentation
  cut limits, see
  :oe:meth:`OEMedChem::OEMCSFragDatabaseOptions::SetFragLimits`,
  :oe:meth:`OEMedChem::OEMCSFragDatabaseOptions::GetMinFragLimit`,
  :oe:meth:`OEMedChem::OEMCSFragDatabaseOptions::GetMaxFragLimit`,
  :oe:meth:`OEMedChem::OEMCSFragDatabaseOptions::SetRingFragLimit`, and
  :oe:meth:`OEMedChem::OEMCSFragDatabaseOptions::GetRingFragLimit`.

* A new method, :oe:meth:`OEMedChem::OEMCSFragDatabase::IsIndexed`, has been
  added to determine whether a particular molecule index has been
  registered in the database.  Depending on the indexing option settings, a
  particular molecule may be rejected from indexing.  This method
  allows that condition to be interrogated.

* A new method, :oe:meth:`OEMedChem::OEMatchedPairAnalyzerOptions::HasIndexableFragmentHeavyAtomRange`, has
  been added to allow an options object to indicate that a ``min-max``
  range has been specified via
  :oe:meth:`OEMedChem::OEMatchedPairAnalyzerOptions::SetIndexableFragmentRange`.

* The :ref:`OEMatchedPairAnalyzerOptions <OEMedChem_OEMatchedPairAnalyzerOptions>` options class
  now supports the ``operator==`` comparison to more easily determine the
  equality of two options objects.

* :oe:func:`OEMedChem::OEConfigureMatchedPairIndexOptions` and
  :oe:func:`OEMedChem::OEConfigureMCSFragDatabaseOptions` now support
  an ``-allfrags`` option to clear the ``min-max`` indexing constraint and to
  allow the indexing of all fragments.  Indexing all fragments has
  indexing size and indexing performance implications
  for :ref:`OEMCSFragDatabase <OEMedChem_OEMCSFragDatabase>`
  and :ref:`OEMatchedPairAnalyzer <OEMedChem_OEMatchedPairAnalyzer>` objects.

* The :oe:func:`OEMedChem::OEConfigureMCSFragDatabaseOptions` function now
  supports the newly added ``-minfragcuts``, ``-maxfragcuts``, and
  ``-ringcuts`` options.

* :oe:func:`OEMedChem::OEReadMatchedPairAnalyzer` now
  supports the ability to merge indices generated from segments of a large
  set of input structures.  This capability can be used in a
  parallel processing approach to increase the throughput of the
  time-consuming structure indexing phase.

Preliminary Fragmentation API
--------------------------------------------------------------------------------

* New :term:`Preliminary API` methods have been added to allow the
  interrogation of intermediate fragmentation output and internal index
  information from the :ref:`OEMCSFragDatabase <OEMedChem_OEMCSFragDatabase>` object.
  See :oe:meth:`OEMedChem::OEMCSFragDatabase::MoleculeToCores`,
  :oe:meth:`OEMedChem::OEMCSFragDatabase::CoreToMolecules`,
  :oe:meth:`OEMedChem::OEMCSFragDatabase::CoreToMoleculeCount`,
  :oe:meth:`OEMedChem::OEMCSFragDatabase::GetMaxCoreMolecule`, and
  :oe:meth:`OEMedChem::OEMCSFragDatabase::GetMaxCoreMoleculeCount`.

* A new example has been provided to demonstrate using the new
  experimental fragment API of :ref:`OEMCSFragDatabase <OEMedChem_OEMCSFragDatabase>`.
  See ``MCSFragOccurrence.py``.

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

* A bug that resulted in the return of ``[R1][R2]`` fragments in the
  Matched Molecular Pair transforms returned by
  :oe:func:`OEMedChem::OEMatchedPairGetTransforms` has been fixed.

* The :oe:meth:`OEMedChem::OEMCSFragDatabase::GetScores` has been changed
  to make the API more consistent with :ref:`OEFPDatabase <OEGraphSim_OEFPDatabase>`.
  The ``end`` range argument is now exclusive instead of inclusive when a
  non-zero value is specified.

* The :oe:meth:`OEMedChem::OEMCSFragDatabase::GetScores` and
  :oe:meth:`OEMedChem::OEMCSFragDatabase::GetSortedScores` methods
  previously returned an arbitrary :ref:`OEMCSMolSimScore <OEMedChem_OEMCSMolSimScore>`
  when different identified cores had the same score (in particular for
  :oe:const:`OEMedChem::OEMCSScoreType::AtomCount` scoring).
  This has been fixed.

* The undocumented internal debugging method
  ``OEMedChem::OEMCSFragDatabase::Dump`` has been removed from the public API.

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

* Minor changes to some examples were made to synchronize
  the behavior and output with other wrapped language examples.

Java-specific changes
--------------------------------------------------------------------------------

* Minor changes to some examples were made to synchronize the
  behavior and output with other wrapped language examples.

C#-specific changes
--------------------------------------------------------------------------------

* Minor changes to some examples were made to synchronize the
  behavior and output with other wrapped language examples.

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

* New methods have been documented in their respective classes.
