Repository navigation
7/8 All assays in a crossValidate call share the same folds (changes results; decision) - #132
Merged
Merged
Conversation
This was referenced Oct 9, 2026
Merged
…the same folds (changes results) Why (Ellis Patrick's decision): each assay, classifier, selection method and combination was cross-validated on its own random splits, because the splits were drawn from the global random stream that earlier cross-validations had advanced (fold assignments of two assays agreed for 19% of samples, chance for 5 folds). So comparisons between them in performancePlot and samplesMetricMap were not paired by fold and included split-to-split noise. With shared folds the comparisons are paired, and per-assay work could be reused across combinations. What: the first cross-validation of a call keeps its seed and splits, and every later one uses them. With the splits shared, the final models no longer need to be fitted one after another in the main process to keep the random streams reproducible, so they are fitted in the worker pool, from the random number state that follows making the splits. Consequence: the first cross-validation of a call gives the same results as before; later ones differ because their folds differ. Tested: every assay, classifier and merge combination has the same fold assignments. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TfsjwkbDbHkX4kJZNe4ER4
ellispatrick
force-pushed
the
review/7-shared-folds
branch
from
October 10, 2026 22:47
acdc0a4 to
21ad9ab
Compare
ellispatrick
force-pushed
the
review/7-shared-folds
branch
from
October 14, 2026 00:20
21ad9ab to
5bfd793
Compare
DarioS
marked this pull request as ready for review
October 28, 2026 02:15
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
Changes results (Ellis Patrick's decision). All assays, classifiers, selection methods and combinations in one
crossValidatecall are evaluated on the same training and test splits.Why
Each assay, classifier and combination used to get its own random splits, drawn from the global random stream that earlier cross-validations had advanced. Two assays' fold assignments agreed for only 19% of samples, which is chance for 5 folds. So comparisons between assays in
performancePlotandsamplesMetricMap, as in the protocol paper, were not paired and included split-to-split noise. With shared splits the comparisons are paired.What changes
?crossValidatedocuments the shared splits.Do results change?
Yes:
Evidence
To reject
Close this pull request. Part 6 alone keeps separate splits, with identical results to before.
🤖 Generated with Claude Code
https://claude.ai/code/session_01TfsjwkbDbHkX4kJZNe4ER4