Define and Validate Localization Data Interface Conventions

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

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
18/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
rust
Bereich
robotics

Rechercherichtung

The issue names no files, so start by locating the existing NDT, gyro odometry, and EKF interface and test modules in the repository and reading their current timestamp, frame, and covariance handling. Use the acceptance criteria as the checklist: document conventions, preserve measurement timestamps, add transform and covariance tests, and validate delayed/out-of-order data and missing transforms. Done means the documented interfaces and tests cover each acceptance criterion, with deviations from Autoware conventions recorded.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Define and implement consistent timestamp, coordinate-frame, and covariance conventions across the NDT, gyro odometry, and EKF interfaces in Awkernel. Ensure that measurements retain their physical meaning when exchanged between components.

Scope:

  • Define measurement, arrival, and publication timestamps, including clock domains and units
  • Specify timestamp ordering, buffering, and permitted interpolation or extrapolation
  • Define map, vehicle, and sensor frames, transform directions, and sensor extrinsics
  • Implement required pose and twist transformations using documented reference points
  • Define covariance layouts, units, and transformation rules consistent with the selected state representation
  • Validate incoming data and document handling of missing transforms, invalid covariance, and unsupported timestamps

Acceptance criteria:

  • Interface documentation specifies frames, timestamps, units, covariance ordering, and validity requirements for each input and output.
  • Measurement timestamps are preserved through processing rather than replaced by arrival or publication times.
  • Transform tests cover identity transforms, known translations and rotations, inverse transformations, and non-identity sensor extrinsics.
  • Twist transformations account for reference-point changes where required, rather than applying rotation alone indiscriminately.
  • Covariance transformations use the appropriate Jacobian for the defined representation and preserve relevant cross-covariance terms.
  • Tests cover delayed and out-of-order measurements, unavailable transforms, and invalid covariance values.
  • Integration tests confirm that NDT pose and gyro odometry twist are interpreted consistently by the EKF.
  • Any deviations from the selected Autoware reference conventions are documented.

Out of scope:

Sensor calibration estimation, hardware clock synchronization, changes to the NDT or EKF algorithms, and full-pipeline performance benchmarking.

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.