Integrate EKF-Based Initial Pose Estimation for NDT

Offen
#757 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

@nokosaaan arbeitet bereits daran.

Seit 13.11.2026.

  • #796 von @nokosaaan — offen

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
12/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
rust
Bereich
robotics

Rechercherichtung

The payload names no files, tests or entry points, so start by finding the existing NDT scan-matching and EKF pose code in the repository and reading how poses and timestamps flow between them. This is design work: the interpolation limits, fallback policy and reset behavior are undecided, so agree on them with maintainers before coding. Done means the listed acceptance criteria hold, with tests for rate mismatch, delayed outputs, missing history, excess horizons and resets.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Use previously available EKF pose estimates or predictions to initialize subsequent NDT scans in Awkernel. Establish a timestamp-aware feedback path without introducing circular waits between NDT and EKF processing.

Scope:

  • Maintain a bounded history of EKF pose estimates with timestamps and validity information
  • Select or derive an initial pose at the reference timestamp of each NDT scan
  • Define permitted interpolation and prediction methods, including maximum time gaps and prediction horizons
  • Apply the coordinate transforms required by the NDT initial-pose interface
  • Define startup, stale-estimate, missing-history, and estimator-reset behavior
  • Record which EKF estimates were used to initialize each scan

Acceptance criteria:

  • Each NDT scan receives an initial pose corresponding to its reference timestamp within the defined temporal limits.
  • Only EKF outputs available when the initial pose is selected are used; offline replay does not access outputs unavailable at the corresponding replay time.
  • NDT does not wait for an EKF update that depends on the result of that same scan.
  • Tests cover different NDT/EKF rates, delayed EKF outputs, missing history, excessive prediction horizons, and resets.
  • Startup uses an explicitly supplied initial pose until valid EKF estimates become available.
  • Invalid or stale estimates trigger the documented fallback or scan-rejection policy rather than being used silently.
  • Selected source timestamps, interpolation or prediction intervals, and fallback decisions are logged for reproducibility.
  • Integrated replay tests verify NDT convergence and localization error against predefined criteria.

Out of scope:

Changes to the NDT optimization algorithm or EKF state model, GNSS-based automatic initialization, and global relocalization.

Vorherrschende Sprache
Rust
Sterne
282
Forks
12
Ø Merge
2 T. 9 Std.
Gemergte PRs (30 T.)
28

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus tier4/awkernel

Alle Issues in tier4/awkernel

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.