Hacktoberfest 2026: những issue maintainer đã đánh dấu cho tháng Mười, đang mở và phù hợp người mới. Xem issue Hacktoberfest

feat: Per benchmark instance properties

Đang mở
  • Có gì không ổn?
#300 0 bình luận 0 reaction 1 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

@christian-pinto đang làm issue này rồi.

Từ ngày 7/10/2026.

Đánh giá

Issue này chưa được đánh giá.

Mô tả

enhancement

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.

Ngôn ngữ chính
Python
Star
4
Fork
7
Merge trung bình
21 giờ 28 phút
Pull request đã merge (30 ngày)
26

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của IBM/algorithm-nexus

Tất cả issue của IBM/algorithm-nexus

Issue tương tự

Thêm issue về Python

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.