data-preparation
Routes EasyCV dataset layouts, annotation conversion, file I/O, and data-hub preparation workflows.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- data-preparation
- license
- Apache 2.0
- metadata
- { "disco-role": "operating" }
- description
- Routes EasyCV dataset layouts, annotation conversion, file I/O, and data-hub preparation workflows.
- disable-model-invocation
- true
02 资源文件 3
- 参考文档references/data-formats.md1.7 KB
- 参考文档references/troubleshooting.md1.2 KB
- 参考文档references/workflows.md1.8 KB
03 SKILL.md 正文
Data preparation
Use this sub-skill when the task is to prepare, validate, or convert datasets for EasyCV.
It covers dataset layout guidance, annotation conversion, OSS / local file I/O, and the repo's data-preparation helper modules.
Read these references first
references/data-formats.mdfor the expected on-disk layouts and table schemas.references/workflows.mdfor the repo-maintained conversion helpers and dataset-specific prep flows.references/troubleshooting.mdfor layout mismatches, missing annotation files, and OSS issues.- Root
references/model-zoo-overview.mdwhen the dataset choice depends on the task family.
What belongs here
Include tasks such as:
- preparing ImageNet, CIFAR, COCO, VOC, nuScenes, Market1501, CrowdHuman, or PAI-iTAG data
- converting annotation formats into EasyCV-ready structures
- checking a file list, manifest, TFRecord, or table schema before training or prediction
- using
easycv.file.iofor local or OSS paths - understanding which data shape a config expects before training
What stays elsewhere
- Training / evaluation once the data is ready ->
sub-skills/training-and-evaluation/ - Batch inference over prepared inputs ->
sub-skills/prediction-and-inference/ - Export / optimization after training ->
sub-skills/export-and-optimization/
Typical decision flow
- Identify the dataset family or table schema.
- Confirm the expected directory or file-list layout.
- Decide whether a conversion helper, a file I/O setup, or a manual layout fix is needed.
- Prepare or validate the data before touching the training command.
Common success signals
- The dataset root matches the layout documented for the chosen family.
- Annotation files, index files, or manifests are present where the loader expects them.
- OSS / ODPS credentials are configured before any remote read or write.
- The config's data roots point at the prepared dataset instead of the source notebook or download location.
Common preparation surfaces
easycv.file.iosupports both local and OSS paths.tools/prepare_datamodules are packaged into the installedeasycv.toolsnamespace.- Some dataset families use filelists, some use manifests, and some use TFRecords or ODPS tables.
- The train / eval sub-skill expects the data to be ready before it starts.
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).