CLI reports.h5: repeated task without changes loses its iteration dimension

Abierto
#2,191 1 comentario 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
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java
Área
backend

Línea de trabajo

Start with the synthetic archive SimulatorSupportsRepeatedTasksWithLinearUniformRanges/1.execution-should-succeed.omex under vcell-cli/src/test/resources/bsts-omex/synths/sedml/ and with BSTSBasedOmexExecTest, which currently checks only success. Then trace how the SED-ML importer turns a repeatedTask with no setValue changes into MathOverrides, and why the run collapses to one job. Done means the __repeated_task_report shape matches the expected [4, 2, 1, 11] and the test asserts report shapes.

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

Descripción

Summary

A SED-ML repeatedTask that iterates without changing anything is reported without its iteration dimension.

The BioSimulators synthetic archive SimulatorSupportsRepeatedTasksWithLinearUniformRanges/1.execution-should-succeed.omex (in vcell-cli/src/test/resources/bsts-omex/synths/sedml/) has a repeated task over a 2-point uniformRange with no setValue changes. VCell writes __repeated_task_report with shape [4, 11]. BioSimulators expects [4, 2, 1, 11]: data sets × iterations × sub-tasks × time points.

The same happens for the other synthetic repeated-task archives I checked: Logarithmic, Vector, Functional, Nested and MultipleSubTasks ranges.

BSTSBasedOmexExecTest doesn't catch this because it only checks that execution succeeds, not the report shapes.

Likely cause

Repeated tasks become VCell parameter scans through MathOverrides. With no change targeting a parameter there is nothing to scan, so the run collapses to one job and the iteration axis disappears. This needs confirming in the SED-ML importer.

Lenguaje dominante
Java
Estrellas
140
Forks
35
Merge medio
17 h 39 min
PR fusionados (30 d)
19

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 virtualcell/vcell

Todos los issues de virtualcell/vcell

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.