Evaluate Command: Config Design and Functionality for Non-Training Model Evaluation
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 15/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- huggingface, python
调研方向
Start from the evaluate command that PR #264 added, and from the training config it reads to load the latest checkpoint. The issue asks for a config design for evaluating arbitrary models, including Hugging Face Hub downloads, so the first step is agreeing on that config shape in the thread rather than writing code. Done means an agreed config format and a tested evaluate path for models outside training runs.
由索引模型根据 Issue 内容生成。
描述
🎯 Goal (What & Why)
With the merging of PR #264, we will have a separate evaluate command that uses the training config to evaluate a trained model by loading the latest checkpoint.
However, we also need the capability to evaluate arbitrary models — potentially with automatic downloading from the Hugging Face Hub for all supported models.
Here, let's discuss the features we need for such a command and what the configuration file should look like.
🚀 Execution Plan
(This section may start as an incomplete draft but must be defined before implementation begins.)
Step 1: What is the smallest working version?
(Describe the simplest way to implement this feature with minimal effort.)
Step 2: What additional optimizations are possible (but optional)?
(List potential refinements that can be added in later PRs if needed.)
📌 Acceptance Criteria (Must-Haves for Completion)
- The feature must be functional and tested.
- The implementation must be documented in practical terms.
- The PR must include a performance/impact summary.
- No refactors unless directly necessary for feature completion.
🛠️ Project Management
- Assign the project to the Fast-LLM project.
- Set the
Estimatefield (in days) in the GitHub project. - Use the
Sizefield to categorize the PR size (Small/Medium/Large). - Assign an owner when opening the issue.
- 主要语言
- Python
- 星标
- 337
- 派生
- 52
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
ServiceNow/Fast-LLM 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 25/100
ServiceNow/Fast-LLM#556 ·
-
难度 4/5 3-5 天 新手友好度 30/100
ServiceNow/Fast-LLM#538 ·
-
enhancement
难度 5/5 一周以上 新手友好度 12/100
ServiceNow/Fast-LLM#533 ·
-
难度 5/5 一周以上 新手友好度 15/100
ServiceNow/Fast-LLM#510 · 1 条评论 ·
-
难度 5/5 一周以上 新手友好度 12/100
ServiceNow/Fast-LLM#507 ·
查看 ServiceNow/Fast-LLM 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 64/100
-
[Bug]: Responses API 500s on assistant message with empty content list可能已有人在做 @shadowmodder 今天认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 66/100
vllm-project/vllm#64940 ·
维护者通常 1 天内回复
-
limits
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
agent-ready area: docs documentation good first issue
难度 2/5 1-3 小时 新手友好度 78/100
Soneso/stellar-agent-wallet#524 ·
维护者通常 1 天内回复
-
Status: Triage Type: Quest
难度 2/5 1-3 小时 新手友好度 66/100
GTNewHorizons/GT-New-Horizons-Modpack#27490 ·
维护者通常 1 天内回复