From 3513f271816618fc453738581889e677861473de Mon Sep 17 00:00:00 2001 From: Federico Igne Date: Wed, 18 May 2022 15:34:23 +0100 Subject: fix: allow bounds update even when the bounds gap is empty This is needed for now because PAGOdA's upper bound is not *always complete*. In this way we can fix its mistake by using RSAComb (or any other lower bound approximation service). --- src/main/java/uk/ac/ox/cs/pagoda/query/QueryRecord.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/main/java/uk/ac/ox/cs/pagoda/query/QueryRecord.java b/src/main/java/uk/ac/ox/cs/pagoda/query/QueryRecord.java index 1fb4ed7..be19734 100644 --- a/src/main/java/uk/ac/ox/cs/pagoda/query/QueryRecord.java +++ b/src/main/java/uk/ac/ox/cs/pagoda/query/QueryRecord.java @@ -117,9 +117,9 @@ public class QueryRecord extends Disposable { boolean update = false; for(AnswerTuple tuple; answerTuples.isValid(); answerTuples.moveNext()) { tuple = answerTuples.getTuple(); - if(!soundAnswerTuples.contains(tuple) && (gapAnswerTuples == null || gapAnswerTuples.contains(tuple))) { + if(!soundAnswerTuples.contains(tuple)) { soundAnswerTuples.add(tuple); - if(gapAnswerTuples != null) + if(gapAnswerTuples != null && gapAnswerTuples.contains(tuple)) gapAnswerTuples.remove(tuple); update = true; } -- cgit v1.2.3