Gwénaël Rault

A constraint on the number of vehicle could be useful in two cases. - The infinite fleet mechanism, with some vehicles prototypes, the idea is to limit their number but...

That's a feature we are interested in, as well as https://github.com/VROOM-Project/vroom/issues/227

My interpretation for this is quite variable depending of the case. But mainly yes, in case of delivery in urban context it could be assimilate to searching a parking place....

The setup time is fully dependent on the sequence of activities, this information is not available for a single activity without its context.

Model it as distinct activity sounds good but seems costly and hard to maintain, because in a general case you could have as much setup activity as regular activity. And...

The setup time should be independent from transport time or waiting time, because there is in the case of a reloading time some handling costs. The current implementation answer this...

It seems that just changing the cost associated to the UnassignedJobs lead the solution faster to good solutions. This value depending on the data. So It's all good for me

We've appied it on some real cases and it gives well formed route, well constrained and with a good quality of results ;) Did you have a look at it...

Thanks - Since the solution is updated after every ruin, yes the setup time will be consider for A2. By the way the cost induced by the setup time is...

Hi @grantm009 It is indeed designed to answer this kind of purpose, which was exactly my starting point ;) This feature is not include in the main version.