******************************
OEToolkits 2018.Feb
******************************

GraphSim TK: GPU-Accelerated Fast Fingerprint Similarity Searches
================================================================================

**GraphSim TK** now supports CUDA for even faster fingerprint searching,
allowing users to perform molecular similarity calculations up to
*200x faster* than the in-memory fast fingerprint mode (see the NxN
similarity score calculations graph below).

CUDA mode involves preloading all fingerprints into GPU memory
prior to performing similarity calculations. Searches are limited by GPU
memory availability and will fall back to the memory-mapped CPU mode if the
entire set of fingerprints cannot be preloaded into the GPU memory.
Despite this limitation, this represents the fastest way to perform
similarity searches.

The most effective way to use CUDA fingerprint searches is to perform
multiple searches with a pre-loaded database on a dedicated GPU machine.
If CUDA mode is selected but a GPU is not present on the system,
the search will simply fall back to memory-mapped mode.

The new :oe:meth:`OEGraphSim::OEFastFPDatabase::GetHistogram` method
performs an NxN search of a database and returns a histogram of scores.
This is valuable information for understanding the diversity of a
database without consuming excess disk space.
Using :oe:meth:`OEGraphSim::OEFastFPDatabase::GetHistogram` in CUDA
mode will afford *2.5 billion* searches per second
(benchmarked on an AWS P3 instance - NVIDIA Tesla V100) compared with
*12.5 million* searches per second when using memory-mapped mode on the CPU.

.. list-table::
   :widths: 300 450

   * - Performance of an NxN similarity score calculation
     - Performance of a fingerprint search (load time not included)

   * - .. image:: images/2018-Feb/Performance-ScoreHistogram-CPU-GPU.*
          :width: 300 pt

       * *16M 4096-bit long tree fingerprints = 8GB data*
       * *CPU benchmarked on m4.10xlarge AWS instance (single threaded)*
       * *GPU benchmarked on p3.8xlarge AWS instance*
       * *In-memory timings are extrapolated from shorter runs*

     - .. image:: images/2018-Feb/Performance-SimilaritySearch-CPU-GPU.*
          :width: 450 pt

       * *128M 4096-bit long tree fingerprints = 64GB data*
       * *retrieving the 10 most similar molecules*
       * *CPU benchmarked on m4.10xlarge AWS instance (single threaded)*
       * *GPU benchmarked on p3.8xlarge AWS instance*

See the :ref:`oegraphsim_chapter_examples` chapter of the **OEGraphSim TK**
documentation for more information and examples using the new
:ref:`OEFastFPDatabase <OEGraphSim_OEFastFPDatabase>` class.

Grapheme TK : Unpaired Interaction Map
================================================================================

**Grapheme TK** now includes the ability to generate unpaired interaction maps
(see the example below).  An unpaired interaction map provides a
complementary view to the more common active site interaction
depiction. While the interaction map (on the right) depicts interactions
between the ligand and protein, the unpaired map (on the left) illustrates
interactions that could contribute to binding but are not formed in the
complex. Together, these two maps of the protein-ligand binding site
provide insights into protein-ligand interactions and communicate complex 3D
structural results in a directly actionable way.

In the unpaired interaction map, different linker types are used to
mark unpaired acceptor and donor hydrogen bond interactions (see the
figure on the left). Note that since these interactions are unpaired, the
direction of the linkers has no real spatial meaning. Ligand linkers
are directed away from the ligand, while protein linkers are directed
towards the ligand.

The geometric parameters used to perceive unpaired interactions are
customizable to fit user needs.

.. only:: oehtml

   .. list-table:: **Unpaired interaction map (left) and active site depiction (right) generated after hydrogen placement (PDB: 1BR6)**
      :widths: 500 500

      * - .. image:: images/2018-Feb/RenderUnpairedMap-2018-Feb.svg
             :width: 500 pt

        - .. image:: images/2018-Feb/RenderActiveSite-2018-Feb.svg
             :width: 500 pt

.. only:: oepdf

   .. list-table:: **Unpaired interaction map (left) and active site depiction (right) generated after hydrogen placement (PDB: 1BR6)**
      :widths: 400 400

      * - .. image:: images/2018-Feb/RenderUnpairedMap-2018-Feb.pdf
             :width: 220 pt

        - .. image:: images/2018-Feb/RenderActiveSite-2018-Feb.pdf
             :width: 220 pt

Conda Packages for Python
================================================================================

The 2018.Feb release is the first release to fully support Conda packages
for Python toolkits on all supported platforms.  The toolkits are available
as a package named ``openeye-toolkits`` in the ``openeye`` Conda channel on
the default ``conda.anaconda.org`` server.  Versions are available for
Python 3.5 and higher on Windows and Python 3.4 and higher on Linux and macOS.
On Linux and macOS, users can install the toolkits into a Conda Python
environment with ``conda install -c openeye openeye-toolkits``.  On Windows,
Anaconda Navigator is a convenient way to manage Conda packages.

See :ref:`Python Installation <python_installation>` for more information.

General Notices
================================================================================

* All **OpenEye Toolkit** Python code examples now follow
  the `PEP8 <https://www.python.org/dev/peps/pep-0008/>`_  standard.

* The 2018.Feb release fully supports macOS High Sierra 10.13.

* mac OS 10.10 is no longer supported.
