[TRNSPRTPCE-769] PCE may select the wrong path instead of selecting the one selected by GNPy Created: 25/Oct/23  Updated: 10/Jan/24  Resolved: 17/Nov/23

Status: Verified
Project: transportpce
Component/s: PCE
Affects Version/s: Potassium
Fix Version/s: PotassiumSR1, Calcium

Type: Bug Priority: Medium
Reporter: Gilles Thouenon Assignee: Gilles Thouenon
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

In the case where PCE calculates a path with "include nodes" type constraints, and that GNPy does not validate the selected path, if GNPy finds another suitable path, it proposes to PCE the new path under the form of new "include nodes" constraints, which this time contain the full path to select.
However, in PostAlgoPathValidator, PCE verifies that the calculated path includes the nodes regardless of the order of the nodes. Also, if there are multiple paths passing through the same nodes, but in a different order, PCE may select the wrong path.


Generated at Wed Feb 07 20:44:02 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.