refactor(cosmo_val): tighten the mixin modules (behavior-preserving cleanup)#208
Merged
cailmdaley merged 1 commit intoJun 20, 2026
Merged
Conversation
…eserving) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
A cleanup pass over the freshly-split
cosmo_val/package — dead code, duplication, and verbose constructs tightened across all seven modules. −62 lines net, no functionality change. Each module's diff was checked by an independent reviewer that reverted anything not provably behavior-preserving, and the whole thing is gated on the value-drift suite staying green.Representative changes:
fig, _ = plt.subplots()→plt.subplots()where the handle was unused)..append()loops → list comprehensions;if/elseassignment → ternary;yaml.load(f.read())→ stream.noise_bias_methodprinted "analytical" while the check uses "analytic").What it deliberately did not touch
Public method names and signatures (every call site is unchanged), and the numerical internals of the diagnostics the value-drift suite does not pin (rho/tau, leakage, 2PCF, aperture-mass) — those got only unambiguously-safe edits.
Verification
ruff check src/sp_validationclean. The value-drift suite (test_cosmo_val.py,test_b_modes.py) stays green in the fresh sandbox — every scientific pin holds.Stacked on #207. Draft for review.
— Claude on behalf of Cail