[codex] Clarify TQQQ fixed-mode diagnostics#15
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
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.
Summary
atr_exit_linefor legacy/diagnostic compatibility.MA200 Exitand MA20 slope instead of the old ATRExitvalue.Root cause
The fixed dual-drive strategy was already using MA200 plus MA20 slope for stateful risk-on/off decisions, but the dashboard still displayed the legacy ATR-derived
exit_line, making the live report look like the old ATR strategy.Validation
uv run --with pytest --with pandas --with numpy python -m pytest tests/test_strategy_plans.py tests/test_entrypoints.py -quv run --with ruff ruff check src/us_equity_strategies/strategies/tqqq_growth_income.py tests/test_strategy_plans.py