Cyme conversion lat/lon child node improvements.

[dpinney]

First off, @afisher1, the conversion code you delivered works, was right on schedule, and the code quality is excellent.

One issue: some child nodes are given (0,0) as their x/y coordinates (in the gld lat/lon properties). Image showing this below. How much work would it take to make sure they're placed near their parents?

[jcfuller1]

@dpinney , What if we started by using the parent's (x,y) coordinate, then added a little offset? May have to play with the offset a little to make it look visually appealing, but that would put it in the right ballpark.

[dpinney]

Small random offset from parent would be a perfect solution. It looks like all the things at (0,0) are triplex_node objects, so the fix is probably quick and easy (parent explicitly referenced instead of having to find everything attached to a from-to link).

[afisher1]

Wow. I'm taking a look at this now to see what caused this. I do remember copying parent x/y information to load objects.

[dpinney]

I added the .py code to /omf/omf/cymeToGridlab.py. I'm keeping the .glm output and .mdb stuff off github, but can we keep that cymeToGridlab.py file up to date?

[afisher1]

Ok sounds good to me. What do you expect lat lon information on besides nodes, meters, loads, triplex_meters, and loads? Capacitors? Links?

[dpinney]

Lat Lon info only needed for node-like objects and not for link-like ones.

The configuration objects can all be put at random lat/Lon's clustered around (0,0).

[afisher1]

Fixes made. @dpinney can you check how the out put looks now?

[dpinney]

Beautiful.