plans/x265: record PROBE-MORTON-SHIFT-MOTION (head-to-head-2) results#252
Conversation
|
Warning Review limit reached
Next review available in: 52 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_df34bf24-14a9-41bd-9098-d75d558d5d1f) |
The non-tautological head-to-head: rigid translation of an arbitrary (non-φ) sprite IS a Morton dilated-lane address-add, bit-exact, O(1) in sprite size (2-byte delta moves the whole object). Interior residual = 0; only the dis-occlusion L-strip is new content. Comma sub-pel dither aperiodic (X-Trans move). PASS->[H] structural — the MortonShift prediction mode for add-a-mode/RDO parity. Full write-up: lance-graph E-X265-MORTON-SHIFT-1. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01K3RyLEbuNSHxxB3NTTrGki
4d2a59f to
837a460
Compare
2 participants
What
Records the results of
PROBE-MORTON-SHIFT-MOTION— the non-tautologicalhead-to-head-2 — into the plan's probe-queue home. The probe lives in lance-graph
(
crates/helix/examples/morton_shift_motion_probe.rs, PR #745); this repo holds theplan + queue.
Result
PASS → [H] (structural). Rigid translation of an arbitrary (non-φ) sprite IS
a Morton dilated-lane address-add — bit-exact, and the whole 576-pixel object moves
for a 2-byte delta (O(1) in sprite size). Interior residual = 0 (x265's DCT+quant
round-trip never is); only the dis-occlusion L-strip is new content — the tail
shrinks to genuine-new-information, doesn't vanish. Sub-pel rides the comma phase
(
three_gap=3), the Fujifilm X-Trans anti-moiré move that replaces quarter-pelinterpolation. This is the concrete "MortonShift" prediction mode for the
add-a-mode/RDO parity path.
Because the sprite appearance is arbitrary and paid equally on both sides, this
removes head-to-head-1's model-match confound — only the motion representation is
tested.
Full write-up: lance-graph
E-X265-MORTON-SHIFT-1.🤖 Generated with Claude Code
https://claude.ai/code/session_01K3RyLEbuNSHxxB3NTTrGki
Generated by Claude Code