[FEA] Break load windows

Aperta
  • Qualcosa non va?
#2,239 0 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
json
Ambito
backend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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!

Lingua principale
Cuda
Stelle
1.1k
Fork
255
Merge medio
1g 11h
PR unite (30g)
123

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di NVIDIA/cuopt

Tutte le issue di NVIDIA/cuopt

Issue simili

Altre issue su Backend & API Design

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.