Two things rose-pro built OUTSIDE vcad that any robot project will need:
- Posed assemblies. rose's pose.py wraps each module root in translate/rotate chains per kinematic chain — it works and cache-hits, but the joint tree already exists in the URDF vcad can import. A
[pose] form (or vcad render --pose '{joint: deg}' on an imported URDF) makes any robot poseable natively.
- Swept clearance as a product. rose's sweep.py / skin_sweep.py — rotate child-side geometry through each joint range against the parent side, report min gap — is the actual safety gate of the whole project and it's 700 lines of project Python.
vcad sweep robot.urdf --ranges ... reporting min clearance per joint (and the angle at which it occurs) would be a headline feature; the kernel already has signed distance everywhere it needs it.
🤖 Generated with Claude Code
Two things rose-pro built OUTSIDE vcad that any robot project will need:
[pose]form (orvcad render --pose '{joint: deg}'on an imported URDF) makes any robot poseable natively.vcad sweep robot.urdf --ranges ...reporting min clearance per joint (and the angle at which it occurs) would be a headline feature; the kernel already has signed distance everywhere it needs it.🤖 Generated with Claude Code