From c668e95345b18799b889b0e3e55a79616c1cfd21 Mon Sep 17 00:00:00 2001
From: Gabriel Studer <gabriel.studer@unibas.ch>
Date: Fri, 31 May 2024 18:23:59 +0200
Subject: [PATCH] ligand scoring: docu update
---
modules/mol/alg/pymod/ligand_scoring_base.py | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/modules/mol/alg/pymod/ligand_scoring_base.py b/modules/mol/alg/pymod/ligand_scoring_base.py
index 8d3882c0e..17a1ad00a 100644
--- a/modules/mol/alg/pymod/ligand_scoring_base.py
+++ b/modules/mol/alg/pymod/ligand_scoring_base.py
@@ -20,10 +20,11 @@ class LigandScorer:
At the moment, two such classes are available:
- * :class:`LDDTPLIScorer` that assesses the conservation of protein-ligand
+ * :class:`ost.mol.alg.ligand_scoring_lddtpli.LDDTPLIScorer`
+ that assesses the conservation of protein-ligand
contacts
- * :class:`SCRMSDScorer` that computes a binding-site superposed,
- symmetry-corrected RMSD.
+ * :class:`ost.mol.alg.ligand_scoring_scrmsd.SCRMSDScorer`
+ that computes a binding-site superposed, symmetry-corrected RMSD.
By default, only exact matches between target and model ligands are
considered. This is a problem when the target only contains a subset
--
GitLab