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

Export PTI data #752

Closed
jbarberia opened this issue Jan 12, 2021 · 7 comments
Closed

Export PTI data #752

jbarberia opened this issue Jan 12, 2021 · 7 comments

Comments

@jbarberia
Copy link
Contributor

Is there an export_pti function to write the networks as export_matpower?

How could it be implemented in PowerModels?

@ccoffrin
Copy link
Member

Hi @jbarberia, at the moment this is not available but it is a good suggestion.

The export_matpower function should provide a good template for how an export_pti could be implemented.

@jbarberia
Copy link
Contributor Author

@ccoffrin, I just saw the export_matpower function, I'm going to try to implement it.

Some questions:

  • Should I check the file extension? export_matpower doesnt have it (see here). You can do something like export_matpower("filename_without_extension", data) and its works.

  • Would it be better to add functions in psse.jl like _pm2psse_generator!(pm_data, pti_data) (opposite of this) or not?

  • What to do with three winding transformers? export it as three two-windings transformers and the star-bus or recreate the three-winding transformer again?

@ccoffrin
Copy link
Member

Sounds good @jbarberia!

  • checking the file extension is a good idea. You probably want to allow both .RAW and .raw. I personally prefer the use of lower case version in this package
  • This is mostly a matter of style, so I am open to defining new functions or not (similar to export_matpower). If you are not going call a function in multiple locations, there is limited utility to adding the function definitions.
  • The inverse problem can be challenging, so I would skip this in the first version and clearly document the limitations of function. In particular the limited set of PSSE features when one can expect it to be idempotent.

As you work along make sure to have a look at the Matpower export tests here,

@testset "test idempotent matpower export" begin

We will need similar tests for export_pti and we will have to make some choices on what level of idempotent we will want to support (note you can use import_all=true to import all of unsupported data fields from a raw file).

@jbarberia
Copy link
Contributor Author

@ccoffrin, Tell me what you think about doing something like this?

If you agree I can continue with the rest.

@ccoffrin
Copy link
Member

@jbarberia I put some initial comments in the code file that you linked, can you see them?

As a meta comment I also saw a number of edge cases that will fail when data is missing. I also recommend that you try the following work flow to catch some of those, "Load a Matpower case, export as PTI".

@jbarberia
Copy link
Contributor Author

@ccoffrin I saw your comments, I will follow them.

I'm going to extend the tests to detect these borderline cases.

Thanks for seeing it!

@ccoffrin
Copy link
Member

closed by #753

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

2 participants