model-backends
Configure OpenCompass model backends including HuggingFace, API, custom wrappers, LMDeploy, vLLM, credentials, resource run_cfg, tokenizer/model kwargs, batching, and backend troubleshooting.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- model-backends
- license
- Apache 2.0
- metadata
- { "disco-role": "operating" }
- description
- Configure OpenCompass model backends including HuggingFace, API, custom wrappers, LMDeploy, vLLM, credentials, resource run_cfg, tokenizer/model kwargs, batching, and backend troubleshooting.
- disable-model-invocation
- true
02 资源文件 5
- 参考文档references/api-models.md5.7 KB
- 参考文档references/backend-compatibility.md6.5 KB
- 参考文档references/model-configuration.md6.5 KB
- 参考文档references/troubleshooting.md5.8 KB
- 脚本scripts/check_api_model_config.py8.9 KB
03 SKILL.md 正文
Model Backends
Use this sub-skill when an OpenCompass task is about model configuration rather than dataset selection, prompt construction, or workflow launch. It covers HuggingFace/local models, API providers, accelerated LMDeploy/vLLM/LightLLM-style backends, custom model wrappers, credentials, and resource sizing.
Route by Backend
- HuggingFace/local Transformers models: use
references/model-configuration.mdforHuggingFace,HuggingFaceCausalLM,HuggingFacewithChatTemplate, tokenizer/model kwargs,batch_size,max_seq_len,max_out_len,batch_padding, andrun_cfg. - API models: use
references/api-models.mdforOpenAI,OpenAISDK,TurboMindAPIModel, credential handling,query_per_second,retry,rpm_verbose,openai_api_base, and no-network config checks. - Accelerated local backends: use
references/backend-compatibility.mdfor--accelerator {vllm,lmdeploy,None}, directVLLMconfigs, directTurboMindModelconfigs, service-based acceleration, and optional dependency boundaries. - New/custom model support: use
references/model-configuration.md#custom-model-extension-routewhen an existing OpenCompass backend cannot express the target model. - Backend failures: use
references/troubleshooting.mdbefore changing datasets, prompts, summarizers, or evaluation mode.
Boundaries
- For prompt templates,
meta_template, and generation prompt behavior, coordinate with../prompt-and-inference/SKILL.mdif present. - For dataset imports, config composition, and
read_base()patterns, coordinate with../configuration-and-datasets/SKILL.mdif present. - For
opencompassCLI launch modes,--mode,--reuse, runners, and work directories, coordinate with../evaluation-workflows/SKILL.mdif present. - Do not claim real HuggingFace/GPU/API inference is verified unless a task explicitly runs it in a suitable environment with required optional extras and credentials.
Bundled Script
scripts/check_api_model_config.py: loads an OpenCompass config, inspects model dictionaries, identifies likely API models, checks credential placeholders/environment-variable references, validates common API rate/resource fields, and exits before building models or making network calls.
04 同仓库更多 Skills
passnet-triton-opt
Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block/grid/warp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.
passnet-solve
END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.
passnet-skill
PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under ./pass_dir/, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.
passnet-pattern-fusion
Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()/replacement_args()/replacement_func() files, when a pass "failed to match", or when deciding how to fuse multiple kernels/ops.
passnet-orchestrate
Round/batch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep/revert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.
passnet-feedback
Fast, deterministic feedback for PassNet work: pre-flight pattern/match verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).