cuopt_mcp: add VRP/routing support
维护者通常 1 天内回复
@Iroy30 已经在做这个了。
开始于 2026年9月18日。
评估
这个 Issue 还没有评估数据。
描述
cuopt_mcp (#1916) currently exposes LP and MILP solving only (cuopt_solve_lp/cuopt_solve_milp), backed by cuopt.grpc.client.grpc_client.Client. Routing/VRP isn't wired in.
Why this is bigger than adding another tool
LP/MILP submission is file-based — problem_path works because MPS/LP are standard formats Read() parses directly. VRP has no file-format equivalent: a routing problem is built programmatically via DataModel calls (fleet size, cost matrix or coordinates, demand, capacity, time windows, breaks, etc.). A cuopt_solve_vrp tool needs a structured JSON input schema covering that construction surface instead of a problem_path string — real design work, not just plumbing.
What's already reusable
RoutingClient (merged into the same cuopt.grpc.client.grpc_client extension module as Client) has a near-identical shape — submit/status/wait/cancel/result/delete — so the tool-calling pattern this PR established (async submit, _guard-shaped errors, generated settings catalogue) should carry over cleanly once the input schema exists.
Gaps to close
- Design a JSON Schema for VRP problem construction (fleet, tasks, time windows, matrices, etc.) to replace
problem_path. cpp/src/grpc/codegen/field_registry.yamlonly haspdlp_settings/mip_settings— no routing settings section, socuopt_list_settings-style generated discovery doesn't cover routing yet. Extending codegen to routing settings (or hand-writing a schema, which the existing settings catalogue deliberately avoids) is its own piece of work.- New tools:
cuopt_solve_vrp, plus routing-appropriatecuopt_resultshaping (route sequences/vehicle assignments look nothing like an LP variable vector).
Scoped as a follow-up to #1916, not part of it.
- 主要语言
- Cuda
- 星标
- 1.1k
- 派生
- 255
- 平均合并
- 1 天 11 小时
- 30 天内合并 PR
- 123
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
NVIDIA/cuopt 的其他 Issue
-
[BUG] Constraint validation reports CSR offset count as the number of rows可能已有人在做 @0z5a 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
ci: pr-test-summary job shows red when the GitHub API returns persistent 5xx errors可能已有人在做 @0z5a 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 82/100
维护者通常 1 天内回复
-
[BUG] Dataset downloader reports success and replaces data after a failed download可能已有人在做 @0z5a 于 1 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 75/100
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
维护者通常 1 天内回复