From ddf9d096e8326c51ce8df1142eadffc15f3a20dc Mon Sep 17 00:00:00 2001 From: Babissimo Date: Thu, 27 Aug 2026 13:06:40 +0100 Subject: [PATCH] chore: bump retina-tracker for the frame dt and gating fix (86cb9bq7p) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit An out-of-order frame made dt negative, which made F P Fᵀ + Q non-positive-definite. The association gate tested only that S was invertible, so such a track kept gating and its Mahalanobis distances came out negative, which wins a minimisation outright: the corrupted track took detections from every healthy track it could reach, with no exception, no log and no counter, and ended up reporting the wrong aircraft under the original track ID. This repo is where that bites. blah2_bridge's duplicate guard admitted an older frame, and FRAME_WORKERS drain a single queue with no per-node keying, so backwards timestamps reach a node's tracker under ordinary operation rather than as an edge case. The bump carries six intervening commits besides the fix. Five are tooling and formatting (ruff configuration, the vulture dead-code gate, running both through pre-commit) and one adds events.jsonl rotation, which this repo never reaches since it supplies its own InMemoryEventWriter. The fix is the only behavioural change that lands: across the range track.py sees import reordering plus one `if/return` pair collapsed to `return expr`, and config.py gains an additive `output` section with no existing default altered. offworldlabs/retina-tracker#24 Co-Authored-By: Claude Opus 5 --- libs/retina-tracker | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libs/retina-tracker b/libs/retina-tracker index 04ec70b8..79db48cd 160000 --- a/libs/retina-tracker +++ b/libs/retina-tracker @@ -1 +1 @@ -Subproject commit 04ec70b8dd0fd5ee24f62cdace0690ad10f54712 +Subproject commit 79db48cdce11e9cb82ee222285b7a62a3f3321c5