waitingPeriod

[log-konz]

Hey together,

since 2-3 weeks I have the problem that the global parameters "MaxTourEarlinessPeriod" and "MaxStopEarlinessPeriod" no longer work.

These are my settings in the "TourOpt.ini" file:
MaxTourEarlinessPeriod=900
MaxStopEarlinessPeriod=900

However, I still get tours back, some of which require six hours of waiting period / earliness:
{
"$type": "TourPoint."
"id": 16198,
"type: TRANSPORT_POINT,
"result": {
"orderId": 16198,
"arrivalTime": 1533112680,
"startServiceTime": 1533135600,
"endServiceTime": 1533135600,
"departureTime": 1533135600,
"Driving period": 560,
"waiting period": 22920,
"Service period: 0,
"breakPeriodOnRoad": 0,
"breakPeriodAtTourPoint": 0,
"restPeriodOnRoad": 0,
"restPeriodAtTourPoint": 0,
"earliness": 22920,
"Delay: 0,
"startDistance": 23043,
"drivingDistance": 3824
},
"tourFixed": false,
"remainPlanned": false
}

Thank you for your help in advance.

[Bernd Welter]

Hello Daniel,

this is a topic we should discuss 1:1. I'll get back to you via email.

Best regards,
Bernd

[Bernd Welter]

Hello Daniel,

as the explanation for the effect might be of public interest I forward it to the forum, too:

• The two values in the config are not hard constraints. They are used to push a solution towards a specific structure without having waiting periods that exceed a given threshold.
• Furthermore these values apply during construction phase (construction step) within Savings and MergeSavings algorithm. In fact Insertion has it's own threshold values.
• Therefore the proper result of the construction step is subject to be overridden during steps such as Improvement or TourReduction.

Probably not what you wanted to hear but for the moment: state of the art.
Sorry for delivering these news,

Bernd

PS:
We will not implement this behaviour in xTour 2.