.. oe:namespace:: OEProton


.. meta::
   :keywords: OEAmberFF94Charges, AmberFF94Charges, ChargeEngine


.. _OEProton_OEAmberFF94Charges:

.. oe:class:: OEAmberFF94Charges

   .. oe:api::


      class OEAmberFF94Charges : public OEChargeEngineBase

   Charge engine input to :oe:func:`OEAssignCharges<OEProton::OEAssignCharges>`
   to assign Amber force field 94 atomic partial charges to standard amino acids.

   The input molecule must have explicit hydrogens and consist of only standard
   Amber amino acids. Residues must be perceived or repairs permitted. The
   amino acid name may be altered to match the Amber naming scheme, such as
   ``HIP`` for a protonated histidine.
   Currently OpenEye supports the following Amber amino acids:
   ``ACE``, ``ALA``, ``ARG``, ``ASH``, ``ASN``, ``ASP``,
   ``CIM``, ``CIP``, ``CYM``, ``CYS``, ``CYX``,
   ``GLH``, ``GLN``, ``GLU``, ``GLY``,
   ``HID``, ``HIE``, ``HIP``, ``HIS``,
   ``HOH``, ``ILE``, ``LEU``, ``LYN``, ``LYS``,
   ``MET``, ``NHE``, ``NME``, ``PHE``, ``PRO``,
   ``SER``, ``THR``, ``TRP``, ``TYR``, ``VAL``.
   Amber charges are graph-based and do not
   require 3D coordinates.

   .. seealso:
      :ref:`chapter_molchargetheory` for an description of Amber charges

   The following methods are publicly inherited from :ref:`OEChargeEngineBase <OEProton_OEChargeEngineBase>`:

   ======================================================================================= ======================================================================================= =======================================================================================
   :oe:meth:`operator!=<OEProton::OEChargeEngineBase::operator!=>`                         :oe:meth:`GetName<OEProton::OEChargeEngineBase::GetName>`                               :oe:meth:`SetRepairRequestedHint<OEProton::OEChargeEngineBase::SetRepairRequestedHint>`
   :oe:meth:`operator==<OEProton::OEChargeEngineBase::operator==>`                         :oe:meth:`GetRepairRequestedHint<OEProton::OEChargeEngineBase::GetRepairRequestedHint>` :oe:meth:`TransferCharge<OEProton::OEChargeEngineBase::TransferCharge>`
   :oe:meth:`CheckCharges<OEProton::OEChargeEngineBase::CheckCharges>`                     :oe:meth:`GetRequirements<OEProton::OEChargeEngineBase::GetRequirements>`
   :oe:meth:`CreateCopy<OEProton::OEChargeEngineBase::CreateCopy>`                         :oe:meth:`IsValid<OEProton::OEChargeEngineBase::IsValid>`
   :oe:meth:`GetExpectValidMol<OEProton::OEChargeEngineBase::GetExpectValidMol>`           :oe:meth:`SetExpectValidMol<OEProton::OEChargeEngineBase::SetExpectValidMol>`
   ======================================================================================= ======================================================================================= =======================================================================================

   .. oe:method:: Constructors

      .. oe:language:: c++ java csharp

         .. oe:api::

            OEAmberFF94Charges()

      .. oe:language:: python

         .. oe:api:: python

            OEAmberFF94Charges() -> OEAmberFF94Charges

      Constructor. There are no options for this charge engine.
