Please check if the PR fulfills these requirements
[x] The commit message follows our guidelines
[x] 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?
Bug fix
What is the current behavior?
The problem only occurs with the following conditions:
2nd preventive with global optimization
PSTs are modeled as approximated integers
The PST is both preventive and curative.
It has a relative range.
For our scenario, we are going to consider that the PST has a relative limit of [-10, 0] and is at tap 5 initially.
It so, its curative limits are wrongly bounded to [-5, 5] because it considers that the tap 5 is fixed and it can only move compare to this value.
What is the new behavior ?
In the same scenario, the previous constraint does not exist anymore so the PST curative limits only depend on the preventive tap which evolves through the MIP.
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? Bug fix
What is the current behavior?
The problem only occurs with the following conditions:
For our scenario, we are going to consider that the PST has a relative limit of [-10, 0] and is at tap 5 initially. It so, its curative limits are wrongly bounded to [-5, 5] because it considers that the tap 5 is fixed and it can only move compare to this value.
What is the new behavior ?
In the same scenario, the previous constraint does not exist anymore so the PST curative limits only depend on the preventive tap which evolves through the MIP.
Does this PR introduce a breaking change or deprecate an API?