Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Segment and cache Stage 12 US simulations

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

I maintainer di solito rispondono entro 1 giorno

@anth-volk ci sta già lavorando.

Dal 30/9/2026.

  • #712 di @anth-volk — aperta

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
api, backend, devops, documentation, testing

Direzione di ricerca

Start by locating the Stage 12 worker coordination path and the existing API v1 runner behavior that defines 20-part execution, then identify the dataset, baseline-cache, deployment-validation, and worker-manifest entry points. Verify the workflow with unit tests for segmentation, caching, coordination, validation, error preservation, and cancellation. Done means independent concurrent baseline and reform execution, 40 segment calls, validated cache artifacts, stable policy errors, consistent failure states, and deployment documentation.

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

Descrizione

Problem

Stage 12 US reports currently execute each baseline and reform simulation as one calculation. They do not have the 20-part execution and precomputed baseline data used by the API v1 runner. The current coordination path also needs to preserve policy-validation details and stop observing the other simulation normally after either baseline or reform fails.

Scope

  • Implement deterministic 20-part US simulation execution within Stage 12 without importing or calling API v1 runner code.
  • Keep baseline and reform execution separate, producing 40 segment function calls for a complete report.
  • Precompute, version, store, validate, and load the Stage 12 dataset and baseline cache artifacts.
  • Include cache identity and validation results in the Stage 12 worker manifest.
  • Observe baseline and reform concurrently.
  • When either simulation fails, cancel the other simulation, preserve its failure details, and persist consistent report and simulation states.
  • Reject malformed policy effective periods with a stable error code and detailed message.
  • Document the deployment, cache, execution, and failure-handling behavior.
  • Add unit tests for segmentation, cache construction and loading, deployment validation, coordination, error preservation, and cancellation.

Acceptance criteria

  • A successful segmented US report produces two simulation calls and 40 segment calls.
  • Baseline and reform calculations run concurrently and remain separate through aggregation.
  • A failed simulation causes the report to fail and the other simulation to be cancelled or recorded as incomplete.
  • Validation errors retain their structured error code and useful summary at the simulation and report levels.
  • Worker deployment rejects missing, mismatched, or inaccessible cache artifacts.
  • The implementation remains independent of API v1 runner modules.
  • Unit tests and deployment documentation cover the complete workflow.
Lingua principale
Python
Stelle
1
Fork
1
Merge medio
1g 7h
PR unite (30g)
23

Preparare l'ambiente

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 PolicyEngine/policyengine-sim-api

Tutte le issue di PolicyEngine/policyengine-sim-api

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.