Repository navigation
Conversation
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
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.
When reviewing motion footage, DVIDIA can now follow a manually selected image region and show observed image speed alongside causal forecasts at 100, 250 and 500 ms. The new
dvidia-motioncommand analyzes permitted local footage, validates receipts, runs authored fixtures and serves a branded read-only replay. It uses CPU sparse feature tracking and actual integer video timestamps; it trains no model and downloads no weights.Tracking losses withhold forecasts. The replay uses the latest observation at or before the playhead and expires stale predictions. Source, seed, clock, protocol, camera display geometry and causal rows are checked before replay; benchmark scores are recomputed against hash-bound evaluator references. Future references never enter tracking.
The first measured batch at commit
ade2b541d8ca4a785bbd1effdfd33eb2a306f150preserves conditional errors, answer coverage, abstentions, timing scope and failure tails. All 720 frames were attempted. Processing took 1.454 seconds for 24 seconds of authored video on one ARM64 machine; this is offline throughput, not live latency. Occlusion and low texture lose tracking. Direction reversal reaches approximately 90 pixels worst forecast error at 500 ms. Speeds and errors remain image-plane quantities; physical motion, independent real-scene accuracy, live robot interaction and calibrated uncertainty remain unqualified.Intake and replay reject nonzero rotation, nonidentity display matrices and explicit non-square pixel aspect ratios. A bounded metadata probe has a 64 KiB output cap and a 10-second owned-process watchdog. Older identity receipts remain readable; consistently rehashed rotated media cannot bypass the replay guard.
Includes source installation instructions, a full v0.2 plan and updated execution map. Original motion code/fixtures use MIT; existing upstream Apache notices remain packaged. The published v0.1 tag and Hugging Face review demo are unchanged.
Validation:
Measured evidence: benchmark. Source installation: motion alpha.