feat(engine): R5-B integrate TargetAssociator into target lock (flag-gated, default off)#96
Merged
Merged
Conversation
…y_target_lock Add `use_target_associator: bool = False` to TrackingConfig and wire the pure TargetAssociator (R5-A) into CameraWorker._apply_target_lock behind that flag. Flag OFF (default) is byte-identical to today — existing heuristic path is completely unchanged and all 1006 existing tests pass. Flag ON routes through _build_candidate_cues (motion via IOU to trusted_bbox; identity when the track carries the camera's target_identity_id; pose + appearance always unavailable from this path — conservative) → _associator.decide → _apply_associator_decision (keep/switch via _commit_target_track; ambiguous via _mark_target_ambiguous). Add 14 tests in tests/test_associator_integration.py covering flag-off isolation, flag-on keep/ambiguous/switch, cue availability rules, and config field defaults. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Merged
TCVinNYC
added a commit
that referenced
this pull request
Jun 24, 2026
Second **pre-release** of the 2.2.0 reliability + performance roadmap, for real-hardware validation before the stable 2.2.0. Bumps `__version__` to `2.2.0-rc2`; on merge, tag `v2.2.0-rc2` triggers the pre-release installer build. **New since rc1 (all merged, CI-green + multi-agent-reviewed):** - #92 CPU subservice governor — fewer CPU spikes (phase-stagger) + cadence throttle under load - #93 preview-rate-cap (~20fps) - #90 live GPU-acceleration verdict in the Services panel - #91 OpenVINO auto-install for Intel - #94 scene-adaptive ReID threshold - #95/#96 opt-in fused TargetAssociator (off by default) - #97 batched detect_batch primitive **Validate especially:** CPU usage/spikes with all subservices running (your priority), and \`python -m autoptz --bench\` / the Services-panel verdict on Intel-Mac+AMD. To try the new tracking logic, set \`tracking.use_target_associator = true\`. Follow-ups after your validation: P4 coalescing scheduler, wire the associator ReID/pose cues + flip its default, int8 CPU quant, stable Win/Linux device binding. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Second half of R5: wires the pure
TargetAssociator(#95) into_apply_target_lock, behind a newTrackingConfig.use_target_associatorflag (default OFF). Flag OFF ⇒ the existing heuristic path runs byte-identical (verified: the flag-off test monkeypatchesdecideto raise and confirms it is never called; full suite green). Flag ON ⇒ the fused associator drives keep/switch/ambiguous._track_identitymatched to the bound target identity. pose/appearance are marked unavailable (not computed per-candidate from this path) — the associator excludes missing cues, so it degrades gracefully rather than using wrong values._commit_target_track(so pose/reid/identity recovery state resets exactly as a ReID switch); ambiguous → existing_mark_target_ambiguous. No raw target-id writes; lock ordering preserved (RLock re-entry).The flag lets you validate + tune the weights/margins on real cameras before it becomes default (a follow-up flips the default + removes the old heuristics). Full suite green.
🤖 Generated with Claude Code