feat: allow specifying multiple values for properties in an instance
Los mantenedores suelen responder en 1 día
@christian-pinto ya está trabajando en esto.
Desde el 28/9/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Description
I would like a way for a problem instance to a sweep of one or more variables.
An example is given in https://zib-aopt.github.io/QOBLIB/instance.html?problem=06&name=a050_t10_s00_b020 where the parameter lambda has multiple values
This would allow us to add this QOBLIB problem instance, a050_t10_s00_b020 (and the others), as defined there which we can't currently do.
Proposed Solution
Proposed solution is to define the properties of the instance in the same way as an entity space. This naturally allows defining a sweep.
The previous solution will not work in this case because
- each lambda value is a separate input file.
- which lambda value is which is only stored in the file name
That is, as is reading only the files you have to know how the lambda value was stored. The qoblib results display works because the submitter of a result can make this mapping in the submission. The website does not have to understand the mapping.
The problem remains in how to handle the difference between parameters which can have exactly one of a set of values (the artefact files) and the others. Right now I propose keeping them separate as they are - later we might find a way to define everything as an entity space (e.g. using constraints).
Alternate Solutions
Define in one instance folder multiple sub-instances which are then rendered as being one instance in the dashboard.
For example in this case one folder for lamdba=0, lambda=1e-6 etc.
Additional Context
If showing on a leadeboard the varying parameters would have to be added to instance name in same was a parameterized experiment. This doesn't happen on QOBLIB and leads to a bug where the best value for 050_t10_s00_b020 is actually the best value for one of the lambdas.
- Lenguaje dominante
- Python
- Estrellas
- 3
- Forks
- 7
- Merge medio
- 15 h 34 min
- PR fusionados (30 d)
- 18
Preparar el entorno
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de IBM/algorithm-nexus
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
IBM/algorithm-nexus#159 ·
Los mantenedores suelen responder en 1 día
-
feat: enabling associating experiment results to a benchmark instance when number of instance properties exceeds experiment propertiesPosiblemente ocupada @christian-pinto la tomó hoy. Abiertoenhancement
IBM/algorithm-nexus#282 · 1 comentario · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
docs: improve readmeAbierto
Dificultad 3/5 1-2 días Aptitud para principiantes 68/100
IBM/algorithm-nexus#276 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
IBM/algorithm-nexus#254 ·
Los mantenedores suelen responder en 1 día
-
Test bmfm-targets with vllm >= 0.29.0Posiblemente ocupada @sivanravidos la tomó hace 18 días. Abierto
IBM/algorithm-nexus#240 · 1 asignado ·
Los mantenedores suelen responder en 1 día
Todos los issues de IBM/algorithm-nexus
Issues similares
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
Los mantenedores suelen responder en 1 día
-
https://search.utilibre.orgAbiertoinstance instance add
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
searxng/searx-instances#941 · 1 comentario ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
FluidNumerics/fluid-walk-blocker#89 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día