extension-patterns
Add and inspect Habitat-Lab registry extensions for tasks, sensors, measures, actions, datasets, simulators, and baselines components.
- License 许可
- MIT
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- extension-patterns
- license
- MIT
- metadata
- { "disco-role": "operating" }
- description
- Add and inspect Habitat-Lab registry extensions for tasks, sensors, measures, actions, datasets, simulators, and baselines components.
- disable-model-invocation
- true
02 资源文件 4
- 参考文档references/extension-patterns.md10.7 KB
- 参考文档references/registry-api.md5.8 KB
- 参考文档references/troubleshooting.md6.4 KB
- 脚本scripts/inspect_registry_extensions.py8.0 KB
03 SKILL.md 正文
Habitat-Lab Extension Patterns
Use this sub-skill when you need to add, inspect, debug, or review custom Habitat-Lab extension classes that are discovered through habitat.registry or baseline_registry. It covers registration and config alignment; it does not run environments or train agents.
Fast Route
- For exact decorator/getter names, ownership boundaries, and config-name alignment, read references/registry-api.md.
- For recipes for sensors, measures, actions, tasks, datasets, simulators, policies, trainers, storage, updaters, and observation transforms, read references/extension-patterns.md.
- For failure diagnosis around missing keys, duplicate registrations, action spaces, measure dependencies, and transform shapes, read references/troubleshooting.md.
- To safely inspect currently importable registry keys without creating a simulator or
Env, runscripts/inspect_registry_extensions.pyfrom a checkout or installed environment.
Working Rules
- Define the extension class in an importable Python module and decorate it with the matching registry decorator.
- Ensure the module is imported before config construction or before a factory calls
registry.get_*orbaseline_registry.get_*. - Align every config
typevalue with the registry key, not necessarily with the config dictionary key or emitted observation/action UUID. - Keep runtime tests narrow: registry lookup, config-node creation, observation/action space compatibility, and shape contracts can be checked without full simulator assets.
- Escalate full
Envexecution, dataset loading, and training/evaluation to the task/env and baselines sub-skills.
Common Extension Flow
- Pick the registry surface:
habitat.registryfor lab runtime components,baseline_registryfor training/inference components. - Pick a stable registry key with
@...register_*(name="...")when the public config name should differ from the class name. - Create or update the matching structured config class so its
typefield equals that registry key. - Add the config node under the correct collection, such as
habitat.task.lab_sensors,habitat.task.measurements,habitat.task.actions,habitat.dataset,habitat.simulator,habitat_baselines.trainer_name,habitat_baselines.rl.policy.name, orhabitat_baselines.rl.agent.type. - Import the module containing the decorator before the lookup site runs.
- Probe with registry lookups and shape/space checks before attempting asset-backed execution.
Safe Probe
From this sub-skill directory, run the bundled probe to list registered keys:
python scripts/inspect_registry_extensions.py --all
Useful narrow probes:
python scripts/inspect_registry_extensions.py --category sensor --category measure
python scripts/inspect_registry_extensions.py --import-module my_project.habitat_extensions --category task_action --category policy
python scripts/inspect_registry_extensions.py --key measure:MyMeasure --key trainer:ppo
The script imports registries and optional extension modules, then prints mapping keys. It does not instantiate Env, datasets, simulators, trainers, or policies.
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).