Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Trim each flight to the airborne portion and segment it into legs

Abierto
  • ¿Algo no está bien?
#229 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 4 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
data

Línea de trabajo

The issue identifies telemetry data, the inference/Results/ output directory, and a hand-built flight test, but names no source files or existing entry point. Start by locating the telemetry processing and test code, then inspect how flight time, altitude, and heading are represented. Done means all flights are trimmed and segmented, gaps and unexpected leg sequences are reported, per-flight leg summaries are produced, and the specified plots and test are added.

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

Descripción

area:ml enhancement python

Blocked by: #228

Is your feature request related to a problem? Please describe.
About 70% of every file is the aircraft sitting on the ground, before and after the flight (roughly 60 min idle, then 24–32 min of flying). Computing deviation over the whole file measures idle time, not flying. A whole-flight standard deviation also mixes a climb, level legs, turns and a descent, which is not comparable to a level-flight target.

Every pilot flew the same route:
takeoff at 180° → climb on 190° to about 3,100 ft → 220° leg with a descent → turn to 040° → return on 000°

Describe the solution you'd like

  • Trimming: cut each flight from the takeoff roll to touchdown, using IAS above a threshold together with altitude above the field. Make the thresholds constants and report the trimmed duration per flight.
  • Gaps: flag any Δt above 3 s and record the count per flight. Do not interpolate. Known gaps: P001_T1 (43 s) and P004_T1 (12 s).
  • Leg segmentation: label each sample with a phase. Proposed phases are takeoff_climb, leg_190, leg_220, turn_040, leg_000 and approach_landing. Detect them from a heading bin held for at least N seconds plus the transitions between bins. Keep the method rule-based and documented. All 19 flights follow the same sequence, so a flight with a missing or extra leg should produce a warning.
  • Output: add a phase column to the telemetry table, plus a per-flight summary with each leg's start, end and duration.
Acceptance criteria
  • Every flight's trimmed duration falls between 20 and 35 min, or the flight is listed as an exception with a reason (P004_T1 is a likely exception: it is only 33 min in total)
  • A plot of altitude and heading against time, coloured by phase, for every flight, saved to inference/Results/ (gitignored)
  • Tests run on a hand-built flight with a known leg sequence
Lenguaje dominante
Rust
Estrellas
4
Forks
8
Merge medio
3 d 12 h
PR fusionados (30 d)
16

Preparar el entorno

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 oss-slu/PilotDataSynchronization

Todos los issues de oss-slu/PilotDataSynchronization

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.