Repository navigation
0.3.0 follow-up: junction case reads the visible corner; Windows contract hashes; landing page - #32
Merged
Merged
Conversation
Six cards from the 0.3.0 changelog, with its figures: fidelity against 0.2.7, JPEG halos and parameters on the noisy tier, faces completed behind their covers and counters cut out, strokes by default, nodes at extrema and --editability, and the Lean theory with its generated checkers. The 0.2.0 cards are in that release's changelog. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016AZWMqqHhRQ337N5EWhNC6
`junction_tri` failed on main after the 0.3.0 merge (junction_err_px 0.48 against 0.2), with the junction exactly where 0.2.7 put it. The check measured how near each large region's path comes to the true junction, which assumed a path is what shows. Since 0.3.0, Quality completes a face beneath the faces painted over it: the Y junction's lower wedge comes back as a rectangle under the other two (`<rect y="62.75" ...>`), the visible corner is where its covers' edges meet, and the rectangle's own edge is 0.48 px from the junction under paint that hides it. The junction is now read from the render. The four source pixels about the true junction are rendered at 64 samples per pixel (the document nested in a window viewBox, so both frames stay the document's own), each artist region is matched to the traced area of its ink that overlaps it most, and the furthest any of them comes to the junction, less the truth's own reach (0.01-0.03 px of blended samples), is the error. Moving the true geometry by 0.05, 0.1, 0.2, 0.3 and 0.5 px reads 0.06, 0.11, 0.20, 0.27-0.31 and 0.43-0.50 on both cases, so the 0.2 px limit means what it said. At the whole-image SCALE the nearest sample inside a 120-degree corner can sit 0.2 px from its apex, which is why the window. junction_tri reads 0.080 on this build and on 0.2.7 alike (the visible corner, 0.09 px off, has not moved); junction_quad 0.035 and 0.014. Quality 42/42 and Fast's 28 recorded cases pass their ratchets. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016AZWMqqHhRQ337N5EWhNC6
…output Taken unchanged from the facade (windows-latest) job's INKVEC_BLESS=add artifact on main at 3d1841c (bindings run 38135195486): 48 lines added, nothing else differs from the committed file. The release's re-bless on Linux had dropped every Windows entry, so the Windows contract ran on everything but the exact bytes until now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016AZWMqqHhRQ337N5EWhNC6
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.
What changed
Three follow-ups to the 0.3.0 merge (#30). The
v0.3.0tag waits on this PR.bench/cases/junctions.py:junction_trireads the junction where it shows.hard cases, Qualitystep, withjunction_trireading 0.48 px against a 0.2 px limit.bindings/contract/cases.json: the x86_64-windows-msvc hashes, recorded by CI (facade job on main, 3d1841c).web/index.html: the landing page's "What's new" is now 0.3.0's.No engine code changes, so output is identical to main.
How verified
cargo test --release --workspace: not re-run, no Rust changes.cargo test --release -p inkvec --test contractpasses with the new hashes.cargo fmt/clippy: no Rust changes.bench/cases.py --ratchet quality42/42 and--ratchet fast(28 recorded) pass.junction_trireads 0.080 px on this build and on 0.2.7 alike.junction_quadreads 0.035 px here and 0.014 px on 0.2.7.docs/THIRD_PARTY.md: no dependency changes.CHANGELOG.md: nothing user-visible beyond the website.studio/scripts/build-web.mjs). The Studio Lite smoke test passes (studio/web/smoke.py, engine 0.3.0, 4 threads, cross-origin isolated).🤖 Generated with Claude Code
https://claude.ai/code/session_016AZWMqqHhRQ337N5EWhNC6
Generated by Claude Code