Skip to content

docs(metrics): clarify close-to-close directional accuracy - #60

Merged
KageRyo merged 1 commit into
mainfrom
feature/52-directional-accuracy
Sep 16, 2026
Merged

KageRyo merged 1 commit into
mainfrom
feature/52-directional-accuracy

Conversation

@KageRyo

@KageRyo KageRyo commented Sep 16, 2026

Copy link
Copy Markdown
Owner

Closes #52

  • keep the public directional_accuracy field for compatibility
  • label CLI output as close-to-close directional accuracy
  • document the signal-close versus next-close definition and gap-open limitation
  • add a regression test where directional correctness and trade PnL differ

@sonarqubecloud

Copy link
Copy Markdown

@KageRyo
KageRyo merged commit a3742ff into main Sep 16, 2026
9 checks passed
@KageRyo
KageRyo deleted the feature/52-directional-accuracy branch September 16, 2026 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs(metrics): clarify directional accuracy semantics in backtest results

1 participant