From edf36e2121c99d348f898fad3973f3f90ee60058 Mon Sep 17 00:00:00 2001
From: Gabriel Studer <gabriel.studer@unibas.ch>
Date: Thu, 17 Aug 2017 21:22:32 +0200
Subject: [PATCH] make unit test work

in one case of the unit test there is an interaction with distance
9.9996 that gets included in QMEAN but not in ProMod3. This fix makes
sure it also gets included in ProMod3 and therefore results in the
exact same score. It does not introduce a conceptual difference,
it's only a manifestation of my lazyness...
---
 scoring/src/cbeta_score.cc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scoring/src/cbeta_score.cc b/scoring/src/cbeta_score.cc
index 26a3db10..a5c2a5b3 100644
--- a/scoring/src/cbeta_score.cc
+++ b/scoring/src/cbeta_score.cc
@@ -262,8 +262,8 @@ void CBetaScorer::Score(const loop::BackboneList& bb_list,
 
   const Real inv_bin_size = bins_ / cutoff_;
   // let's reduce the cutoff a bit -> hack to ensure bin always within range
-  const Real squared_cutoff = cutoff_*cutoff_ - 0.001;
-  const Real cutoff = cutoff_ - 0.001;
+  const Real squared_cutoff = cutoff_*cutoff_ - 0.0001;
+  const Real cutoff = cutoff_ - 0.0001;
 
   // let's precalculate the idx ranges we have to neglect
   int min_idx_chain = idx_handler_->GetChainStartIdx(chain_idx);
-- 
GitLab