[FEA] Break load windows
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- json
- 领域
- backend
调研方向
Read the vehicle breaks documentation and trace how fleet_data.vehicle_breaks is parsed and validated in the cuOpt API. The linked PR #2193 is a proposed example to inspect for context. Determine whether breaks can be constrained by capacity dimensions, then confirm the recommended behavior with an API example or guidance in the issue.
由索引模型根据 Issue 内容生成。
描述
Context
Vehicle breaks in cuOpt currently allow defining:
- Break window (when the break may occur)
- Break duration (how long the break lasts)
- Break location(s) (where the break may occur)
Feature Request
We are using cuOpt to solve vehicle routing problems and have a requirement that vehicle breaks may only occur when the vehicle is empty (i.e. its active load/capacity is 0).
From the current documentation, my understanding is that break feasibility is based on the break's time window and optional locations, but not on the vehicle's current load. As a result, the solver may schedule a break while the vehicle is still carrying cargo.
Would you consider adding support for load-based break constraints? For example, an option to require that a break can only be scheduled when one or more capacity dimensions have a load of zero.
If this is already possible with the current API, or if there is a recommended modeling approach to achieve the same behavior, I would greatly appreciate any guidance.
Pull Request
I added a PR to give an example of how this could be implemented.
https://github.com/NVIDIA/cuopt/pull/2193
An example shape for the API endpoints looks like:
{
"fleet_data": {
"capacities": [[10, 10]],
"vehicle_breaks": [
{
"vehicle_id": 0,
"earliest": 60,
"latest": 120,
"duration": 15,
"locations": [3],
"load_windows": [[0, 0]]
}
]
}
}
Thank you!
- 主要语言
- Cuda
- 星标
- 1.1k
- 派生
- 255
- 平均合并
- 1 天 22 小时
- 30 天内合并 PR
- 102
环境准备
- 没有 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 于 3 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
ci: pr-test-summary job shows red when the GitHub API returns persistent 5xx errors可能已有人在做 @0z5a 于 2 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 82/100
维护者通常 1 天内回复
-
bug mip
难度 4/5 1-2 天 新手友好度 53/100
维护者通常 1 天内回复
-
[BUG] Dataset downloader reports success and replaces data after a failed download可能已有人在做 @0z5a 于 2 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 75/100
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
rubys/roundhouse#1917 ·
-
Pretalx reports older version to be the latest release than what is actually installed and available未关闭
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
stringify escapes leading digits in pseudo-class arguments (:nth-child(1) becomes :nth-child(\31 ))未关闭
难度 2/5 1-3 小时 新手友好度 83/100
维护者通常 1 天内回复