Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Add simulation and report definitions to the simulation schema

Abierto
  • ¿Algo no está bien?
#899 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@anth-volk ya está trabajando en esto.

Desde el 22/10/2026.

  • #900 de @anth-volk — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
python
Área
backend-api-design, database

Línea de trabajo

Start by reading the Simulation Entrypoint's simulation schema and the Public API table definitions it references. Define the simulations and reports tables with the described foreign keys and legacy ID columns; check the schema or migration entry point to confirm both tables are created empty and can support a repeatable later migration.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

The Simulation Entrypoint's simulation schema needs the definitions that later runs and results attach to:

  • simulation.simulations: what to run, independent of model versions. A simulation is one policy (null for current law) applied to one population, either a household or an economy named by a region code such as state/ca with an optional dataset name (null means the region's default dataset in whichever catalog version a run uses), with an optional dynamic.
  • simulation.reports: which two simulations a report compares (an economy report needs a reform; a household report may have only a baseline), both of the report's own country and kind, with its year and options.

Both reference the Public API's policies, households and dynamics in the same database with foreign keys (composite with the country where the Public API table has one), all ON DELETE RESTRICT. Simulations and reports migrated from the Public API's v1 database keep their v1 IDs in unique legacy_simulation_id and legacy_report_id columns, so a later one-time migration can be run again safely.

Once deployed, both tables exist with no rows; nothing writes them until the stage 2 routes.

Lenguaje dominante
Python
Estrellas
1
Forks
1
Merge medio
1 d 16 h
PR fusionados (30 d)
61

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de PolicyEngine/policyengine-sim-api

Todos los issues de PolicyEngine/policyengine-sim-api

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.