Repository navigation
feat(strategy-v2): integrate registered factors into research - #289
Merged
Merged
Conversation
3 tasks done
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
2 participants
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 factor-research API exposed a unified catalog, but the research engine only executed legacy momentum/volatility aliases and TA-Lib factors. Selecting canonical built-in factors such as RSI therefore produced empty research output.
This change routes registered factors through the shared factor service with their catalog parameters, computes each score from data available at the research timestamp, and adds return skewness and kurtosis to the registry. It keeps legacy aliases compatible, resolves canonical fundamental requirements, and avoids constant-rank correlation warnings.
Validation:
This is the maintained replacement for #283.