|
|
1 week ago | |
|---|---|---|
| .. | ||
| README.md | 1 week ago | |
| pins.json | 1 week ago | |
| server.patch | 1 week ago | |
README.md
PTZ17. YOLO evidence for steering after validation timeout
Apply server.patch from the production module directory after checking the baseline SHA-256 in pins.json. The production base is the PR10 field release. The repository carries its field deltas as pinned patches.
Camera 17 (internal ID 6) can use a same-frame YOLO box at confidence ≥0.45 to continue steering an existing target. Normal acquisition, verified zoom, full STOP and alarm processing keep their existing paths. Field logs mark entry, continuation and exit from steering-only control. The installed module is a shared service, but the new behavior applies only to camera 17.
Three offline YOLO observations from the 17:44:55 PTZ17 flight matched. With the assumed frame timing the candidate retained the tracker through the sampled tick 944 ms after the original timeout. Two observations produced non-zero native pan/tilt queue values. Zoom-out occurred at the original sampled tick. The replay uses extracted frames with no verified PTS-to-UTC mapping, so live retention duration remains to be measured.