domain-adaptation
Router for Transfer-Learning-Library domain adaptation workflows, losses, and optional benchmark stacks.
- License 许可
- MIT
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- domain-adaptation
- license
- MIT
- metadata
- { "disco-role": "operating" }
- description
- Router for Transfer-Learning-Library domain adaptation workflows, losses, and optional benchmark stacks.
- disable-model-invocation
- true
02 资源文件 6
- 参考文档references/api-reference.md9.6 KB
- 参考文档references/domain-adaptation-workflows.md8.7 KB
- 参考文档references/object-detection-adaptation.md4.7 KB
- 参考文档references/troubleshooting.md4.5 KB
- 参考文档references/wilds-workflows.md3.1 KB
- 脚本scripts/tllib_domain_adaptation_smoke.py10.3 KB
03 SKILL.md 正文
Domain Adaptation
Use this sub-skill for TLLib domain-adaptation workflows, loss wiring, and benchmark recipe selection.
What it covers
- Closed-set feature alignment: DANN, CDAN, ADDA, DAN, JAN, CORAL, BSP, MCD, MDD.
- Partial and open-set adaptation: PADA, IWAN, OSBP, class-weight reweighting, unknown-class thresholding.
- Special DA variants: AFN, MCC, RegDA keypoint, D-adapt object detection, and WILDS DA examples.
Route elsewhere when
- Datasets, ImageList formats, model factories, or transforms are the main question:
../vision-data-models/SKILL.md - Translation, CycleGAN, FDA, or style-transfer is the main question:
../translation/SKILL.md - SSL, pseudo-labeling, or teacher/student training is the main question:
../self-training/SKILL.md - DG, fine-tuning, or standalone transfer regularization is the main question:
../task-generalization/SKILL.md
How to use
- Identify the transfer setting: closed-set, partial, open-set, regression, keypoint, detection, or WILDS.
- Pick the matching API or workflow reference in
references/. - For CPU-safe validation, use
scripts/tllib_domain_adaptation_smoke.py. - Treat object-detection and WILDS coverage as optional-stack guidance unless the user explicitly has those dependencies.
Notes
- AFN appears here because it is used in DA workflows, but its standalone module mechanics live in the task-generalization / normalization path.
- MCC appears here because it is used in DA workflows, but its standalone semi-supervised mechanics live in the self-training path.
- Do not point users back to the source checkout or benchmark launchers; keep them on the bundled references and smoke helper.
- Keep benchmark-scale training, downloads, and optional dependency setup out of the smoke path.
Reference map
references/api-reference.md- public modules, losses, shapes, and common traps.references/domain-adaptation-workflows.md- classifier, regression, keypoint, and WILDS workflow patterns.references/object-detection-adaptation.md- D-adapt, Detectron2, proposal and feedback flow, optional stack notes.references/wilds-workflows.md- WILDS-specific CLI and dependency patterns.references/troubleshooting.md- shape, NumPy, TorchVision, CUDA, Detectron2, and WILDS issues.scripts/tllib_domain_adaptation_smoke.py- tiny CPU tensor smoke using installedtllib.
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).