You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All validation checks are performed always, independent of the minimum validation level established in the network.
Even if we have set that we accept the network to be in EQUIPMENT validation level, any change will emit logs and report errors related to the verification of steady state attributes.
This can be easily reproduced with the following code:
The logger contents will show the following errors:
ERROR c.p.i.n.ValidationUtil | Load 'l1': p0 is invalid
ERROR c.p.i.n.ValidationUtil | Load 'l1': q0 is invalid
Describe the expected behavior
We expect to obtain errors based in the current minimum accepted validation level.
If we want to keep the validations for levels higher than the minimum accepted (to compute the actual validation level of the network no matter what is the minimum set), at least we should be able to configure that we do not want to emit logs/report errors for the "higher" level checks.
Currently validation checks can be called with a boolean flag that controls the behaviour of error processing: either raise an exception or simply log/report the error. This flag could be changed to an enum with a third option to run the checks silently (no exception, no log, no report), just to update the validation level of the network.
Describe the motivation
This suggestion is made in the context of CGMES import refactoring to split the conversion of networks in two stages:
Building the network structure from equipment (EQ) files that contain only connectivity and electric characteristics of the devices.
Apply information from a steady state hypothesis (SSH) file.
During the first stage we do not want errors to be emitted for missing SSH data.
Extra Information
When we request a validation report, we miss the identification of the related equipment. In the logger, we have messages like Load 'l1': p0 is invalid. In the output from reports we get only the attribute with error, but not the equipment identifier.
Describe the current behavior
All validation checks are performed always, independent of the minimum validation level established in the network.
Even if we have set that we accept the network to be in
EQUIPMENT
validation level, any change will emit logs and report errors related to the verification of steady state attributes.This can be easily reproduced with the following code:
The logger contents will show the following errors:
Describe the expected behavior
We expect to obtain errors based in the current minimum accepted validation level.
If we want to keep the validations for levels higher than the minimum accepted (to compute the actual validation level of the network no matter what is the minimum set), at least we should be able to configure that we do not want to emit logs/report errors for the "higher" level checks.
Currently validation checks can be called with a boolean flag that controls the behaviour of error processing: either raise an exception or simply log/report the error. This flag could be changed to an enum with a third option to run the checks silently (no exception, no log, no report), just to update the validation level of the network.
Describe the motivation
This suggestion is made in the context of CGMES import refactoring to split the conversion of networks in two stages:
During the first stage we do not want errors to be emitted for missing SSH data.
Extra Information
When we request a validation report, we miss the identification of the related equipment. In the logger, we have messages like
Load 'l1': p0 is invalid
. In the output from reports we get only the attribute with error, but not the equipment identifier.To check it, run the following code:
It will produce this output:
The text was updated successfully, but these errors were encountered: