Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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?
Code cleaning
What is the current behavior?
We allow to run a non global opt 2P (where we only reoptimize preventive remedial actions). This requires us to disable many actions (including preventive) for various reasons linking curative optimization to preventive. It also complicates the results structure a lot. And it gives worst results for little performance gain.
What is the new behavior (if this is a feature change)?
We now force global opt 2P, reoptimizing preventive actions and curative PSTs.
Does this PR introduce a breaking change or deprecate an API?
If yes, please check if the following requirements are fulfilled
What changes might users need to make in their application due to this PR? (migration steps)
Users will have to remove the "re-optimize-curative-range-actions" field from parameters.
Other information: