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

retrieve: vos can't fetch data exposures: images, weights and flags sit in three vos dirs

Abierto
  • ¿Algo no está bien?
#965 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python, shell
Área
cloud, data

Línea de trabajo

Start with workflow/config/cfis/config_exp_Gie.ini, where all three exposure inputs share one $SP_INPUT_EXPOSURES root, and with the retrieve: vos handling for inputs.exposures in the Python config code. The issue also names scripts/stage_block.sh and the nibi and candide profiles. Choosing between the per-kind roots (option 1) and the stage-first contract (option 2) is a maintainer decision, so the work is not settled yet. Done means the chosen option lets each exposure kind resolve to its own vos directory, or the docs and staging script reflect the stage-first contract.

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

Descripción

retrieve: vos cannot fetch the single exposures of a data run.

What breaks. workflow/config/cfis/config_exp_Gie.ini points all three exposure inputs at one root:

INPUT_PATH = $SP_INPUT_EXPOSURES, $SP_INPUT_EXPOSURES, $SP_INPUT_EXPOSURES
INPUT_FILE_PATTERN = 000000, 000000.weight, 000000.flag

On CADC the three kinds live in three vos directories: images in vos:cfis/pitcairn, weights in vos:cfis/weights, flags in vos:cfis/flags. With retrieve: vos, any single inputs.exposures URL leaves two of the three missing. (Tile images and catalogues are unaffected: they share vos:cfis/tiles_DR6.)

Why production hasn't hit it. The nibi profile uses retrieve: symlink against a staged mirror, /project/def-mjhudson/unions-wl/exposures, filled beforehand by a compute-node job (unions-wl/scripts/stage_block.sh, which runs vcp per kind; Nibi compute nodes reach CADC). The candide profile sets retrieve: vos but has no exposures input, so as written it would need one.

Options.

  1. One input root per file kind (inputs.exposures: {image: vos:cfis/pitcairn, weight: vos:cfis/weights, flag: vos:cfis/flags}, a string still meaning one root for all three), exported as three variables for Gie's INPUT_PATH.
  2. A documented "stage first" contract: data runs take a local mirror with retrieve: symlink, the staging script moves into the repo, and retrieve: vos is limited to tiles and catalogues.

Option 1 keeps retrieve: vos honest at little cost. Option 2 matches how the Nibi campaigns actually run (staging overlaps the previous batches, and a CADC hiccup fails a staging job rather than a 144-core batch).

Found by the Nibi scale-up runs (integration/smk-g18, 11 Oct).

Claude (Opus 5.5) on behalf of Cail.

Lenguaje dominante
Python
Estrellas
18
Forks
14
Merge medio
2 d 10 h
PR fusionados (30 d)
37

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 CosmoStat/shapepipe

Todos los issues de CosmoStat/shapepipe

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.