Writing Skills
writing-skills
效率与协作技能,来自 obra/superpowers,查看原文获取完整用途和操作说明。
actuator-network【部署与运维】Validate Go1 deployment logs, build six-feature per-joint actuator samples, evaluate the small actuator MLP on CPU, and optionally train and export a bounded TorchScript model with safe diagnostics.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Use this sub-skill for the offline actuator-model workflow: inspect a
hardware_closed_loop deployment log, turn its 12-joint state history into
six-feature samples, evaluate the supplied TorchScript actuator model on CPU,
or deliberately opt in to a bounded CUDA training/export run.
inspect_actuator_log.py first. It is
read-only and validates a pickle log or portable JSON fixture without
importing Torch, training, networking, or plotting.prepare_actuator_data.py to emit a
deterministic JSON dataset to stdout or to a new explicit output path. It
does not train, load a network, plot, or overwrite an existing output by
default.Robot data collection, LCM channels, calibration, controller launch, and physical safety belong to robot-deployment, not this sub-skill. Do not start a robot, publish LCM messages, SSH, transfer artifacts, or run the repository's source-relative scripts as a prerequisite.
{"hardware_closed_loop": [config, infos]} where infos is a chronological list of records. A portable JSON
fixture may instead use {"records": [...]} or be a list of records; see
data format.joint_pos,
joint_pos_target, joint_vel, tau_est, and torques. The first three
may be a singleton (1, 12) row as produced by the deployment logger;
torque arrays may be (12,) or a singleton row.error = joint_pos - joint_pos_target and uses
[error[t], error[t-1], error[t-2], joint_vel[t], joint_vel[t-1], joint_vel[t-2]] as six inputs for each joint. The target is tau_est[t].resources/actuator_nets/unitree_go1.pt is a
TorchScript model contract, not a file to copy into this skill. Keep model
weights and generated logs outside the skill tree.tau_est, short history, shape/path issues,
CUDA, overwrite, and headless plotting.The scripts intentionally contain no source-repository-relative imports. They are data checks and preparation helpers, not replacements for robot collection or a training launcher.
The repository evidence was inspected from scripts/actuator_net/utils.py,
train.py, eval.py, go1_gym_deploy/utils/logger.py, the example log
format, README.md, and the existing TorchScript artifact contract. The
example artifact was loaded on CPU and accepted (batch, 6) input with
(batch, 1) output. The large example pickle was inspected for its envelope
and record shapes. Full actuator training, interactive plotting, CUDA
training, and physical deployment are not run or claimed here.