S16.5: Save and reopen experiments

Aperta
  • Qualcosa non va?
#189 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
49/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python, supabase
Ambito
database, full-stack

Direzione di ricerca

Start by reading the linked roadmap and the dependency issues S16.2, S16.3, S16.4, and S9.5 to understand the existing builder, results, and data model. Then inspect the backtest builder and results entry points and how the project accesses Supabase. Done means signed-in users can save and reopen experiments, see them on a “My experiments” page, and saved runs retain their spec, data version, and metric summary; signed-out users can still run the canonical example.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: web blocked priority: P1 story

Roadmap story S16.5 · Project · Roadmap

Parent epic: E16 #108

Dependencies: S16.2 #22, S16.3 #187, S16.4 #188, S9.5 #33

Priority: P1 · Size: M · Sprint: 5 · Milestone: M5 · Area: web · Depends on: S16.2, S16.3, S16.4, S9.5 · Reqs: FR-U2, FR-X1 · Status: Backlog

Story: As a researcher, I want to save an experiment and its runs to my account, so that I can come back to them later.

Acceptance criteria

  • From the backtest builder, a signed-in user can save a spec, run it again later, and find it on a "My experiments" page.
  • Each saved run records its spec, data_version, and metric summary, so it can be reproduced (S7.7). The full run registry and history (S13.1, S13.3) build on these tables in CISC 499.
  • Signed-out users can still run the canonical example; saving asks them to sign in.

Tasks

  • Add save and list endpoints, or Supabase queries under row-level security
  • Add "Save" to the builder and results pages
  • Build the "My experiments" 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.

Lingua principale
Python
Stelle
0
Fork
0
Merge medio
3h 33m
PR unite (30g)
50

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nfiasco/Quant-Time-Machine

Tutte le issue di nfiasco/Quant-Time-Machine

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.