feat: Per benchmark instance properties
维护者通常 1 天内回复
@christian-pinto 已经在做这个了。
开始于 2026年10月7日。
评估
这个 Issue 还没有评估数据。
描述
Motivation
Given a problem class with some general properties that define it, there may be a variety of "free" variables that one could set to generate instances of the problem. For example I create an instance with all the problem class properties but I add an additional "penalty" property.
At the moment I would have to do one of two things to add such an instance
- Not mention this penalty property (maybe just in description). It will not be in any table etc.
- Create a new problem class that is same as existing except with the penalty property
The first is problematic as I can't see this additional property in any table. The second is annoying as I have to keep adding problem class whenever I want to try setting some additional parameter or constraint on my instance.
Proposed Solution
Allow instances to define their own "generative" property and associated values. This is additional information used to create an instance that matches the general structure of the problem class but with instance specific features. These properties could be shown in the instance table view but hidden in the problem class view.
The overall benefit is to have more flexibility in the type of benchmark instances that can be added under a problem class.
Additional Context
This does bring the question of an ever expanding tree of instances.
That is someone else comes along with an instance that also has same extra features as my instance but different values. With above solution you would not see these as related. You could then request that these should be related so you want an "instance class" as well as "problem class" in the taxonomy, but then you can always have same problem again.
The proposed solution to this is to just to keep the two levels (problem class and instance) and let instances have their free parameters. If many instances are added with the same free parameters and it's deemed that they need to be collected together so we can create tables with all then a new problem class is created.
Additionally by allowing the user to create in UI a custom "query key" it should be possible for them to aggregate any data they want, addressing niche use cases without having to add additional structure.
- 主要语言
- Python
- 星标
- 4
- 派生
- 7
- 平均合并
- 21 小时 28 分钟
- 30 天内合并 PR
- 26
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
IBM/algorithm-nexus 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
IBM/algorithm-nexus#159 ·
维护者通常 1 天内回复
-
feat: allow specifying multiple values for properties in an instance可能已有人在做 @christian-pinto 于 17 天前认领。 未关闭enhancement
IBM/algorithm-nexus#277 · 1 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 68/100
IBM/algorithm-nexus#276 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 45/100
IBM/algorithm-nexus#254 ·
维护者通常 1 天内回复
-
Test bmfm-targets with vllm >= 0.29.0可能重新可做 @sivanravidos 于 34 天前认领，目前没有进行中的 PR。 未关闭
IBM/algorithm-nexus#240 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 IBM/algorithm-nexus 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
cathrynlavery/diagram-design#441 ·
维护者通常 2 天内回复
-
[Cleanup] Include the public header in work_split.cpp可能已有人在做 @blozano-tt 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
tenstorrent/tt-metal#60850 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
backend::sglang bug language::python observability
难度 2/5 半天 新手友好度 65/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 75/100
OpenShot/openshot-qt#6202 ·
维护者通常 1 天内回复