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

[Flow decomposition] #150

Open
OpenSuze opened this issue Jun 3, 2024 · 0 comments
Open

[Flow decomposition] #150

OpenSuze opened this issue Jun 3, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@OpenSuze
Copy link
Contributor

OpenSuze commented Jun 3, 2024

Describe the current behavior

Provided XNECs can be outside main synchronous component or not connected.
If a XNEC is outside main synchronous component, then the sensitivity analysis will be zero, then each decomposed flow will be zero.
If a XNEC is not connected, it will have a NaN DC flow and each decomposed flow will be zero.

Describe the expected behavior

We should warn user that a XNECs is outside main synchronous component or not connected with some logs.
Maybe we should add also two flags in the DecomposedFlow object:

  • isInsideMainSynchrinousComponent
  • isConnected

We can use the branch to get those information.

Describe the steps

No response

Environment

No response

Relevant Log Output

No response

Extra Information

Not urgent

@OpenSuze OpenSuze added bug Something isn't working enhancement New feature or request and removed bug Something isn't working labels Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant