[FEA] Break load windows

Abierto
  • ¿Algo no está bien?
#2,239 0 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
json
Área
backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

feature request

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!

Lenguaje dominante
Cuda
Estrellas
1.1k
Forks
249
Merge medio
1 d 15 h
PR fusionados (30 d)
124

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de NVIDIA/cuopt

Todos los issues de NVIDIA/cuopt

Issues similares

Más issues de Backend & API Design

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.