Replies: 2 comments 3 replies
-
|
@N-Wouda We are experimenting with using PyVRP to replace our production or-tools. PyVRP seems to be not good at finding feasible solutions for lots of edges with a really big number. |
Beta Was this translation helpful? Give feedback.
-
please tell me if you need the solution in a different format, or a different solution.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
PyVRP solves instances for many different vehicle routing variants very well, often reaching best-known solutions, or approaching those closely. At the same time, PyVRP is still fairly young: it has not been tested on a lot of instances outside of academia. As a consequence, we do not really know how PyVRP behaves when faced with real-world instances that might not be as nice to solve as the academic benchmarks we often use for comparison.
So, this discussion is an open call to anyone using PyVRP to provide instances that PyVRP currently struggles to solve. This can either be because it's hard to find a feasible solution, because of poor convergence, or any other aspect that makes the problem difficult for PyVRP. We are interested in learning more from such instances, and use that knowledge to improve PyVRP's robustness and performance going forward.
Important
It is much easier for us if you provide an instance by serialising a
ProblemDataobject using Python's builtinpicklemodule. Please then also specify the version of PyVRP you use.It would be immensely helpful if you have a contrasting solver that does perform well on the instance. A good solution from such an alternative solver will help us quickly understand:
Note
If you want to share your instances but would rather not do so publicly in this discussion thread, feel free to send them via email.
Beta Was this translation helpful? Give feedback.
All reactions