Optional locations, potentially with penalty
Open
- Dominant language
- C++
- Stars
- 155
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
We should expose an option to configure locations as being optional.
Potentially adding a penalty to the solution if the location is not serviced.
---
Implementation: see `model.AddDisjunction()`
Contributor guide
Research direction
Start by reading the existing binding around model.AddDisjunction() and how routing options are exposed. Clarify the API for marking a location optional and for applying a penalty, then verify that both behaviors are represented in the relevant routing examples or tests; done means optional locations can be skipped and penalties affect the solution as specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, node.js
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100