Ilya Builuk

Hi, thanks for reporting! So far sounds like an issue in init solution logic related to reload functionality. Anyway, I'll check it.

I think I found the reason of the problem: when initial solution is constructed from user provided, inserted jobs are not analyzed whether they should be promoted to locked as...

I've added a fix in the master branch, will be available in the next release

Actually, there is no really issue (well, maybe some missing validation rule), just a bit misuse of a tag: try to specify different values for each reload and use the...

Hi, thanks for feedback! Interesting use case, not sure that I got it precisely. One of the features, I'm considering to add the next, might help: optional start location. My...

Hi! No, there is not such constraint. You can try to use `activity order` feature, but it doesn't provide `Job B must be done after job A in X minutes`...

It is possible if you use the project as a library. Then you can have write your own extension. However, this would require some understanding how to do it which,...

Hi, capacity constraint is hard constraint, it should not be violated (only if you use relations and added too much jobs). Can you give me an example data?

Hi, thanks for feedback! Yes, some checks are run only if matrices are specified. Also checker itself can have some issues (there is one already: https://github.com/reinterpretcat/vrp/issues/31), but I think the...

yes, that's possible when the logic is used as a library (rust crate). You would need to construct your own instance of VRP using desired constraints (wrapped by `Feature` concept)....