Reproducibility question: canonical VIIRS source and discovery-time contract

Abierto
  • ¿Algo no está bien?
#1 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
25/100
Tipo de issue
Documentación
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
python
Área
data-engineering, documentation

Línea de trabajo

Start by reading pipeline.py and inspecting the released canonical VIIRS feature table, especially the entries for FOD_ID 400645736. Compare the pipeline revision and available source metadata with the reported candidate matches. Done requires maintainers to identify the release inputs, timestamps, filtering rules, and provenance details or provide a construction manifest.

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

Descripción

Hello WildfireIA maintainers, I am independently auditing the discovery-time input contract of the publicly released WildfireIA benchmark. This is a reproducibility request, not an assertion that the benchmark contains an error.

Could you please clarify:

  1. Which exact code commit or script revision constructed the released canonical VIIRS features? Was the public pipeline.py implementation the version actually used for the release?
  2. Which original NASA FIRMS sources, sensors, processing versions, and source snapshots were used? If available, could you provide a version identifier, checksum, or construction manifest?
  3. What timezone convention applies to the underlying FPA-FOD DISCOVERY_DATE and DISCOVERY_TIME fields? How were missing discovery times, apparent 00:00 values, UTC conversion, and daylight-saving time handled?
  4. Were VIIRS detection acquisition times filtered against each individual fire's discovery timestamp, or were detections matched by calendar date and spatial proximity? Were original publication/ingest timestamps retained?
  5. For FOD_ID 400645736, the released canonical feature table contains two VIIRS detections within 1 km. Our retrospective lookup using current standard-processed SNPP and NOAA-20 sources returns four candidate matches. Could you identify the original two detections (sensor, acquisition timestamp, coordinates, FRP, or stable detection/granule ID) and any additional filtering or nearest-fire assignment rule? The audit uses a deliberately selected 30-event sample and does not establish a population leakage rate. Original source identity and timestamp semantics would help us distinguish genuine temporal issues from source-version differences. Thank you for your work and for any provenance details you can share.
Lenguaje dominante
Python
Estrellas
3
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.

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.