界面已本地化;技能介绍与说明文档按所选语言由 AI 自动翻译,代码、命令、路径和专业术语保留原文,以原作者文档为准。
探索技能
数据与研究 · SKILL.md

training

training

【数据与研究】Plan and diagnose legacy Frustum PointNets v1 or v2 training runs, including flags, data contracts, checkpoints, and backend gates.

独立 GitHub 快照 · 自动分类 · 以原作者文档为准

技能说明

GitHub

name: training description: "Plan and diagnose legacy Frustum PointNets v1 or v2 training runs, including flags, data contracts, checkpoints, and backend gates." disable-model-invocation: true metadata: disco-role: operating license: Apache 2.0

Training

Use this route when a Researcher wants to train or resume Frustum PointNets. Read CLI reference, then training workflow before launching. This release assumes generated frustum pickles and a TensorFlow-1 graph runtime.

Safe route

  1. Validate KITTI inputs and generated pickle ownership through ../kitti-data-preparation/SKILL.md.
  2. Choose frustum_pointnets_v1 for a pure-TensorFlow graph path. Choose v2 only after ../runtime-and-custom-ops/SKILL.md proves all custom operators.
  3. Run python scripts/inspect_training_args.py --help and use its preflight before allocating a GPU or creating logs.
  4. Set a new log directory, explicit model, point count, channel mode, and restore path. Start with a short, separately approved smoke run; the repository's default is 201 epochs and is not a smoke test.

Training writes model-source copies, log_train.txt, TensorBoard summaries, and periodic model.ckpt files under the log directory. Keep these outputs outside the source tree when possible and never overwrite a checkpoint from a different model/point/channel configuration.

Backend boundary

The verified CPU TensorFlow-1 graph smoke supports API inspection and bounded v1 checks only. GPU placement, v2 custom ops, and practical training speed are not verified here. The route does not turn a CPU run into CUDA evidence. Route post-training validation to ../inference-and-evaluation/SKILL.md.

我的收藏