-
Notifications
You must be signed in to change notification settings - Fork 12
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
Get network elements properties as data frame #909
Conversation
Signed-off-by: Damien Jeandemange <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jeandemanged maybe we should add an "element_type" column to the datadrame to make it easy to use/associate with other dataframes ?
Signed-off-by: Damien Jeandemange <[email protected]>
Quality Gate passed for 'pypowsybl'Issues Measures |
Hi @geofjamg, |
Quality Gate passed for 'pypowsybl'Issues Measures |
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
Related to #894, in part only, please do not close the issue when merging this PR.
What kind of change does this PR introduce?
Feature
What is the current behavior?
all_attributes=True
in theget_<element_type>
methods, in which case properties are added as columns.What is the new behavior (if this is a feature change)?
Network.get_elements_properties
, returning a data frame of properties "row-oriented" - to be compared with theget_<element_type>
methods returning properties in columns.We can also get properties of the network objects with this method
Does this PR introduce a breaking change or deprecate an API?
Other information: