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

Missing XY Coordinates when using onestep.py in the CPYDAR #52

Open
OESNES opened this issue Jul 9, 2024 · 1 comment
Open

Missing XY Coordinates when using onestep.py in the CPYDAR #52

OESNES opened this issue Jul 9, 2024 · 1 comment

Comments

@OESNES
Copy link

OESNES commented Jul 9, 2024

Describe the bug
I have a working version of the onestep.py script located in the CPYDAR folder that is correctly converting the supplied 13-node and 123-node models. But when I tried to make a test of a model I built in OpenDSS and exported into CIM within OpenDSS, the resulting DSS model is missing multiple xPosition and yPosition points.

I reviewed the code to the extent I can understand the entire flow and only found one spot within the CIMImporter.java file where a _busxy.dss file is created. This is on

lines 2469 fXY = fRoot + "_busxy.dss";
lines 2502 fXY = fRoot + "_busxy.dss";

  1. What I would like to know is how X and Y coordinates are getting captured, used, and then saved into the DSS file?
  2. Is there something I might be missing with input data or something else, that would cause some coordinates to get skipped?
  3. What script (Python or Java)is responsible for all the coordinate data points getting extracted?
  4. And oddly, how was the CUMHub onestep.py able run a successful load flow on the converted model given the lack of connectivity nodes (and also a missing Solve command in the DSS file)?

To Reproduce
There are no errors thrown, just the fact that when I review the sum_ugrid_busxy.dss file there are only 8 nodes as opposed to the 15 nodes in the original.

The original BusXY.csv file used to build the model

Source 200 280
150 200 275
200 200 250
250 200 245
300 165 220
350 170 220
400 175 220
450 200 220
500 225 220
550 230 220
600 200 195
650 200 190
700 175 165
750 200 165
800 225 165

sm_ugrid_busxy.dss
550,230.0,220.0
650,200.0,190.0
300,165.0,220.0
500,225.0,220.0
600,200.0,195.0
700,175.0,165.0
150,200.0,275.0
350,170.0,220.0

Screenshots
SLD of the model
image

Original DSS model with all nodes
image

Converted DSS model with the missing nodes
image

Additional context
The cases.json file I made for this test is

[
    {
     "dssname": "sm_ugrid.dss",
     "root": "sm_ugrid",
     "dss_controls": true,
     "mRID": "16C9D717-9B39-4BCD-86C5-AA64E3411335", 
     "glmvsrc": 66395.28,
     "substation":"subname",
     "region":"region",
     "subregion":"subregion",
     "bases": [
      115000.0,
      12470.0
     ],
     "inpath_dss": "./sm_ugrid/",
     "export_options": " -e=carson",
     "check_branches": [
      {
       "dss_link": "LINE.250450",
       "dss_bus": "250"
      }
     ],
     "path_xml": "./xml/",
     "outpath_dss": "./dss/",
     "outpath_glm": "./glm/",
     "outpath_csv": "./csv/"
    }
   ]

While in the CPYDAR directory I placed an Excel data file along with the various model and input data folders I placed

A B
Excel file version v2.0
Name sm_ugrid
Frequency (Hz) 60
Power Base (MVA) 100

sm_ugrid folder which has the original model in the same fashion as the ieee13x or j1red files

  • sm_ugrid.dss which is the DSS model
  • LoadShape5_Q.csv and LoadShape5_P.csv and BusXY.CSV

xml folder

  • sm_ugrid_uuids.dat which contains the mRID numbers
  • sm_ugrid.xml which contains the master CIM model information

CPYDAR folder

  • sm_ugrid.xlsx which seems to have initial file settings information.
  • NAME is the New Circuit.sm_grid name in the sm_ugrid.dss file
@OESNES
Copy link
Author

OESNES commented Oct 7, 2024

Looking to follow-up on this and see why there are missing coordinates. I am having the same issues with the ieee13x conversion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant