协作头脑风暴
brainstorming
在实现前澄清需求、探索设计选择,并形成清晰的开发方向。
evaluation【开发与工程】Evaluate pytorch-cifar100 checkpoints safely with test.py, metric interpretation, and checkpoint/path validation.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Use this sub-skill when a user already has a pytorch-cifar100 checkpoint and needs to run the repository evaluator, select safe evaluation options, or interpret the printed metrics. This sub-skill does not create checkpoints and does not catalog architectures beyond the net-name validation needed for evaluation.
test.py command, validating -net and -weights, choosing CPU/GPU and batch size, explaining CIFAR-100 test-data side effects, interpreting Top-1/Top-5 error and parameter-count output.training: creating checkpoints, resuming training, changing optimization settings, or deciding which epochs to save.model-zoo: model internals, architecture trade-offs, output-shape adaptation, or choosing among architecture families.scripts/build_eval_command.py --list-nets for supported evaluator names.scripts/build_eval_command.py; it checks net spelling, validates the weights path unless explicitly allowed, and warns about CIFAR-100 download and GPU behavior../data for CIFAR-100.Top 1 err, Top 5 err, and Parameter numbers; lower error is better, and the printed errors are fractions unless you convert them to percentages.references/evaluation-workflows.md — evaluator command, runtime behavior, metric interpretation, and CPU/GPU/batch choices.references/checkpoints.md — checkpoint naming, expected state_dict format, architecture matching, and safe checkpoint path selection.references/troubleshooting.md — common failures and targeted recovery steps.