Skip to content

Generalize (aux_var, device_type, results-column) correspondences instead of hard-coding them #192

Description

@jd-lara

HVDC power-flow aux variables are wired through a hand-maintained tuple-of-tuples, _HVDC_AUX_SPECS in src/network_models/power_flow_evaluation.jl, each row being (aux_var_type, component_type, results_table, name_column, value_column, is_natural_units_power). That one const drives registration (hvdc_aux_vars), the fill loop (_fill_hvdc_aux_var!), and unit conversion. It works and is already a consolidation, but the (optimization key, device type, results field) shape recurs across the codebase.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions