Repository navigation
Fix allocation normalization breaking repeated validation and cross-repo execution - #17
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.
The normalizer added EWMA, risk-free, tracking-error and tail-risk parameters to every policy. Execution validates the persisted allocation plan again, so valid equal/inverse-vol/cost-aware policies immediately failed with an irrelevant-parameter error. The new Windows and Linux research integration gate reproduced this for all four advanced-study candidates.
Emit optional fields only for applicable estimators/modes, while retaining explicit rejection of irrelevant input fields. Preserve the EWMA default when building non-EWMA covariance.
Validation: 132 tests passed, 1 skipped; coverage 80.96%; Ruff check/format passed. New regressions cover round-trip validation for all ten modes, custom mode-specific parameters, rejection of irrelevant fields, and execution parity between raw and normalized policies. Cross-repo verification is tracked in quant-workspace #14.