Triangulation and alert grouping

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Área
api

Línea de trabajo

Start by reviewing the listed pyro-api issues #662, #643, and #638, then collect and describe example cases of triangulation problems. This epic is blocked on pyronear/roadmap#4 and also depends on localisation work in pyronear/vision-rd#153. Done means the examples are documented, grouping rules are specified, follow-up issues are created, and the listed issues are closed.

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

Descripción

epic P2 T1-27

Context & Objective

Alerts group the sequences of several cameras and triangulate a position. Some cases go wrong: a fire's detections taken by another sequence after a merged giant bounding box, alerts that are redundant, not crossed or crossed too much (same camera at different poses), a fire at the edge of two poses of the same camera. We want to make the grouping and the triangulation of alerts more reliable.

Not specified yet. The grouping rules depend on the localisation work: one-frame localisation (pyronear/roadmap#4) and the smoke origin point (pyronear/vision-rd#153). This epic is blocked by pyronear/roadmap#4 until that work is done.

What has to be done

Existing issues of pyro-api: pyronear/pyro-api#662, pyronear/pyro-api#643, pyronear/pyro-api#638.

  • Collect example cases of triangulation problems (redundant, not crossed, over-crossed, the same camera at two poses).
  • After the localisation work, specify the new grouping rules and create the issues.
  • Later, maybe: triangulation with a neighbouring organisation (to handle with care, to avoid saturating it).

Done when

  • Example cases are collected and described
  • New grouping rules are specified, and the issues are created
  • The listed issues are closed

Theme API · Priority P2 · Period T1-27

Lenguaje dominante
Sin datos de lenguaje
Estrellas
0
Forks
0
Sin PR fusionados en 30 d

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 pyronear/roadmap

Todos los issues de pyronear/roadmap

Issues similares

Más issues de Backend & API Design

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.