PR #154 changes how per-phase measurements are reported to enable better interop with devices that only report certain phases (e.g. only phases B and C).
In the current usecases phase-specific values are communicated as an array with all reported phases. In the case where a device does not report all phases, the array would contain less than three values and matching array entries to values is complicated.
The new approach introduced in #154 replaces the array of phases with a map[ElectricalConnectionPhaseNameType]float64 which allows receivers to always determine which value corresponds to which phase even when the map contains less than 3 values.
This approach should be extended beyond the ma-mpc and ma-mgcp usecases to all usecases that work with phase-specific limits or measurements.
The known implemented use cases that would require this update are:
PR #154 changes how per-phase measurements are reported to enable better interop with devices that only report certain phases (e.g. only phases B and C).
In the current usecases phase-specific values are communicated as an array with all reported phases. In the case where a device does not report all phases, the array would contain less than three values and matching array entries to values is complicated.
The new approach introduced in #154 replaces the array of phases with a map[ElectricalConnectionPhaseNameType]float64 which allows receivers to always determine which value corresponds to which phase even when the map contains less than 3 values.
This approach should be extended beyond the ma-mpc and ma-mgcp usecases to all usecases that work with phase-specific limits or measurements.
The known implemented use cases that would require this update are: