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

Add configurable scaling before ACOPF solving #62

Merged
merged 19 commits into from
Apr 16, 2024

Conversation

p-arvy
Copy link
Member

@p-arvy p-arvy commented Apr 1, 2024

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

Does this PR already have an issue describing the problem?

What kind of change does this PR introduce?

A scaling is added before ACOPF solving.

What is the current behavior?

No scaling is specified. So default scaling of the non-linear solver is applied before ACOPF solving.

What is the new behavior (if this is a feature change)?
A scaling is applied, with configurable values.

Does this PR introduce a breaking change or deprecate an API?

  • Yes
  • No

If yes, please check if the following requirements are fulfilled

  • The Breaking Change or Deprecated label has been added
  • The migration steps are described in the following section

What changes might users need to make in their application due to this PR? (migration steps)

Other information:

p-arvy added 6 commits April 1, 2024 12:30
Signed-off-by: parvy <pierre.arvy@artelys.com>
Signed-off-by: parvy <pierre.arvy@artelys.com>
Signed-off-by: parvy <pierre.arvy@artelys.com>
Signed-off-by: parvy <pierre.arvy@artelys.com>
Signed-off-by: parvy <pierre.arvy@artelys.com>
Signed-off-by: parvy <pierre.arvy@artelys.com>
@p-arvy p-arvy requested review from klorel and So-Fras April 1, 2024 10:33
@p-arvy p-arvy self-assigned this Apr 1, 2024
p-arvy added 5 commits April 1, 2024 12:46
Signed-off-by: parvy <pierre.arvy@artelys.com>
Signed-off-by: parvy <pierre.arvy@artelys.com>
Signed-off-by: parvy <pierre.arvy@artelys.com>
Signed-off-by: parvy <pierre.arvy@artelys.com>
Signed-off-by: parvy <pierre.arvy@artelys.com>
p-arvy added 4 commits April 3, 2024 18:22
Signed-off-by: parvy <pierre.arvy@artelys.com>
Signed-off-by: parvy <pierre.arvy@artelys.com>
Signed-off-by: parvy <pierre.arvy@artelys.com>
Signed-off-by: parvy <pierre.arvy@artelys.com>
Copy link
Member

@So-Fras So-Fras left a comment

Choose a reason for hiding this comment

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

Most of the review comments are typos.
The main question for me is about the test resource files that seem to vary with the optimization run. Can we avoid it?

p-arvy added 4 commits April 5, 2024 12:36
Signed-off-by: parvy <pierre.arvy@artelys.com>
Signed-off-by: parvy <pierre.arvy@artelys.com>
Signed-off-by: parvy <pierre.arvy@artelys.com>
Signed-off-by: parvy <pierre.arvy@artelys.com>
Copy link

sonarcloud bot commented Apr 5, 2024

Copy link
Member

@So-Fras So-Fras left a comment

Choose a reason for hiding this comment

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

Thanks for your work! Regarding the test resources that are dependent on date, elapsed time, local directory, I agree that this could be dealt with in another PR.

@So-Fras So-Fras merged commit 6acab12 into main Apr 16, 2024
6 checks passed
@So-Fras So-Fras deleted the scaling_before_ACOPF_solving branch April 16, 2024 11:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants