Exceptions on voltage thresholds are not precise enough
rolnico opened this issue · comments
Describe the current behavior
Some error messages on voltage thresholds are not precise enough to enable the user to identify what the problem is.
For example the following message does not indicate which network element raised the exception:
com.google.common.util.concurrent.UncheckedExecutionException: java.lang.IllegalArgumentException: Inconsistent low (0.0) and high (0.0) voltage thresholds
at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2085)
at com.google.common.cache.LocalCache.get(LocalCache.java:4011)
at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4919)
at com.powsybl.afs.ext.base.ScriptCache.get(ScriptCache.java:61)
at com.powsybl.afs.ext.base.LocalNetworkCacheService.getNetwork(LocalNetworkCacheService.java:116)
at com.powsybl.afs.ext.base.ImportedCase.getNetwork(ImportedCase.java:81)
(...)
Describe the expected behavior
The error message should at least identify the type of network element and give its ID
Describe the steps
add an element with both low and high voltage thresholds set as 0.0
Environment
No response
Relevant Log Output
No response
Extra Information
No response