Add iterative palette proof calibration - #67
Open
vycdev wants to merge 29 commits into
Open
Conversation
vycdev
marked this pull request as ready for review
July 25, 2026 10:08
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.
Summary
Why
Kromacut previously had no closed feedback loop between physical palette-proof prints and its simulated colors. This workflow lets users record what actually printed closest to each target and safely use sufficiently strong evidence to improve later auto-paint results without changing filament assignments, hiding-distance calibration, or export colors.
Impact
Users can generate proof sheets, record closest/tied/no-match results, continue testing the same targets, or rotate to new targets. Appearance correction is applied only when training and held-out evidence clear strict quality gates.
Validation
npm test? 367 passingnpm run build? passing (Vite reports the existing large-chunk warning)npm run lint? passinggit diff --check develop...HEAD? passing