From e243f9028917e4df695e9ee4128c477816232c92 Mon Sep 17 00:00:00 2001
From: Xavier Robin <xavier.robin@unibas.ch>
Date: Mon, 13 Mar 2023 17:59:05 +0100
Subject: [PATCH] doc: SCHWED-5481 fix Sphinx links
---
modules/mol/alg/pymod/ligand_scoring.py | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/modules/mol/alg/pymod/ligand_scoring.py b/modules/mol/alg/pymod/ligand_scoring.py
index 5883b029f..85190fe11 100644
--- a/modules/mol/alg/pymod/ligand_scoring.py
+++ b/modules/mol/alg/pymod/ligand_scoring.py
@@ -21,7 +21,7 @@ class LigandScorer:
At the moment, two scores are available:
* lDDT-PLI, that looks at the conservation of protein-ligand contacts
- with :func:`lDDT <ost.mol.alg.LocalDistDiffTest>`.
+ with :class:`lDDT <ost.mol.alg.lddt.lDDTScorer>`.
* Binding-site superposed, symmetry-corrected RMSD that assesses the
accuracy of the ligand pose.
@@ -30,11 +30,11 @@ class LigandScorer:
of model and target ligands, as described in (Manuscript in preparation).
Results are available as matrices (`(lddt_pli|rmsd)_matrix`), where every
- target-model score is reported in a matrix, or as `(lddt_pli|rmsd)` where
+ target-model score is reported in a matrix; as `(lddt_pli|rmsd)` where
a model-target assignment has been determined, starting from the "best"
possible mapping and using each target and model ligand in a single
- assignment, and the results are reported in a dictionary. In addition,
- (`(lddt_pli|rmsd)_details`) methods are available with additional details
+ assignment, and the results are reported in a dictionary; and as
+ (`(lddt_pli|rmsd)_details`) methods, which report additional details
about different aspects of the scoring such as chain mapping.
The class generally assumes that the
--
GitLab