diff options
| author | Daniel Friesel <daniel.friesel@uos.de> | 2021-04-19 10:12:32 +0200 |
|---|---|---|
| committer | Daniel Friesel <daniel.friesel@uos.de> | 2021-04-19 10:12:32 +0200 |
| commit | 6eb3a087d4cac74cc276ccc96c649a1ad3903da9 (patch) | |
| tree | 6561818be35aedfdd5acf764c7753b7dfbcff56d /lib/drift.py | |
| parent | 43d32703f5ec3c4541895de345884ae82a2df220 (diff) | |
drift: Fix end_ts candidate/drift calculation
Diffstat (limited to 'lib/drift.py')
| -rw-r--r-- | lib/drift.py | 1 |
1 files changed, 1 insertions, 0 deletions
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 |