AGENT SKILL

paddle-detection

Guides PaddleDetection object detection, segmentation, keypoint, multi-object tracking, configuration, training, evaluation, inference, export, deployment, and PP-Human/PP-Vehicle pipeline workflows.

License 许可
Apache-2.0
最近更新
2026-09-03
Stars
★ 351
Forks
27

01 前言 Front Matter

name
paddle-detection
license
Apache 2.0
metadata
{ "disco-role": "operating" }
description
Guides PaddleDetection object detection, segmentation, keypoint, multi-object tracking, configuration, training, evaluation, inference, export, deployment, and PP-Human/PP-Vehicle pipeline workflows.
disable-model-invocation
true

02 资源文件 6

03 SKILL.md 正文

PaddleDetection

Use this skill when a task names PaddleDetection, paddledet, PP-YOLO/PP-YOLOE/PicoDet, PaddleDetection YAML configs, tools/train.py, tools/infer.py, model export, PP-Human, PP-Vehicle, PP-Tracking, or PaddleDetection deployment.

This is an operating router, not a copy of the repository. Work against the user's PaddleDetection checkout or installed package, and use the bundled references/scripts in this skill for decisions and preflight checks. Do not assume the creation checkout or its private environment still exists.

First route

  1. Identify the task family and choose exactly one primary route below.
  2. Establish the target checkout/package version, PaddlePaddle device, dataset layout, config path, weights source, and whether network/GPU/vendor runtimes are allowed.
  3. Run the bundled environment preflight before importing deep modules: scripts/check_paddledet_environment.py.
  4. Keep use_gpu=false or --device=CPU for a deterministic smoke test unless CUDA/TensorRT is explicitly required and available.
  5. Read references/troubleshooting.md whenever imports, weights, config paths, optional dependencies, or device checks fail.

Routes

Package baseline

The distribution is paddledet and the primary import is ppdet. The repository's baseline requirements include PaddleDetection utilities plus NumPy below 2, OpenCV, PyYAML, Shapely, SciPy, pycocotools, VisualDL, MOT dependencies, and image augmentation utilities. Install a compatible PaddlePaddle CPU or GPU build first, then install the repository requirements and the package in editable mode when working from source.

Minimal import check:

python -c "import paddle, ppdet; print(paddle.__version__, ppdet.__version__)"
python -c "import paddle; paddle.utils.run_check()"

The source checkout currently advertises package version 0.0.0 even when its Git tag is newer. Treat ppdet.model_zoo.get_config_file() as a network/cache operation and prefer a checked-out config path for source workflows; see the model-zoo route for the observed 404 failure mode.

Shared operating rules

  • Configs are YAML and may recursively merge _BASE_ files. Use -o key=value only for deliberate, logged overrides; verify paths and num_classes after merging.
  • Weights may be local files or remote URLs. Never download weights or datasets without explicit network approval; record the exact source and checksum when reproducibility matters.
  • CPU checks validate parsing/import/data contracts only. They do not prove CUDA, TensorRT, Paddle Lite, Serving, FastDeploy, or vendor accelerator behavior.
  • Treat training, benchmark, full pipeline, and TIPC commands as expensive unless a tiny fixture and explicit runtime budget are available.
  • Keep generated outputs outside the source tree when possible: checkpoints under a chosen save_dir, inference exports under a separate output_inference-style directory, and visualizations/results under a separate output directory.
  • Before changing a config, inspect the dataset reader, metric, input shape, class count, device flags, and pretrained/weights fields together.

Read references/install-and-environment.md for supported dependency variants and backend boundaries, references/verification-candidates.md for safe checks, and references/repo-provenance.md before deciding whether this skill is stale.

04 同仓库更多 Skills

VectorSpaceLab
VectorSpaceLab/AREX-Skill

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.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

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.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

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.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

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.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

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.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

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).

★ 351