Define cross-language evaluation semantics - #364
Merged
Conversation
Contributor
|
uriahf
marked this pull request as ready for review
August 21, 2026 10:04
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
1 participant
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.
Goal
Establish the Stage 0 semantic vocabulary for the cross-language parity work before adding characterization tests.
Contract
Defines shared meanings for:
model × population)It also records the key compatibility rule that existing
reference_groupterminology is a generic implementation/grouping concept and is not the target domain abstraction. Stage 1 must characterize what it represents in each current code path rather than assuming it means either model or population.Scope
Documentation only. No statistical calculations, public APIs, input formats, return values, plotting behavior, labels, colors, reference lines, package metadata, generated documentation, or
rtichoke_vizare changed.Paired PR
R: uriahf/rtichoke#162
Both PRs carry the same semantic contract so Stage 1 tests can use one vocabulary in both repositories.