RouteLocks is for establish starting points in order, or to assign points to route to visit optimized?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start with the routeLocks entry point and the VRP setup described in the issue; trace how locked points are interpreted during route construction and optimization. Reproduce the route shown in the issue, then establish whether the behavior is expected or needs correction, with the requested optimized route as the completion criterion.
Written by the indexing model from the issue text.
Description
I am working with routeLocks to assign some points to a certain route and to visit them along with others remain, in a optimized way. But instead it just makes the VRP to push them in first place to visit starting the route without analyze if those points are optimized.
As you can see in the image red route start from point depot, goes to point 1, next it goes back to point 2, and goes to point 3 which is close to point 1. With routeLock I expected to assign those points to certain route and visit them optimized. As you can see the route is not optimized, it goes far away, and then comes close to depot, then goes far away close to the first point and come back to depot, the traveling time is the highest possible.
Expected result..
Or this..
Any help?
Did I understand wrong?
Is Node-or-tools capable to solve this and assign points to a route and visit them in a optimized way?
- Dominant language
- C++
- Stars
- 155
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mapbox/node-or-tools
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
mapbox/node-or-tools#84 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
mapbox/node-or-tools#82 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
mapbox/node-or-tools#81 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
mapbox/node-or-tools#80 ·
-
Windows build Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
mapbox/node-or-tools#77 · 5 reactions ·
All issues in mapbox/node-or-tools
Similar issues
-
bug build
Difficulty 1/5 Under an hour Newbie friendliness 91/100
facebookincubator/velox#19194 ·
-
JIT-compiled number -> Decimal conversion silently overflows instead of raising DECIMAL_OVERFLOW Openfuzz
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ClickHouse/ClickHouse#122114 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
module/agent platform/macos type/bug/regression
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
enhancement PyCDE
Difficulty 2/5 1-3 hours Newbie friendliness 78/100