Group cross-camera motion events into journeys #147
marvin8
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/issue-146-cross-camera-journeys"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Chains per-camera motion events into cross-camera journeys using a time-based join window (
[events] journey_gap_seconds, default 180 s, inclusive, applied per hop). One real-world movement now appears as a single journey card in the day view, with a stitched viewer that plays it across cameras in order.events.py:Snapshotprotocol +Event/Journeytype aliases;group_events_into_journeysgreedy chronological chaining; journey helpersconfig.py: new[events]section (journey_gap_seconds, default 180)/days/{day}/journeys/{anchor_id}(segment highlighting by snapshot id, time bar with segment markers)Query-time derivation only — no schema changes, cangcang untouched.
Spec:
.superpowers/specs/2026-09-05-cross-camera-journeys-design.mdCloses #146
New commits pushed, approval review dismissed automatically according to repository settings
WuMing
Found 1 issue(s). See inline comments below.
@ -32,3 +32,3 @@- repo: https://github.com/rohaquinlop/complexipy-pre-commitrev: v7.0.0rev: v7.0.1config [LOW]
complexipy-pre-commit is pinned to v7.0.1 while pyproject dev dependencies and pylock.toml now use complexipy~=8.0.0. This can make the pre-commit hook run a different complexipy version than the installed dev tooling. Update the hook rev to the matching 8.0.0 tag if available, or keep the complexipy dependency at 7.x for consistency.
.pre-commit-config.yaml line 34
🔴 Not actioned — upstream has no v8 tag.
git ls-remote --tags https://github.com/rohaquinlop/complexipy-pre-commitshows v7.0.1 is the newest tag, so the hook rev cannot be aligned to 8.0.0, and keeping the dependency at 7.x would revert a deliberate dependency bump. Pre-commit hook environments are isolated, so the rev does not need to match the installed dev tooling exactly — CI (which runs complexipy 8 via uv) is green. The rev moves to 8.x as soon as upstream tags it.