S13.2: Re-run and verify

Open
  • Is something wrong?
#171 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

Research direction

Read the parent epic #105, dependency #170, and the roadmap in doc/roadmap.md to understand the experiment and pinned-version requirements. The issue names no endpoint, comparator, or UI files, so first locate the saved-experiment flow and its tests. Done means a re-run uses the pinned data and engine versions and reports either an identical result or a diff covering spec, data, code versions, and results.

Written by the indexing model from the issue text.

Description

area: engine priority: P0 story

Roadmap story S13.2 · Project · Roadmap

Parent epic: E13 #105

Dependencies: S13.1 #170

Priority: P0 · Size: S · Sprint: 10 · Milestone: M8 · Area: engine · Depends on: S13.1 · Reqs: FR-X2, NFR-2 · Status: Backlog

Story: As a reviewer, I want to re-run any saved experiment and confirm it matches, so that I can trust results I didn't produce.

Acceptance criteria

  • "Re-run" replays the run with its pinned data version and engine version.
  • The result is either "identical" or a diff of the spec, data, and code versions and of the results.

Tasks

  • Write the re-run endpoint
  • Write the result comparator
  • Add the button and diff view

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.