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

Fix doc for sensitivity thresholds #2511

Merged
merged 4 commits into from
Mar 28, 2023
Merged

Fix doc for sensitivity thresholds #2511

merged 4 commits into from
Mar 28, 2023

Conversation

obrix
Copy link
Member

@obrix obrix commented Mar 21, 2023

Fix doc for sensitivity thresholds

Please check if the PR fulfills these requirements (please use '[x]' to check the checkboxes, or submit the PR and then click the checkboxes)

  • 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 ? If so, link to this issue using '#XXX' and skip the rest

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change or deprecate an API? If yes, check the following:

  • The Breaking Change or Deprecated label has been added
  • The migration guide has been updated in the github wiki (What changes might users need to make in their application due to this PR?)

Other information:

(if any of the questions/checkboxes don't apply, please delete them entirely)

Signed-off-by: Bertrand Rix <bertrand.rix@artelys.com>
@obrix obrix requested a review from annetill March 21, 2023 13:49
@@ -94,7 +94,8 @@ public SensitivityAnalysisParameters setVoltageVoltageSensitivityValueThreshold(

/**
* VoltageVoltageSensitivityValueThreshold is the threshold under which sensitivity values having
* variable type BUS_TARGET_VOLTAGE and function type BUS_VOLTAGE will be filtered from the analysis results.
* variable type BUS_TARGET_VOLTAGE
Copy link
Member

Choose a reason for hiding this comment

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

This is the invert?

Copy link
Member

Choose a reason for hiding this comment

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

No no, no mistake here indeed for me.

@@ -109,7 +110,7 @@ public SensitivityAnalysisParameters setFlowVoltageSensitivityValueThreshold(dou
/**
* FlowVoltageSensitivityValueThreshold is the threshold under which sensitivity values having
* variable type among INJECTION_REACTIVE_POWER and BUS_TARGET_VOLTAGE
* and function type among BUS_VOLTAGE, BRANCH_REACTIVE_POWER_1/2/3 and BRANCH_CURRENT_1/2/3
Copy link
Member

Choose a reason for hiding this comment

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

No error here too, maybe just some clarifications...

Copy link
Member

Choose a reason for hiding this comment

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

FlowVoltageSensitivityValueThreshold is the threshold under which sensitivity values having variable type among INJECTION_REACTIVE_POWER and function type among BUS_VOLTAGE or variable type among BUS_TARGET_VOLTAGE and function type among BRANCH_REACTIVE_POWER_1/2/3 and BRANCH_CURRENT_1/2/3.
Is it better for you?

Copy link
Member Author

Choose a reason for hiding this comment

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

yes!

@annetill
Copy link
Member

@obrix do you want to clarify something finally?

@obrix
Copy link
Member Author

obrix commented Mar 28, 2023

@geofjamg @annetill The issue was that the couple BUS_TARGET_VOLTAGE/BUS_VOLTAGE is documented as filtered by flowVoltage threshold and voltageVoltageThreshold, where in reality only voltageVoltageThreshold filters those kind of sensitivity values. Do you prefer another way to modify the documentation from the one I used or do you feel it is already explicit enough without modification ?

Signed-off-by: Bertrand Rix <bertrand.rix@artelys.com>
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@annetill annetill merged commit d8c3ba8 into main Mar 28, 2023
@annetill annetill deleted the fix_sensi_threshold_doc branch March 28, 2023 14:40
miovd pushed a commit that referenced this pull request Mar 30, 2023
Signed-off-by: Bertrand Rix <bertrand.rix@artelys.com>
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