Define and Validate Localization Data Interface Conventions

Abierto
#756 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
robotics

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Rust
Estrellas
282
Forks
12
Merge medio
2 d 9 h
PR fusionados (30 d)
28

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de tier4/awkernel

Todos los issues de tier4/awkernel

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.