Validate Temporal and Spatial Consistency for Motion Distortion Correction

Abierto
#762 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust

Línea de trabajo

The issue names no source files, so start by locating the M2 interface conventions it refers to and the existing motion distortion correction code in the awkernel repository. Write scan-level integration tests covering timestamp units, clock-domain mapping, transform direction with non-identity extrinsics, motion-history gaps and out-of-order samples. Done means each failure case produces a diagnostic naming the scan, reason and interval rather than silent output.

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

Descripción

Validate that LiDAR point timestamps, coordinate transforms, and available vehicle motion data are consistent throughout motion distortion correction in Awkernel. Verify the interface conventions defined in M2 using scan-level integration tests.

Scope:

  • Verify the relationship between per-point timestamps, scan timestamps, and the correction reference time
  • Check clock-domain mappings, timestamp units, and coverage of the scan acquisition interval
  • Validate sensor extrinsics, transform directions, and the reference points used for motion estimates
  • Verify that motion samples support the required interpolation or prediction within configured limits
  • Test handling of unavailable transforms, incomplete motion history, and stale inputs

Acceptance criteria:

  • Tests detect incorrect timestamp units, offsets, and clock-domain mappings rather than silently producing corrected output.
  • Every corrected point is supported by motion data or an explicitly permitted prediction within the configured limits.
  • Tests cover motion-history gaps, scan-boundary timestamps, delayed arrivals, and out-of-order samples.
  • Known-motion tests with non-identity sensor extrinsics verify transform direction and reference-point handling.
  • Replay uses only motion data available at the correction decision time; any waiting policy and its latency are explicit.
  • Missing transforms or insufficient motion data trigger the documented rejection or flagged fallback policy.
  • Diagnostics identify the affected scan, failure reason, and relevant timestamp or coverage interval.
  • Test fixtures, expected outcomes, and reproduction steps are documented.

Out of scope:

Redefining the M2 interface conventions, implementing the distortion-correction algorithm, hardware clock synchronization, and broad fault-injection campaigns.

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.