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

UCTE importer should allow non active equivalent branches/lines between 2 XNODES #2697

Open
AnkurArohi opened this issue Sep 12, 2023 · 3 comments
Assignees

Comments

@AnkurArohi
Copy link

AnkurArohi commented Sep 12, 2023

Describe the current behavior

Currently UCTE importer can only build net model when there is no line between 2 XNODES.

Currently there is an exception and model is not built
Exception is that there is a line between 2 XNODES

Describe the expected behavior

Actually it is possible to have an equivalent modelling between 2 XNodes.
Considering the documentation there is no where explicitly mentioned that such a model is not considered valid.
Moreover the net should atleast be built with a warning.
It is obvious that the network is then not N-1 conform as there is an equivalent model which will not be directly included in N-1 calculatins but still specially in case one would like to merge this model withthe actual downstream network model below, the equivalent will be replaced a line after merging this network with downstream network so it should function and must be allowed.

Describe the motivation

After merge the equivalent line would be replaced by the actual downstream network. HEnce the whole network can actually be built.

Extra Information

If the documentation is followed the 21st character in the Line section has a status field which is set based on integers, if the integer is 9 this means that the model is equivalent and moreover it is out of operation

image

I am attaching the relevant part of the UCT file, please include this part in the already previously used UCT file for testing purpose in powsybl. This has the explicit part of lines which lead to the exception which should ideally not occur.

Since this file is not supported i added a txt suffix, please remove that

uct_dummy.UCT.txt

@AnkurArohi
Copy link
Author

FYI @annetill

@annetill
Copy link
Member

I can change the exception by a log and ignore the line.

@AnkurArohi
Copy link
Author

yes I understand that, that will help as a first step but ignoring this line is not constructive because this should be modelled as dangling line to both XNODES so that when this is merged with the DSO file, this will correctly be converted to a line

pseudo code

if (char 21 is 1 or char 21 is 9){
-> eqv. line
convert eqv_line to dangling line
}

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

No branches or pull requests

3 participants