Page 1 of 1

Meaning of VIOLATIONS in xRoute1

Posted: Tue Jun 14, 2022 4:30 pm
by Bernd Welter
Here's a little description of the violations handling in xRoute 1.

Let's start with a simple route through Karlsruhe. Important to know: the original track uses a few (10) segments with a height restriction of 2.60m (PTV_TruckAttributes) - a tunnel under the Südtangente. The used car in the initial scenario has a height of 2.50m and is therefore allowed to use these segments.
Total costs: 2'772
Total costs: 2'772
Violations forbiden, vehicle height not critical.
Violations forbiden, vehicle height not critical.
Now in the next loop I increased the vehicle's height to 2.70m which exceeds the height restriction of the tunnel. Violations are still forbidden: the vehicle has to take a detour.
Dertour with total costs of 5'732  ( +2'960 compared to the direct route)
Dertour with total costs of 5'732 ( +2'960 compared to the direct route)
From now on I enable violations and I play with the costs of violated segments:
Price per violates segments==0: The violated segments are reporteds in the output's violations list. The total costs of the route are again 2'772.
Price per violates segments==0: The violated segments are reporteds in the output's violations list. The total costs of the route are again 2'772.
Now by setting the costs for violations to 290/"violated segment" the route takes the direct (violated) path with costs=5'672  (which is 2'722 + 10x290) which is still cheaper than the 5'732 alternative with the detour.
Now by setting the costs for violations to 290/"violated segment" the route takes the direct (violated) path with costs=5'672 (which is 2'722 + 10x290) which is still cheaper than the 5'732 alternative with the detour.
Now I simulated this based on compareably small values for "costs per violated segment". Usually this value is set to somewhere around "50'000". This is recommended to see violated segments as a last ressort if you can't reach waypoints without them.

Bernd