Skip to content

Documentation: Improve Power Flow Method Comparisions#1306

Open
Jerry-Jinfeng-Guo wants to merge 1 commit intomainfrom
documentation/improve_pf_documentation_01
Open

Documentation: Improve Power Flow Method Comparisions#1306
Jerry-Jinfeng-Guo wants to merge 1 commit intomainfrom
documentation/improve_pf_documentation_01

Conversation

@Jerry-Jinfeng-Guo
Copy link
Member

Improvements as requested in #1003

  • Methods comparision

Signed-off-by: Jerry Jinfeng Guo <jerry.jinfeng.guo@alliander.com>
@Jerry-Jinfeng-Guo Jerry-Jinfeng-Guo self-assigned this Feb 19, 2026
@Jerry-Jinfeng-Guo Jerry-Jinfeng-Guo added the documentation Improvements or additions to documentation label Feb 19, 2026
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the user manual’s power flow documentation to help users choose an appropriate calculation method (per #1003) by adding a more practical comparison and selection guidance.

Changes:

  • Replaces the power flow algorithm comparison table with columns focused on convergence and typical use cases.
  • Adds a “Choosing the right power flow algorithm” section with selection guidance based on accuracy, speed, and grid characteristics.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +277 to +280
#### Choosing the right power flow algorithm

The choice of algorithm depends on your specific requirements for accuracy, speed, and grid characteristics.

Copy link

Copilot AI Feb 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new #### Choosing the right power flow algorithm subsection now implicitly contains all following content until the next #### heading. This means the general nodal-equation explanation and bus type list end up nested under “Choosing…”, which is likely unintended and makes the document structure confusing. Consider moving this “Choosing…” section further down (e.g., after the general formulation section), or adding an explicit sibling subsection heading (e.g., “Power flow formulation”) before the nodal equations so the scope is clear.

Copilot uses AI. Check for mistakes.
Comment on lines +260 to +265
| Algorithm | Default | Convergence | Typical Use Cases | Algorithm call |
| --------- | ------- | ----------- | ----------------- | -------------- |
| [Newton-Raphson](#newton-raphson-power-flow) | &#10004; | Fast (quadratic) | General purpose, meshed networks, accurate results required | {py:class}`CalculationMethod.newton_raphson <power_grid_model.enum.CalculationMethod.newton_raphson>` |
| [Iterative current](#iterative-current-power-flow) | | Moderate (linear) | Time-series analysis, operational studies, batch calculations | {py:class}`CalculationMethod.iterative_current <power_grid_model.enum.CalculationMethod.iterative_current>` |
| [Linear](#linear-power-flow) | | Single iteration | Constant impedance loads only, quick estimates | {py:class}`CalculationMethod.linear <power_grid_model.enum.CalculationMethod.linear>` |
| [Linear current](#linear-current-power-flow) | | Single iteration | Fast approximations, screening studies, real-time applications | {py:class}`CalculationMethod.linear_current <power_grid_model.enum.CalculationMethod.linear_current>` |
Copy link

Copilot AI Feb 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This table update drops the previous at-a-glance “Speed” and “Accuracy” comparison in favor of “Convergence” and “Typical Use Cases”. Since the surrounding text in this section emphasizes choosing based on speed vs accuracy, consider either keeping speed/accuracy columns (even as qualitative labels), or adjusting the surrounding prose so the selection criteria aligns with what the table presents.

Copilot uses AI. Check for mistakes.
@sonarqubecloud
Copy link

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

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments