The following new getter methods have been added to OEShapeDatabaseOptions for retrieving the number of starts for the relevant method:
OEShapeDatabaseOptions::GetNumStarts has also been overloaded for each alternative start option.
There is no need to alter existing scripts if the OEFastROCSOrientation::AsIs alternative starts feature is not being used since the default argument results in the correct execution path for all other use cases.
Generally, the constructor is not used in most scripts as the OEShapeDatabaseScore object is constructed internally when calling OEShapeDatabase::GetScores or OEShapeDatabase::GetSortedScores. Therefore, most users will not be affected by this change.
The default value for the additional argument satisfies all other use cases, so no action is required.
See OEShapeDatabaseScore::Constructors for more information.
Previously, GPU memory limits were being reached for routine searches when using OEFastROCSOrientation::InertialAtHeavyAtoms, causing searches to default to OEFastROCSOrientation::Inertial. The improved alternative starts algorithm handles any number of starts without reaching GPU memory limits.
Performance will be affected by using large numbers of alternative starts.
OEShapeDatabaseOptions::SetMaxOverlays now sets the number of overlay results to return per conformer. Previously, this was broken and was restricting the number of overlays to 1 per conformer regardless of its setting. OEShapeDatabaseOptions::SetMaxOverlays is now fixed and works correctly with OEShapeDatabaseOptions::SetMaxConfs, OEShapeDatabaseOptions::SetNumInertialStarts and alternative starts for both OEShapeDatabase::GetScores and OEShapeDatabase::GetSortedScores.
Tversky calculations no longer overestimate the score of caged systems or conformer pairs where one conformer is much larger than the other.
A tutorials page has been created that walks through features of FastROCS TK and gives detailed examples. The first tutorial gives step-by-step instructions on how to use alternative starts.
If you have a specific feature that you would like in a tutorial, please contact support at firstname.lastname@example.org with the subject header FastROCS TK Tutorial Request.