Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

fix: update benchmarking requirements

已关闭
  • 哪里不对？
#255 1 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@christian-pinto 已经在做这个了。

开始于 2026年9月25日。

  • #261 来自 @michael-johnston —— 已合并

评估

这个 Issue 还没有评估数据。

描述

  • Change the name from Requirements for models benchmarking[¶](http://localhost:8000/requirements/benchmark/#requirements-for-models-benchmarking)
  • In general can drop the terms "Nexus package owner" / "package owner" throughout out. Often we can just us "user" or "experiment owner" or something more generic.

Terminology

Benchmark Target The AI model or algorithm being evaluated. This is the element that varies across benchmark experiments while the benchmark definition and benchmark instance specification are held constant.

This second part of this definition is incorrect (now a benchmark target may be == benchmark experiment). Also it uses a term "benchmark definition" that's not in the terminilolgy. Probably should say - for a given benchmark instance this is the primary element that is varied.

Benchmark Registration and Discoverability

REQ 2.3 uses the bare term benchmark and it's not clear what it is. From the context it sounds like it is a benchmark submission

REQ 2.3: Benchmark Registration The system must provide a method to define and register a benchmark:

The Benchmark Registration and Discoverability requirements miss the requirement adding logical benchmark. instance and the submission These are all someone bundled in current 2.3

Using the Benchmarking System

REQ 3.1 uses bare term benchmark.

主要语言
Python
星标
3
派生
7
平均合并
14 小时 4 分钟
30 天内合并 PR
15

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

IBM/algorithm-nexus 的其他 Issue

查看 IBM/algorithm-nexus 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。