feat: allow specifying multiple values for properties in an instance
Maintainers usually reply within 1 day
@christian-pinto is already working on this.
Since Sep 28, 2026.
Assessment
This issue has not been assessed yet.
Description
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.
- Dominant language
- Python
- Stars
- 4
- Forks
- 7
- Avg merge
- 18h 13m
- Merged PRs (30d)
- 18
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from IBM/algorithm-nexus
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
IBM/algorithm-nexus#159 ·
Maintainers usually reply within 1 day
-
bug: `nexus validate logical-benchmarks` does not fail when instances are misplacedPossibly taken @AlessandroPomponio claimed this 1 day ago. Openbug
IBM/algorithm-nexus#288 · 1 assignee ·
Maintainers usually reply within 1 day
-
feat: enabling associating experiment results to a benchmark instance when number of instance properties exceeds experiment propertiesPossibly taken @christian-pinto claimed this 3 days ago. Openenhancement
IBM/algorithm-nexus#282 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
docs: improve readmeOpen
Difficulty 3/5 1-2 days Newbie friendliness 68/100
IBM/algorithm-nexus#276 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
IBM/algorithm-nexus#254 ·
Maintainers usually reply within 1 day
All issues in IBM/algorithm-nexus
Similar issues
-
good first issue hacktoberfest
Difficulty 1/5 Under an hour Newbie friendliness 92/100
RogueAlg0/taken#387 · 4 comments ·
Maintainers usually reply within 1 day
-
tool-calling
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
vllm-project/vllm#59838 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
raullenchai/Rapid-MLX#4042 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
transitmatters/mbta-slow-zone-bot#70 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
open-webui/open-webui#31871 · 1 comment ·
Maintainers usually reply within 1 day