Define and Validate Localization Data Interface Conventions

Ouverte
#756 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
18/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
rust
Domaine
robotics

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Rust
Étoiles
282
Forks
12
Merge moyen
2 j 9 h
PR mergées (30 j)
28

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de tier4/awkernel

Toutes les issues de tier4/awkernel

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.