Export in the format of a technique (NXcanSAS, ORSO), in place of the generic HDF5 files

Abierto
  • ¿Algo no está bien?
#176 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
32/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend, data

Línea de trabajo

Read ess.apps.batch.export.export_table and write_outputs, which the issue identifies as the export path, then compare the current ess.apps.hdf5 output with the requested NXcanSAS and ORSO formats. Decide where writers live, how each output selects a writer, and what happens when none is available; the issue leaves these design questions open. Done means exports use the appropriate technique format and the workspace files are no longer misclassified as calibration.

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

Descripción

essapps-batch export and ess.apps.batch.export.export_table (#174) write each output of a record as <key>/<output>.h5 in the format of the folder store (ess.apps.hdf5): scipp HDF5, with a group as a DataGroup of its fields. This is a placeholder. scipp.io.load_hdf5 reads the files, but no other SANS or reflectometry tool does.

Wanted: an output is exported in the format of its technique, such as NXcanSAS for I(Q) or ORSO for reflectivity.

Open questions:

  • Where does a writer live, and what selects it? Candidates: the output type (a writer per group class, provided by the instrument or technique package), or the spec.
  • Does export stay a step over the record column of the table, with the writer chosen per output? I think so: the table and the step need not change, only what write_outputs writes.
  • What does an output without a writer do: fall back to the generic file, or refuse?
  • The same writers would serve a later publish to SciCat, where a column of catalogue identifiers takes the place of the paths.

A side effect that goes away with this: files exported into the workspace folder are scipp HDF5, which LoKI's read_metadata lists as kind: calibration in a later essapps-batch files.

Lenguaje dominante
Python
Estrellas
0
Forks
1
Merge medio
8 h 48 min
PR fusionados (30 d)
70

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 scipp/essapps

Todos los issues de scipp/essapps

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.