[Feature request]: Consider having a `~/plan/action` component

Aperta
  • Qualcosa non va?
#80 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 15 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
distributed-systems

Direzione di ricerca

Start by reading the plan message's trajectory segment fields and how plan_executor handles departure_action and arrival_action. The issue proposes an Action and ActionProgress component on ~/plan/action/, with custom executors publishing progress on ~/plan/action/progress; identify the message definitions and execution entry points before estimating the design. Done means an action can be dispatched to an executor and its progress reported, but the issue leaves the interface details open.

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

Descrizione

enhancement
Before proceeding, is there an existing issue or discussion for this?
Description

In the plan message each trajectory segment generally consists of a departure_action and an arrival_action. These are meant to be workflows which you execute. Ideally, we would use crossflow, but as we want to be flexible as to what executor can use we should perhaps use an RPC call from our plan_executor to the relevant process execution node. For this we should consider adding a ~/plan/action node.

Implementation Considerations

One option is to directly extend the Progress message with an additional field. This would make sense if the agent is the one executing an action. It makes a lot less sense when the executor may be used to orchestrate multiple devices centrally.

The better option IMO would be to introduce an Action and ActionProgress field which publishes on the ~/plan/action/ component so we could have custom executors that listen for Action messages execute them and publish the progress of the execution on the ~/plan/action/progress topic.

Alternatives

No response

Additional information

No response

Lingua principale
Python
Stelle
10
Fork
9
Merge medio
3h 21m
PR unite (30g)
1

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 open-rmf/next_gen_prototype

Tutte le issue di open-rmf/next_gen_prototype

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.