Skip to content

[Task] 0 Day Model Support: Reusable Integration Experience from Transformers to GPU and NPU Inference Engines #315

Open

Description

@david6666666

Current state: Scope is defined at roadmap level only. The body defers the initial models, GPU/NPU engines and environments to the owner, so acceptance criteria 1-5 cannot yet be judged, and no delivery has started. The 2026-11-02 review additionally asks which existing assets this work extends, since workflows/inference-engine-research, hardware/ascend/ascend-model-adaptation and methods/weight-loading-optimization already cover parts of this path.
Decision needed: The initial model, GPU/NPU engine and environment list with versions, the incremental gap relative to those existing skills, and who accepts completion, from the owner @amy-why-3459.
Next action: The owner records that list and the incremental gap in this Issue; knowledge delivery then follows the protected-path admission and index-regeneration rules. No scope, assignment or acceptance is changed by adding this status block.

Parent issue: #316 · InferRSI Roadmap

Goal

Expand reusable integration and optimization experience along the Transformers → GPU Inference Engine → NPU Inference Engine path to improve InferRSI's efficiency in supporting new models.

Owner: @amy-why-3459. Corresponds to original roadmap item 8.

Scope

  • Map the integration path: Starting from a Transformers reference implementation, document how to adapt model architecture, weight mappings, operator implementations, and inference behavior to GPU and NPU engines.
  • Collect engineering cases: Record key changes, compatibility problems, correctness checks, performance bottlenecks, and both successful and unsuccessful attempts.
  • Consolidate reusable experience: Turn cases into searchable, reusable InferRSI knowledge / skills. Specify the model, engine, backend, versions, applicability conditions, and limitations.
  • Validate reuse: Use concrete model cases to assess whether the workflow helps identify gaps, complete integration, and reduce repeated trial and error.

The owner will list the initial models, GPU / NPU engines, and environments in this issue. Record each stage separately as completed, requiring further work, or unverified.

Acceptance Criteria

  • Define the initial model and engine scope, and document the three-stage integration path and its gaps.
  • Produce reusable integration instructions and case records covering key implementation differences, validation methods, and lessons from resolving problems.
  • Include traceable correctness / performance evidence for each case; explicitly mark stages that have not been executed as unverified.
  • Add the experience to the existing knowledge system and make it discoverable through relevant model integration queries.
  • Demonstrate how the knowledge supports new model integration using a concrete case, and record remaining limitations.

Activity

  1. changed the title [-][Task] 0 Day Model Support:完善 Transformers → GPU → NPU 推理引擎适配经验[/-] [+][Task] 0 Day Model Support: Reusable Integration Experience from Transformers to GPU and NPU Inference Engines[/+] on Nov 2, 2026
  2. agent-ci-infra-bot commented on Nov 2, 2026

    @agent-ci-infra-bot

    该 Issue 要求在 Transformers → GPU → NPU 引擎路径上沉淀可复用的新模型接入经验、案例与可检索知识,并以具体案例验证复用价值(Roadmap #316 工作项 8,负责人 @amy-why-3459)。结论:需要补充信息并由人决策,暂不适合无人值守开发——首批模型/引擎/环境与版本尚未列出,交付物与现有技能库的增量缺口未界定,Issue 也缺少仓库约定的状态块与完成验收人;正文没有明确要求修改代码的句子,且 Issue 已被指派。Labels: kind:task, area:knowledge(属知识线交付任务;因无 status:* 标签且 repository 规定 priority 仅随 status:proposed/accepted 使用,故不返回 priority)。

    缺少首批模型 / 引擎 / 环境清单,范围与验收无法判定

    • Where: Issue 正文「首批模型、GPU / NPU 引擎和环境由负责人在本 issue 中列出」;对应验收项 1「明确首批模型与引擎范围」。
    • Problem: 交付范围被显式推迟到负责人后续补充,当前无法确定要覆盖哪些模型、哪些 GPU/NPU 引擎与版本,也无法判断验收项 2–5 何时算完成。仓库要求「Work Issue-first: confirm the governing Issue's accepted scope」(AGENTS.md:117),并把版本与适用范围作为知识记录的必备字段(docs/knowledge-base.md:13-20)。
    • Conditions: 只要清单未落盘,任何执行者(人或 agent)只能自行猜测首批范围。
    • Impact: 容易产出宽泛、不可复用或与既有技能重复的经验条目;也无法对照验收项判断「已完成 / 待补齐 / 未验证」。
    • Fix: 按验收项 1 在 Issue 中列出首批模型(含 checkpoint/任务变体)、GPU 引擎与 NPU 引擎、CANN/TorchNPU/vLLM 等版本和环境,再开始整理。

    交付物与现有知识资产高度重叠,未说明真正的增量缺口

    • Where: 验收项 2、4「形成可复用的适配说明……进入现有知识体系」。
    • Problem: 仓库已有多份覆盖该路径的资产:模型感知准备与引擎研究路由(src/inferrsi/data/skill_library/workflows/inference-engine-research/SKILL.md:15、references/model-aware-preparation.md:1-5)、NPU 侧 checkpoint 接入(src/inferrsi/data/skill_library/hardware/ascend/ascend-model-adaptation/SKILL.md:1-12)、权重加载路径(src/inferrsi/data/skill_library/methods/weight-loading-optimization/SKILL.md:1-6),以及 GPU→NPU 缺口清单先例(docs/drama3-npu-readiness.md:1-9)。SearchSpace 矩阵已把「Model adapter / FP8 / KV 复制」标为已覆盖(docs/searchspace-matrix.md:42)。Issue 未说明要新增或修订哪一条、哪个矩阵单元格仍是缺口。
    • Conditions: 执行者若直接「沉淀经验」,很可能重复既有 skill 或写入与矩阵成熟度冲突的内容。
    • Impact: 知识库膨胀但不增加检索价值,验收项 4「可通过相关模型适配问题检索到」无法证伪。
    • Fix: 在 Issue 中写明相对上述资产的增量缺口(例如缺少 Transformers→引擎的权重映射/算子映射 procedure,而 ascend-model-adaptation 只覆盖 vllm-ascend 侧),并说明是修订既有 skill 还是新建,遵循 npu-skill-factory 的 artifact 路由。相关且已核对:父 Roadmap [Roadmap] InferRSI: Optimization, Evaluation, and Engineering #316(工作项 8 → [Task] 0 Day Model Support: Reusable Integration Experience from Transformers to GPU and NPU Inference Engines #315)、总体 Roadmap [Roadmap] InferRSI: reusable knowledge, verifiable inference optimization #61、GPU→NPU 先例 [RFC] Drama3 NPU task readiness: execution contracts, validation and knowledge supplementation #27。

    缺少仓库约定的三行状态块

    • Where: Issue 正文开头(无 status block)。
    • Problem: 仓库约定开放的 kind:task Issue 以三行状态块开头并由 acting agent 保持更新(docs/agent-collaboration.md:212-219),scoped-task 模板也把它放在正文首位(.github/ISSUE_TEMPLATE/scoped-task.md:17-19)。本 Issue 是 kind:task,但三项均缺失。
    • Conditions: 任何读者或后续 agent 无法判断当前状态、待决问题及下一步责任人。
    • Impact: 与标签/状态约定脱节,状态只能靠评论重建;也让 status/priority 标签无法按规则使用。
    • Fix: 在正文顶部补 **Current state:**、**Decision needed:**、**Next action:** 三行,并保持更新。

    未记录完成验收/关闭责任人,也未记录接受范围或授权

    • Where: Issue 正文「负责人:@amy-why-3459」与「对应 Roadmap 原始工作项 8」。
    • Problem: 指定的是执行负责人,但未说明谁接受完成并关闭。仓库要求工作遵循已接受范围与明确/常设授权,且完成须由具名人员或被授权 agent 接受、关闭权限须在动作前明确(docs/agent-collaboration.md:15、docs/agent-collaboration.md:17);模板相应字段为 .github/ISSUE_TEMPLATE/scoped-task.md:36、:40、:55。
    • Conditions: 多个子交付(路径梳理、案例、知识条目、复用验证)由不同人或 agent 分片提交时,无法判断谁可宣布整体完成。
    • Impact: 可能出现 PR 合并被误当作 Issue 完成,或长期无人授权关闭。
    • Fix: 补 Status、Accepted decision or scoped delegation(链接)与 Who accepts completion and may close 三项,明确分片的独立评审与最终验收人。

    知识交付落在受保护路径,未说明知识准入声明与索引再生成要求

    • Where: 验收项 4「经验进入现有知识体系」。
    • Problem: 交付必然触及受保护路径 src/inferrsi/data/skill_library/** 等(.github/knowledge-model-policy.json:4-5),main 上 knowledge-model-policy 是必需检查,需要在 PR 正文给出唯一 JSON 声明,且模型 ID/effort 仅限策略清单(.github/knowledge-model-policy.json:24、docs/knowledge-model-policy.md:31、:46);不合规需 @Dong1017 的例外审批。同时 skill-index.json 是生成物(docs/knowledge-base.md:17),新增/修订 skill 后需按 tools/build_skill_index.py:1-6 生成并刷新记录(docs/knowledge-base.md:271),catalog.py/skill_catalog.py 同为保护路径。
    • Conditions: 任何提交经验/技能内容的 PR,尤其是由不在准入清单内的模型生成时。
    • Impact: 缺声明会被必需状态检查阻断;漏刷新索引会导致验收项 4 的「可检索」实际不成立。
    • Fix: 在 Issue 的交付说明中写明该路径的知识准入声明义务、可用模型/effort 范围与例外审批人,以及新增 skill 后必须重新生成索引并验证 inferrsi knowledge search 能命中。

    验收项 3 的可追溯证据缺少冻结的门槛与修订版本

    • Where: 验收项 3「案例包含可追溯的正确性 / 性能证据;尚未执行的阶段明确标注未验证」。
    • Problem: 仓库要求先开 acceptance Issue 记录 pinned baseline/candidate、RunSpec、以及在候选择优之前冻结的验证级别与数值门槛,证据树置于 evidence/<campaign-id>/,判定仅 PASS/FAIL/INCONCLUSIVE(docs/contributing.md:94-112、:175-184)。本 Issue 既未链接相应 acceptance Issue,也未给出所需 L0–L4 级别,无法产出可追溯证据。
    • Conditions: 一旦需要给出任何正确性或性能数字(哪怕是案例对比)。
    • Impact: 结果只能停留在 source-grounded 候选,无法满足验收项 3;若事后补门槛则证据无效。
    • Fix: 明确哪些阶段只做文档/来源级记录(标注未验证),哪些阶段需为具体模型案例另开 acceptance Issue,并在其中冻结修订版本、RunSpec、验证级别与门槛后再运行。

    Reviewed commit: 2baebf6
    Coverage: Snapshot: 2637 files, 42149780 bytes; skipped 0 entries; Initial model context: 28 files; other accepted files available through tools; Git workspace contains a fixed snapshot, not full upstream history

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:knowledgeKnowledge line: packs, skill library, knowledge admissionbot-reviewedkind:taskBounded delivery task with a delegated slice

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions