S14.1: Compare strategies side by side

Open
  • Is something wrong?
#174 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
backend-api-design, data-visualization, full-stack

Research direction

Read the roadmap entry for S14.1 and its dependency, S13.3 (#172), then inspect the committed project structure for existing run APIs and web pages. The issue calls for an API and page comparing two to four runs, including a metrics table, overlaid equity curves, a spec diff, and monthly-return statistics. Done means all acceptance criteria are implemented; no file paths or tests are named in the issue.

Written by the indexing model from the issue text.

Description

area: web priority: P0 story

Roadmap story S14.1 · Project · Roadmap

Parent epic: E14 #106

Dependencies: S13.3 #172

Priority: P0 · Size: M · Sprint: 12 · Milestone: M9 · Area: web · Depends on: S13.3 · Reqs: FR-R1 · Status: Backlog

Story: As a researcher, I want to compare strategies directly, so that I can see which idea is actually better.

Acceptance criteria

  • Select two to four runs to see a metrics table, overlaid equity curves, and a spec diff.
  • The difference in monthly returns is shown with its mean, t-statistic, and correlation.

Tasks

  • Write the comparison API
  • Build the comparison page

Progress evidence (2026-11-08): No implementation or completion evidence for these acceptance criteria is present in the audited commit. This remains planned work.

Audited against committed main at 0c32c57. Local, staged, and untracked work is excluded.

Dominant language
Python
Stars
0
Forks
0
Avg merge
3h 33m
Merged PRs (30d)
50

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nfiasco/Quant-Time-Machine

All issues in nfiasco/Quant-Time-Machine

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.