Repository navigation
docs: WO68 — lineage recovery verified by reproduction - #390
Merged
Merged
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.
Summary
run-081-khm-latn-recovery completed (attempt 2 of 3; the first was canceled externally): held-out 5% split, 895 rows — greedy EM 58.21% / CER 28.13%, beam4 EM 58.44% / CER 27.49%. Against khm-latn-1.0's 27.42 this is reproduction within noise: the secryst/data-khmer-translit corpus is confirmed as the khm-latn training lineage and the provenance pin is verified by reproduction. Best checkpoint on the training bucket.
Consequence recorded: reproduction confirms the corpus ceiling — CER < 15 requires data expansion, making the owner's licensing decision (SEAlang / full Chuon Nath IPA or a blessed corpus-release license) the B7 blocker.