OEDocking TK 4.0.0.2¶
March 2021
Default value of
Target Mask
has been changed toOEDesignUnitComponents::TargetComplexNoSolvent
, to reflect best practices for receptor generation.Target Mask
in OEMakeReceptorOptions now provides added flexibility to create user defined mask.An issue causing OEPosit to occasionally ignore the
Posit Methods
has been fixed.Constraints (both protein constraints and custom constraints) are now properly serialized in the OEReceptor in a .OEDU file.
All of the protein constraints, custom constraints, and extra molecules are now properly transferred in the OEReceptor and the OEDesignUnit, when OEB format receptors are used.
OEDocking TK 4.0.0¶
Fall 2020
New features¶
A new class, OEMakeReceptorOptions, has been added that provides choices for making an OEReceptor inside an OEDesignUnit.
The
OEMakeReceptor
function now takes an OEDesignUnit and an OEMakeReceptorOptions, and adds an OEReceptor inside the OEDesignUnit object.A new class, OEDockOptions, has been introduced that provides choices for
OEDockMethod
andOESearchResolution
in the OEDock class.The OEDock class constructor now has an overload that takes an OEDockOptions argument.
The following methods now have an overload that accepts as an argument an OEDesignUnit containing an OEReceptor:
A new method,
OESinglePoseResult::GetDesignUnit
, has been added added that returns the resulting design unit containing the pose ligand and the target.A new class, OEPoseOptimizerOptions, has been added that provides choices for force fields and flexibility in performing pose optimization with OEPoseOptimizer.
The OEPoseOptimizer class constructor now has an overload that takes an OEPoseOptimizerOptions.
The
OEPoseOptimizer::Optimize
method now takes an OEDesignUnit to optimize.Flexible POSIT with
OEPosit::Dock
now uses the OEFF14SBParsley for pose optimization.A new method,
OEPosit::RankDesignUnits
, has been added that ranks an OEDesignUnit containing an OEReceptor for posing with multiple receptors.With the introduction of the new OEReceptor class and the corresponding behavior of the OEDocking TK, several previously existing APIs have been deprecated. The following table shows the deprecated APIs and their replacements:
Deprecated API
New API
OEDocking::OEBoxBase
OEDocking::OEBox
OEDocking::OECustomConstraints
OEDocking::OEFeature
OEDocking::OEProteinConstraint
OEDocking::OESphereBase
OEDocking::OEAlignReceptors
OEDocking::OEIsReceptor
OEDocking::OEReceptorClear
OEDocking::OEReceptorClearCustomConstraints
OEDocking::OEReceptorClearProteinConstraints
OEDocking::OEReceptorGetBoundLigand
OEDocking::OEReceptorGetCustomConstraints
OEDocking::OEReceptorGetInnerContourLevel
OEDocking::OEReceptorGetOuterContourLevel
OEDocking::OEReceptorHasBoundLigand
OEDocking::OEReceptorHasCustomConstraints
OEDocking::OEReceptorHasInnerContourLevel
OEDocking::OEReceptorHasNegativeImageGrid
OEDocking::OEReceptorHasOuterContourLevel
OEDocking::OEReceptorHasProteinConstraints
OEDocking::OEReceptorSetCustomConstraints
OEDocking::OEReceptorSetInnerContourLevel
OEDocking::OEReceptorSetOuterContourLevel
OEDocking::OEReceptorAddCachedScore
OEDocking::OEReceptorSetCachedScore
OEDocking::OEReadReceptorFile
OEDocking::OEReadReceptorToBytes
OEDocking::OEWriteReceptorFile
OEDocking::OEWriteReceptorToBytes
OEDocking::OEBoxArea
OEDocking::OEBoxExtend
OEDocking::OEBoxTranslate
OEDocking::OEBoxVolume
OEDocking::OEBoxXDim
OEDocking::OEBoxYDim
OEDocking::OEBoxZDim
OEDocking::OEBoxXMid
OEDocking::OEBoxYMid
OEDocking::OEBoxZMid
OEDocking::OEInBox
OEDocking::OESetupBox
OEDocking::OESetupBoxCenterAndExtents
OEDocking::OEInSphere
OEDocking::OESphereArea
OEDocking::OESphereVolume
With the introduction of the new APIs, several obsolete functionalities have been deprecated without any suitable replacements. These functionalities were added in the early development days of OEDocking TK and are no longer deemed useful:
OEDocking::OEAlignReceptorFunction
OEDocking::OEReceptorAddExtraMols
OEDocking::OEReceptorClearBoundLigand
OEDocking::OEReceptorClearExtraMols
OEDocking::OEReceptorHasExtraMols