Skip to content

[doc] [zh_cn]Add docs for judge evaluate and gedit extend benchmark#168

Merged
GaoHuaZhang merged 7 commits intoAISBench:masterfrom
SJTUyh:gedit_doc
Mar 5, 2026
Merged

[doc] [zh_cn]Add docs for judge evaluate and gedit extend benchmark#168
GaoHuaZhang merged 7 commits intoAISBench:masterfrom
SJTUyh:gedit_doc

Conversation

@SJTUyh
Copy link
Collaborator

@SJTUyh SJTUyh commented Mar 5, 2026

Thanks for your contribution; we appreciate it a lot. The following instructions will make your pull request healthier and help you get feedback more easily. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
感谢您的贡献,我们非常重视。以下说明将使您的拉取请求更健康,更易于获得反馈。如果您不理解某些项目,请不要担心,只需提交拉取请求并从维护人员那里寻求帮助即可。

PR Type / PR类型

  • Feature(功能新增)
  • Bugfix(Bug 修复)
  • Docs(文档更新)
  • CI/CD(持续集成/持续部署)
  • Refactor(代码重构)
  • Perf(性能优化)
  • Dependency(依赖项更新)
  • Test-Cases(测试用例更新)
  • Other(其他)

Related Issue | 关联 Issue
Fixes #(issue ID / issue 编号) / Relates to #(issue ID / issue 编号)

🔍 Motivation / 变更动机

Please describe the motivation of this PR and the goal you want to achieve through this PR.
请描述您的拉取请求的动机和您希望通过此拉取请求实现的目标。
Add docs for judge evaluate and gedit extend benchmark

📝 Modification / 修改内容

Please briefly describe what modification is made in this PR.
请简要描述此拉取请求中进行的修改。
Add docs for judge evaluate and gedit extend benchmark

📐 Associated Test Results / 关联测试结果

Please provide links to the related test results, such as CI pipelines, test reports, etc.
请提供相关测试结果的链接,例如 CI 管道、测试报告等。

⚠️ BC-breaking (Optional) / 向后不兼容变更(可选)

Does the modification introduce changes that break the backward compatibility of the downstream repositories? If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
是否引入了会破坏下游存储库向后兼容性的更改?如果是,请描述它如何破坏兼容性,以及下游项目应该如何修改其代码以保持与此 PR 的兼容性。

⚠️ Performance degradation (Optional) / 性能下降(可选)

If the modification introduces performance degradation, please describe the impact of the performance degradation and the expected performance improvement.
如果引入了性能下降,请描述性能下降的影响和预期的性能改进。

🌟 Use cases (Optional) / 使用案例(可选)

If this PR introduces a new feature, it is better to list some use cases here and update the documentation.
如果此拉取请求引入了新功能,最好在此处列出一些用例并更新文档。

✅ Checklist / 检查列表

Before PR:

  • Pre-commit or other linting tools are used to fix the potential lint issues. / 使用预提交或其他 linting 工具来修复潜在的 lint 问题。
  • Bug fixes are fully covered by unit tests, the case that causes the bug should be added in the unit tests. / 修复的 Bug 已完全由单元测试覆盖,导致 Bug 的情况应在单元测试中添加。
  • The modification is covered by complete unit tests. If not, please add more unit tests to ensure the correctness. / 此拉取请求中的修改已完全由单元测试覆盖。如果不是,请添加更多单元测试以确保正确性。
  • All relevant documentation (API docs, docstrings, example tutorials) has been updated to reflect these changes. / 所有相关文档(API 文档、文档字符串、示例教程)已更新以反映这些更改。

After PR:

  • If the modification has potential influence on downstream or other related projects, this PR should be tested with those projects. / 如果此拉取请求对下游或其他相关项目有潜在影响,应在那些项目中测试此 PR。
  • CLA has been signed and all committers have signed the CLA in this PR. / CLA 已签署,且本 PR 中的所有提交者均已签署 CLA。

👥 Collaboration Info / 协作信息

  • Suggested Reviewers / 建议审核人: @xxx
  • Relevant Module Owners / 相关模块负责人: @xxx
  • Other Collaboration Notes / 其他协作说明:

🌟 Useful CI Command / 实用的CI命令

Command / 命令 Introduction / 介绍
/gemini review Performs a code review for the current pull request in its current state by Gemini. / 对当前拉取请求在当前状态下由 Gemini 执行代码审核。
/gemini summary Provides a summary of the current pull request in its current state by Gemini. / 对当前拉取请求在当前状态下由 Gemini 提供摘要。
/gemini help Displays a list of available commands of Gemini. / 显示 Gemini 可用命令的列表。
/readthedocs build Triggers a build of the documentation for the current pull request in its current state by Read the Docs. / 触发当前拉取请求在当前状态下由 Read the Docs 构建文档。

@github-actions github-actions bot added the docs label Mar 5, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

此拉取请求通过引入新的中文文档来扩展AISBench的评估能力。它详细介绍了如何使用裁判模型进行评估,这对于没有标准答案或需要更深入评估过程的场景至关重要。此外,还新增了关于GEdit-Bench基准测试的文档,为真实世界指令图像编辑提供了评估指南。这些文档的添加旨在提升用户对AISBench工具的理解和使用体验,使其能够更灵活地应对复杂的模型评估需求。

Highlights

  • 裁判模型评估文档: 新增了关于如何使用裁判模型进行模型评估的详细中文教程,涵盖了其必要性、快速上手指南、配置方法和结果分析。
  • GEdit-Bench基准测试文档: 新增了GEdit-Bench(Genuine Edit-Bench)测评基准的中文文档,介绍了其核心定位、数据集、测评指标以及在AISBench中进行实践的详细步骤。
  • 数据集配置更新: 更新了aime2025数据集的README.md,加入了aime2025_gen_0_shot_llmjudge任务的描述,以支持裁判模型评估。

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • ais_bench/benchmark/configs/datasets/aime2025/README.md
    • 新增了aime2025_gen_0_shot_llmjudge任务的表格条目,包括其评估指标和配置文件路径。
  • docs/source_zh_cn/advanced_tutorials/judge_model_evaluate.md
    • 新增了关于如何使用裁判模型进行评估的详细教程。
    • 解释了裁判模型评估的必要性,并提供了快速上手指南。
    • 包含了配置裁判模型、执行命令、查看任务细节和输出结果的步骤。
    • 拓展了裁判模型在多任务测评、中断续测等场景下的应用。
  • docs/source_zh_cn/extended_benchmark/lmm_generate/gedit_bench.md
    • 新增了GEdit-Bench测评基准的简介,包括其核心定位、数据集信息和测评指标。
    • 提供了在AISBench中实践GEdit-Bench测评的详细步骤,包括环境准备、测评配置和启动测评。
    • 说明了如何处理和展示测评结果,以及如何将AISBench结果用于GEdit-Bench工具。
  • docs/source_zh_cn/extended_benchmark/lmm_generate/index.rst
    • 新增了拓展多模态生成类评测基准的索引文件,并包含了gedit_bench文档。
  • docs/source_zh_cn/index.rst
    • 在“高级教程”部分新增了judge_model_evaluate文档的引用。
    • 新增了“拓展评测基准”章节,并引用了extended_benchmark/lmm_generate/index
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

本次拉取请求主要增加了裁判模型评估和GEdit-Bench基准测试的文档,并更新了相关数据集配置。文档内容详尽,对用户理解和使用新功能非常有帮助。但在文档中发现了一些表述不清晰和图示与文字描述不一致的问题,建议进行修正以提高文档的准确性和易读性。

Comment on lines +239 to +244
D --> E[从裁判模型判断结果中提取相关指标得分]
E --> F((精度数据))
F --> G[呈现结果]

classDef green fill:#90EE90,stroke:#228B22,stroke-width:2px;
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

关于--mode infer_judge的mermaid图示与文字描述存在不一致。文字描述指出该模式“不进行指标提取”,但图示却包含了“从裁判模型判断结果中提取相关指标得分”和“呈现结果”的步骤。请修正图示以准确反映该模式的行为,即图示应在“裁判模型的判断结果”处结束。

Suggested change
D --> E[从裁判模型判断结果中提取相关指标得分]
E --> F((精度数据))
F --> G[呈现结果]
classDef green fill:#90EE90,stroke:#228B22,stroke-width:2px;
```
graph LR;
A[基于给定数据集执行推理] --> B((被测模型的推理结果))
B --> C[裁判模型对被测模型推理结果进行判断]:::green
C --> D((裁判模型的判断结果)):::green
classDef green fill:#90EE90,stroke:#228B22,stroke-width:2px;

D --> E[基于精度数据生成汇总报告]
E --> F((呈现结果))
```
当时有些测评场景中没有标准答案,或者不仅需要看标准答案,还要看得到标准答案的过程是否正确。这个时候常规的答案提取方式就无法满足这样的评测场景。因此需要引入裁判模型对被测模型推理结果进行判断。有裁判模型介入的整体测评流程如下:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

在描述一般场景时,使用“当时”可能不够准确,因为它暗示了一个特定的时间点。建议使用“然而,在某些”或“在某些”来更普遍地引入这种场景。

Suggested change
当时有些测评场景中没有标准答案,或者不仅需要看标准答案,还要看得到标准答案的过程是否正确。这个时候常规的答案提取方式就无法满足这样的评测场景。因此需要引入裁判模型对被测模型推理结果进行判断。有裁判模型介入的整体测评流程如下:
然而,在某些测评场景中没有标准答案,或者不仅需要看标准答案,还要看得到标准答案的过程是否正确。


### 运行命令前置准备
- `--models`: 使用`vllm_api_general_chat`模型任务,需要准备支持`v1/chat/completions`子服务的推理服务,可以参考🔗 [VLLM启动OpenAI 兼容服务器](https://docs.vllm.com.cn/en/latest/getting_started/quickstart.html#openai-compatible-server)启动推理服务(被测模型是一个推理服务,裁判模型是另一个推理服务,快速入门如果图方便也可以共用一个服务)
- `--datasets`: 使用`aime2025_gen_0_shot_llmjudge`数据集任务,需要准备aime2025数据集,可以从🔗 [opencompass
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

“opencompass 提供的”可以简化为“opencompass 的”,使表达更简洁。

Suggested change
- `--datasets`: 使用`aime2025_gen_0_shot_llmjudge`数据集任务,需要准备aime2025数据集,可以从🔗 [opencompass
提供的aime2025数据集压缩包

### 运行命令前置准备
- `--models`: 使用`vllm_api_general_chat`模型任务,需要准备支持`v1/chat/completions`子服务的推理服务,可以参考🔗 [VLLM启动OpenAI 兼容服务器](https://docs.vllm.com.cn/en/latest/getting_started/quickstart.html#openai-compatible-server)启动推理服务(被测模型是一个推理服务,裁判模型是另一个推理服务,快速入门如果图方便也可以共用一个服务)
- `--datasets`: 使用`aime2025_gen_0_shot_llmjudge`数据集任务,需要准备aime2025数据集,可以从🔗 [opencompass
提供的aime2025数据集压缩包](http://opencompass.oss-cn-shanghai.aliyuncs.com/datasets/data/aime2025.zip)下载。将解压后的`aime2025/`文件夹部署到AISBench评测工具根路径下的`ais_bench/datasets`文件夹下。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

对于文件夹的操作,使用“部署到”可能过于正式,通常用于软件或服务的部署。建议使用“放置到”或“复制到”来更准确地描述将文件夹放到指定位置的操作。

Suggested change
提供的aime2025数据集压缩包](http://opencompass.oss-cn-shanghai.aliyuncs.com/datasets/data/aime2025.zip)下载。将解压后的`aime2025/`文件夹部署到AISBench评测工具根路径下的`ais_bench/datasets`文件夹下。
将解压后的`aime2025/`文件夹放置到AISBench评测工具根路径下的`ais_bench/datasets`文件夹下。


### 测评指标(MLLM 自动评分,满分10分)
- **G_SC, Q_SC(语义一致性)**:编辑结果与指令的匹配度
- **G_PQ, Q_PQ(图像质量)**:清晰度、细节保留、无伪影
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Q_0可能是一个笔误,为了与G_O保持一致性,建议修改为Q_O

Suggested change
- **G_PQ, Q_PQ(图像质量)**:清晰度、细节保留、无伪影
G_O, Q_O(综合得分)

| gedit-2-PQ_judge | 16dd59 | PQ | gen | - | - | 7.22 | - |
| gedit-3-SC_judge | 16dd59 | SC | gen | - | - | - | 7.31 |
| gedit-3-PQ_judge | 16dd59 | PQ | gen | - | - | - | 7.24 |

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

日志路径中lmm_exmaple存在拼写错误,应为lmm_example

Suggested change
[2026-03-04 15:40:45,583] [ais_bench] [INFO] write markdown summary to /workplace/benchmark/ais_bench/configs/lmm_example/outputs/default/20260213_150110/summary/summary_20260304_152835.md

SJTUyh and others added 3 commits March 5, 2026 17:23
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@GaoHuaZhang GaoHuaZhang merged commit 9abdd80 into AISBench:master Mar 5, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants