Expose configurable solver knobs
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 155
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
There are a few knobs we can tune and constraints we can set, especially here:
We should aim for common use-cases and make the API surface easy to use. At the same time it should be possible to tune your search based on the user's domain knowledge.
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 reading the linked RoutingSearchParameters and RoutingModelParameters definitions in src/constraint_solver/routing_parameters.proto. Identify the common solver knobs and constraints to expose, then define an easy-to-use API whose completed surface supports domain-specific search tuning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, node.js
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100