From 6eb3a087d4cac74cc276ccc96c649a1ad3903da9 Mon Sep 17 00:00:00 2001
From: Daniel Friesel <daniel.friesel@uos.de>
Date: Mon, 19 Apr 2021 10:12:32 +0200
Subject: drift: Fix end_ts candidate/drift calculation

---
 lib/drift.py | 1 +
 1 file changed, 1 insertion(+)

(limited to 'lib/drift.py')

diff --git a/lib/drift.py b/lib/drift.py
index f2dd889..7d73b58 100644
--- a/lib/drift.py
+++ b/lib/drift.py
@@ -53,6 +53,7 @@ def compensate(data, timestamps, event_timestamps, offline_index=None):
                     candidate_weights[i][changepoint] = 1
 
     for i, expected_start_ts in enumerate(expected_transition_start_timestamps):
+        expected_end_ts = event_timestamps[2 * i + 1]
 
         # TODO ist expected_start_ts wirklich eine gute Referenz? Wenn vor einer Transition ein UART-Dump
         # liegt, dürfte expected_end_ts besser sein, dann muss allerdings bei der compensation wieder auf
-- 
cgit v1.2.3