Please check if the PR fulfills these requirements
[x] 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?
No.
What kind of change does this PR introduce?
Algorithm enhancement
What is the current behavior?
If the 2nd preventive RAO is run without GlobalOptimization, we may exclude some rangeActions from the 2nd preventive, meaning we will not re-optimize them. In this case, to ensure we don't exceed the RaUsageLimits in preventive, we decrement these limits with the excluded range actions.
But currently, we decrement these limits by considering all the RangeActions excluded from the 2nd preventive.
What is the new behavior (if this is a feature change)?
We only consider the Range Actions that were actually activated during the 1st preventive.
Does this PR introduce a breaking change or deprecate an API?
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem? No.
What kind of change does this PR introduce? Algorithm enhancement
What is the current behavior?
If the 2nd preventive RAO is run without GlobalOptimization, we may exclude some rangeActions from the 2nd preventive, meaning we will not re-optimize them. In this case, to ensure we don't exceed the RaUsageLimits in preventive, we decrement these limits with the excluded range actions.
But currently, we decrement these limits by considering all the RangeActions excluded from the 2nd preventive.
What is the new behavior (if this is a feature change)?
We only consider the Range Actions that were actually activated during the 1st preventive.
Does this PR introduce a breaking change or deprecate an API?