Define and Implement Input Freshness and Overload Policies

Aperta
#764 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
18/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust

Direzione di ricerca

Start by reading the Awkernel localization pipeline modules that ingest input streams, hold buffers, and publish status events; the issue names no files, so map each input stream and its current timeout, buffer, and deadline handling first. Then draft the policy matrix from the acceptance criteria before touching code, and use it to drive implementation and fault-injection tests. Done means the matrix is documented, bounded/configurable behavior is implemented, and tests cover stale inputs, missing messages, overflow, overruns, and late results.

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

Descrizione

Define and implement explicit policies for stale or missing inputs, bounded buffers, and processing overruns in the Awkernel localization pipeline. Ensure that abnormal conditions produce observable and predictable behavior rather than unbounded backlog or silently invalid estimates.

Scope:

  • Define freshness limits and missing-input timeouts for each input stream
  • Specify buffer capacities and overflow behavior, such as dropping oldest or newest messages
  • Define component-specific behavior when required data is unavailable, including bounded waiting, skipping updates, or explicitly flagged fallback
  • Define handling of deadline overruns, overlapping activations, and late results
  • Specify recovery conditions and estimator-reset behavior where necessary
  • Report policy decisions through structured status events and counters

Acceptance criteria:

  • A policy matrix documents each condition, detection rule, threshold, action, output-validity status, and recovery condition.
  • Waiting periods and buffer capacities are bounded and configurable.
  • Component-specific requirements are respected; motion history is not discarded while still required for an admitted scan without an explicit failure outcome.
  • Stale or missing data is not silently reused as a fresh measurement, and prediction-only outputs are distinguishable from measurement-updated outputs.
  • Deadline overruns do not create uncontrolled overlapping executions or unlimited catch-up work.
  • Late or cancelled computations cannot overwrite newer state or access released buffers; cancellation is used only where supported safely.
  • Fault-injection tests verify the expected behavior for stale inputs, missing messages, buffer overflow, processing overruns, and recovery.
  • Logs distinguish input rejection, queue overflow, skipped updates, deadline misses, and discarded late results.
  • Any deviations from the selected Autoware reference behavior are documented.

Out of scope:

Fault-injection infrastructure, new scheduling algorithms, vehicle-level emergency-stop behavior, and formal safety certification.

Lingua principale
Rust
Stelle
282
Fork
12
Merge medio
2g 9h
PR unite (30g)
28

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 tier4/awkernel

Tutte le issue di tier4/awkernel

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.