Not giving the best (shortest and fastest) route
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 155
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
It is not taking the best (shortest and fastest) route. The image shows the points to visit ordered as the VRP result.
i use node-osrm to get the cost table using.
As you can see, it ordered to visit A > C > B > D
I Draw these points to osrm route and give this as not the fastest one.
The fastest one was ordering as A > B > C > D , just by some little difference, but i expect it to be the optimized order
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.
Research direction
Start by reproducing the VRP result using the node-osrm cost table and the points shown in the issue. Compare the returned A > C > B > D ordering with the claimed faster A > B > C > D route, then determine whether the discrepancy is in the cost table or the VRP result. Done means the cause of the ordering difference is identified and the expected optimized order is reproducible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100