dioph/elegant

Electrical Grid Analysis Tool

elegant's Issues

Allow delta loads

editLineType raises NotImplementedError

We should either implement a way to edit line models or remove the option altogether.

scipy requirement

We are using scipy solely because of its gmean function; should we implement our own geometric mean and drop the requirement?

Values are not updated outside mouse release events

After adding loads/generations or updating parameters, update_values should be called.

Let user chooses the report output format through interface

The following paths should be added on interface

• Generate report >> .pdf
• Generate report >> .dat

We could store shutil.which("latexmk") in an environment variable stored in elegant.core, and figure out a way to make this persistent over the sessions. What do you think? Any better idea?

Program crashes when submitting empty strings

Currently, the interface module does not check if any QLineEdit text is an empty string.
When submitting empty strings, it raises a ValueError: could not convert string to float: '' and crashes.

Segmentation fault on software termination

Steps to reproduce

• Run python3 elegant-runner.py
• Close Elegant

Log prompts Segmentation fault (core dumped)

No need to have active power loss on transformers

The Ploss column of the Trafo table will always be zero.

Current session is erased when canceling a Load

Steps to reproduce:

• Run elegant
• Draw any system (or open a saved one)
• Click the "Load Session" tab and close the dialog

The intended behavior is to keep whatever was already in the canvas.

Fix text size in power flow annotations

Power flow annotations are currently automatically checked for colisions, which can make them too tiny.

Resizing window makes sidebar menu width behave erratically

The width of the left sidebar should remain constant throughout every possible menu layout -- as it indeed does when the window is on its initial size. However, resizing the window makes every layout have a different width, which can create problems to the user experience in the Editor.

scipy requirement

We are using scipy solely because of its gmean function; should we implement our own geometric mean and drop the requirement?