Skip to content

Derive shock parameter registry dynamically from PDL #14

@Hackatro

Description

@Hackatro

The mapping between shockable scenario parameters and their onset/end timing
fields is manually maintained in 5 places: pdl_loader.py, scenario.py,
environment.py, main.py, and model.py. Adding a new shock parameter requires
touching all 5 files in lockstep.

The goal of this issue is to create a single source of truth for the shock
parameter registry so that adding or removing a shockable parameter requires
a change in one place only.

Metadata

Metadata

Assignees

Labels

simulation logicFor everything related to the internal simulation logic

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions