Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] KeyError: key "rs" not found in European Low Voltage Test Feeder case #441

Closed
juanjospina opened this issue Sep 7, 2023 · 2 comments · Fixed by #444
Closed

[BUG] KeyError: key "rs" not found in European Low Voltage Test Feeder case #441

juanjospina opened this issue Sep 7, 2023 · 2 comments · Fixed by #444
Assignees
Labels
Category: Data Parsers parser issues Type: Bug Something isn't working

Comments

@juanjospina
Copy link
Contributor

Describe the bug
I am getting a key error when trying to solve the European Low Voltage Test Feeder (I am attaching the file). This test case was solvable in previous PMD versions, but now, for some reason, there is an error when parsing/instantiating the test case data.

Minimum Viable Example

import PowerModelsDistribution as _PMD
import JuMP
import Ipopt
ipopt = JuMP.optimizer_with_attributes(Ipopt.Optimizer, "acceptable_tol"=>1.0e-8, "print_level"=>5, "sb"=>"yes", "print_info_string"=>"yes")
pmd_file = "./lvtestcase_pmd_138kv.dss"
eng1 = _PMD.parse_file(pmd_file)
result1 = _PMD.solve_mc_opf(eng1, _PMD.ACPUPowerModel, ipopt)

Expected behavior
Test case should work fine. In previous PMD versions, this error did not exist. The error seems to be related to the kron_reduction, so maybe something was added to the new versions that require the rs key?

Screenshots
If applicable, add screenshots to help explain your problem.

pmd_error

System Information (please complete the following information):

  • OS: Ubuntu 20.04 LTS
  • Version: 0.14.9 (Main Branch)

Additional context
Attached zip file with IEEE LV test case.
lvtestcase_pmd_138kv.zip

@pseudocubic
Copy link
Collaborator

The issue seems to be that the Linecodes have . characters in their names, which was not expected, and breaks the regex that parses lines. I will have to consider how to address that. In the meantime, you can search/replace those linecode names and it will work again (I confirmed).

@pseudocubic pseudocubic added the Type: Bug Something isn't working label Sep 7, 2023
@pseudocubic pseudocubic self-assigned this Sep 7, 2023
@pseudocubic pseudocubic added the Category: Data Parsers parser issues label Sep 7, 2023
@juanjospina
Copy link
Contributor Author

Great! Thank you @pseudocubic. I was looking for the bug but wasn't able to find. I will modify my testcases to avoid this edge-case error.

pseudocubic added a commit that referenced this issue Sep 19, 2023
This fixes a bug where dss allows for '.' characters in the name of the object, but we were previously splitting on all '.' chars, causing us to drop part of the name in some cases.

Resolves #441
pseudocubic added a commit that referenced this issue Sep 20, 2023
* FIX: dss parsing of object names with '.' char

This fixes a bug where dss allows for '.' characters in the name of the object, but we were previously splitting on all '.' chars, causing us to drop part of the name in some cases.

Resolves #441

* FIX: scaling for pf_bf relaxation tests

the sbase_scale_factor=1.0 was causing SCS solver problems, adjusted to 100.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Data Parsers parser issues Type: Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants