协作头脑风暴
brainstorming
在实现前澄清需求、探索设计选择,并形成清晰的开发方向。
testing【开发与工程】Run EdgeConnect checkpoint-backed testing and inference with prepared commands and checkpoint checks.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Use this sub-skill when the task is to run, prepare, or troubleshoot EdgeConnect test-time inference from existing checkpoints.
It covers the test.py wrapper, stage-specific checkpoint requirements, paired image/mask/edge inputs, output files, and safe command construction.
test.py as the thin main(mode=2) wrapper.main.load_config(mode=2) behavior: reads config.yml from --path/--checkpoints, forces MODE=2, defaults MODEL=3, forces INPUT_SIZE=0, and lets CLI inputs override the test flists and output path.--path/--checkpoints, --model, --input, --mask, --edge, and --output.MODEL=1, MODEL=2, MODEL=3, and MODEL=4 at inference time.DEBUG edge/masked side outputs.references/testing-workflows.md for single-file, directory, and external-edge recipes.references/checkpoint-layout.md before choosing a stage or checkpoint directory.references/troubleshooting.md when a command runs but produces missing, random-looking, or mismatched outputs.scripts/check_checkpoints.py validates a checkpoint directory without downloading anything or importing Torch.scripts/build_test_command.py prints a shell-quoted python test.py ... command from user-supplied paths and stage options; it never executes the command.config.yml and the stage's required generator weights.EDGE=1) or external edges (EDGE=2).data-preparation; route training to training; route PSNR/SSIM/FID scoring to evaluation.MODEL=3 and MODEL=4 have the same test-time flow: generate edges with the edge model, then inpaint with the inpainting model.EDGE: 2.