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

Track ESGF-retracted datasets and the results that used them

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

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend-api-design, data-engineering

Línea de trabajo

Start by tracing the periodic ingest and the ref datasets retract <slug> CLI entry point, then inspect Dataset.retracted_at, Execution.retracted, and the ESGF intake query. The issue proposes checking ingested CMIP6, CMIP7, and obs4MIPs datasets and marking affected latest executions; first resolve the open questions about execution handling, re-solving groups, and index failures. Done when the chosen behavior is implemented for periodic and manual runs.

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

Descripción

ESGF retracts datasets that have errors, but the REF never finds out. Results computed from a retracted dataset stay live and look the same as any other result.

What we have

  • ref datasets retract <slug> sets Dataset.retracted_at by hand, which stops the solver selecting that dataset. It doesn't touch the executions that already used it (#802).
  • Execution.retracted exists and the results readers hide retracted executions by default, but nothing in the codebase ever sets it.
  • The ESGF index carries a retracted flag per dataset. intake-esgf passes retracted=False by default, so our searches never see a retracted dataset rather than telling us one was retracted.

Proposal

  • Add a check that queries the ESGF index for the instance ids of the ingested CMIP6/CMIP7/obs4MIPs datasets and finds the ones flagged retracted=True.
  • Set retracted_at on those datasets.
  • Mark the latest execution of every group that used a retracted dataset as retracted, so the results readers and the frontend drop or flag them.
  • Run it from the periodic ingest, with a CLI entry point for running it by hand.

Open questions

  • Should a retracted input retract the execution outright, or should we record which inputs were retracted and let the readers decide?
  • Do we re-solve affected groups? A newer version of the dataset is often published alongside the retraction, so re-solving would pick it up.
  • What to do when the index can't be reached. Probably skip and warn, never unretract.
Lenguaje dominante
Python
Estrellas
27
Forks
14
Merge medio
1 d 2 h
PR fusionados (30 d)
75

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 Climate-REF/climate-ref

Todos los issues de Climate-REF/climate-ref

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.