While looking up #946 I came across another problem when using input steps in solving mode. Take for example this simplified version of our example_1 file:
{
"vehicles": [
{
"id": 1,
"start": [
2.35044,
48.71764
],
"end": [
2.35044,
48.71764
],
"steps": [
{
"type": "job",
"id": 1
}
],
"max_travel_time": 1
}
],
"jobs": [
{
"id": 1,
"location": [
1.98935,
48.701
]
}
]
}
The max_travel_time parameter is not accounted for when trying to set the initial solution with the vehicle.steps array. In a release mode, this produces a solution breaking the max travel time constraint. In debug mode, this crashes upon formatting the solution:
vroom: ./utils/helpers.h:540: vroom::Solution vroom::utils::format_solution(const vroom::Input&, const RawSolution&): Assertion `v.ok_for_travel_time(eval_sum.duration)' failed.
Aborted (core dumped)
While looking up #946 I came across another problem when using input steps in solving mode. Take for example this simplified version of our example_1 file:
{ "vehicles": [ { "id": 1, "start": [ 2.35044, 48.71764 ], "end": [ 2.35044, 48.71764 ], "steps": [ { "type": "job", "id": 1 } ], "max_travel_time": 1 } ], "jobs": [ { "id": 1, "location": [ 1.98935, 48.701 ] } ] }The
max_travel_timeparameter is not accounted for when trying to set the initial solution with thevehicle.stepsarray. In a release mode, this produces a solution breaking the max travel time constraint. In debug mode, this crashes upon formatting the solution: