Reproducibility question: canonical VIIRS source and discovery-time contract

Aperta
  • Qualcosa non va?
#1 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Documentazione
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
python
Ambito
data-engineering, documentation

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
Python
Stelle
3
Fork
0
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.