-
Notifications
You must be signed in to change notification settings - Fork 36
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
improve cyme reader logging, power factor handling, doc strings #400
base: master
Are you sure you want to change the base?
Conversation
not sure why this is here, just printing cable sectionID
- cannot parse a list of objects though it was taking a obj_list as input; - it would only parse the first value in the list; - now it takes in a string instead of list of string - also improved notes/documentation
came across some transformers in CYME that have actual voltages set to something different than nominal. CYME has base voltages in TRANSFORMER SETTINGS (e.g. `primarybasevoltage`) and actual voltages in TRANSFORMER (e.g. `kvllprim`). The latter are currently set to Winding.nominal_voltage.
add same test to opendss reader, which passes
@@ -44,6 +45,28 @@ def test_cyme_reader(): | |||
# TODO: Log properly | |||
print(">Cyme model {model} parsed.\n".format(model=model)) | |||
|
|||
if model == "ieee_13node": | |||
""" | |||
test load base voltage values |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tarekelgindy this is the load nominal voltage issue that I mentioned in the cyme reader. perhaps we should add tests for comparing opendss voltage values between a IEEE13 model read from cyme and a IEEE13 model read from opendss?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that this test is failing because of a bug in cyme reader I believe.
not sure why this is here, just printing cable sectionID
- cannot parse a list of objects though it was taking a obj_list as input; - it would only parse the first value in the list; - now it takes in a string instead of list of string - also improved notes/documentation
add same test to opendss reader, which passes
Bug fixes
Improvements
parser_helper
was taking in a list of object names but only parsing the first item in the list (by design), so I made that list argument a single argument